Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

Transition Documentation: https://developers.google.com/actions-center/verticals/ordering/e2e/transitioning-to-redirect/overview-and-timelines

Adding them to our current feed: https://developers.google.com/actions-center/verticals/ordering/e2e/transitioning-to-redirect/providing-action-links-via-e2e-feeds#sending_action_links

Opting out: When merchants request to opt out, we should require them to either reply back through an email address of their restaurant domain or opt out by our system calling their restaurant and them answering there to confirm. We can do this manually first and then automate it. This is to prevent random people taking down our listings.  https://developers.google.com/actions-center/verticals/ordering/redirect/policies/compliance-requirements#merchant_eligibility_criteria

Partner Brand Clarification: https://developers.google.com/actions-center/verticals/ordering/redirect/policies/platform-policies#partner_brand

Real Time Updates: https://developers.google.com/actions-center/verticals/ordering/redirect/integration-steps/action-link-feeds/real-time-update

Conversion tracking: We can charge a fee based off of this if we want https://developers.google.com/actions-center/verticals/ordering/redirect/integration-steps/direct-conversion-tracking

Questions/Potential Concerns

Tracking orders: we will need to implement a way to track which orders placed on an RDS’s website come from google BTSF-4728 - Getting issue details... STATUS

OwG specific features: Menu Markup, Customer-facing fees

ActiveMenus Branding: Maybe we need to figure out a way to include an ActiveMenu logo on the ordering page when the order source is OwG https://developers.google.com/actions-center/verticals/ordering/redirect/policies/platform-policies#merchant_service_eligibility

  • No labels