Google teams will migrate your Order with Google (OwG) integration from the Actions on Google (AoG) platform to the Partner Portal. By migrating to the new platform, we’ll consolidate and streamline the tools available to our food partners in one central place regardless of the type of integration they implement.
Below is a description of how the configuration of the OwG integration on the new Partner Portal account maps to the configuration of the AoG platform project.
For the OwG integration Production environment on Partner Portal, your brand information (Display name, Logo, ToS, PP), Fulfillment URL and Feed bucket configuration is copied from the Live AoG production deployment (AoG > Deploy > Release; Channel = Production & Review status = Approved) at the time of migration start notification.
For the OwG integration Sandbox environment on Partner Portal, your brand information (AoG > Deploy > Directory information), Fulfillment URL (AoG > Develop > Actions) and Feed bucket (AoG > Develop > Data Feeds; Sandbox data feeds) configuration is copied from the working version data on the AoG console at the time of migration start notification.
For accessing your Partner Portal account, users are copied from your GCP project with below role mapping:
|GCP project||Partner Portal account|
Alpha testers (defined under AoG > Deploy > Release > Manage alpha testers) are now part of the account users with the role “Tester”.
Users who have access to the AoG project via inherited, Org-level permissions will need to be manually added to the Partner Portal under Configure > Accounts and Users by a user with Administrator role. To see which permissions are inherited from the Org, look at the Inheritance column under IAM & Admin > IAM in your GCP Project. Note that Inheritance operates at the Role level, not the User level. If a User has an Admin role inherited from the Org and an Editor role on the project directly, the user will only have the Editor role in the Partner Portal.
What’s new and what changed?
Below is a description of different areas that have notable changes for the OwG integration between the AoG platform and the new Partner Portal.
|Area||AoG platform||Partner Portal|
|User access management||GCP access also controls AoG access. Three dots on the upper right corner > Manage user access||Access management is separate from GCP project access management. Configuration > Account and users > Users tab. For more details check Account and Users article.|
|Partner Contacts||Updated via a Google form||Viewed and updated directly on the platform. Configuration > Contact Information. For more details check Setting up your contact information article.|
|Production environment||Changes made to the integration need to be deployed and approved by Google to go live||Changes made to the integration in the Production environment would go live immediately without deployment step or approval step from Google.|
|Sandbox environment||Defined as the combination of Sandbox Feeds (Develop > Data Feeds; Sandbox data feeds) and working version of Fulfillment URL (Develop > Actions)||A complete environment meant to correspond to a partner development or staging environment.|
|Preview environment||Defined as the combination of uploaded feed file (Develop > Data Feeds > Upload test feed) and working version of Fulfillment URL (Develop > Actions)||Renamed to Quick Testing under Feeds for the Sandbox environment. You can upload a feed file and define a separate Test API url.|
|Alpha testing||Alpha deployment available at any time in the development lifecycle where a staging API url could be used and pre-defined alpha users can access Production feed to conduct end to end testing. Alpha users don't have access to the AoG project.||Tester users will have access to browse live restaurants from Production via testing link on the Restaurant Status Report under Dashboards. Tester users don't have access to the Partner Portal.|
|Batch Feed||Batches with file level errors would be processed and feeds would get updated based on the successfully fetched and parsed files. Any entities outside of the successful files would be kept (no implicit delete). As a result these entities would be stale and may cause errors during checkout.||Batches with file level errors would not be processed and feeds would get updated only when a new batch is clear of any file level errors. As a result the entire feeds is stale and may cause errors during checkout.|
|Incremental Inventory Updates||Incremental inventory updates reporting found at the bottom of Develop > Data Feeds > Prod/Sandbox||Naming updated to Real Time Updates (RTUs) and reporting can be found on Dashboards > RTU Reporting. For more details check Real-time updates article.|
|Entity Lookup||Entity lookup by ID available on Develop > Data Feeds > Prod/Sandbox||Submit a support request on Help & Support > Cases|
|Analytics - Overview||An overview of how is your business doing can be found under Analytics > Overview||An overview of how is your business doing can be found under Dashboards > Business Overview with an updated layout. For more details check Business Overview article.|
|Analytics - Transactions||An overview of Order request volumes, errors, and error rates occurring on your fulfillment API can be found at Analytics > Transactions||An overview of Order request volumes, errors, and error rates occurring on your fulfillment API can be found under Dashboards > Fulfillment API with an updated layout. For more details check Fulfillment API reporting article.|
|Analytics - Export||You can configure and update orders related data export via BigQuery by going to Analytics > Export||BigQuery export would continue to work for partners who already configured it via AoG. However, further configuration changes directly by partner are currently paused. Please submit a support request to configure BigQuery or make any changes. For more details check BigQuery export article.|
|Provider serving based on launguage matching||When a user's language did not match any language specified in the AoG console
||When a user's language does not have at least a partial match for the language with defined brands, the default language for that country is always used. For more details check Brand serving logic article.|
Why is Order with Google moving off the Actions on Google platform to the Partner Portal? What are the benefits?
To better serve the needs of our partners, we’re migrating our Order with Google experience to the Partner Portal. By migrating to our Partner Portal, we’ll consolidate and streamline the tools available to our Food partners in one central place.
What is Reserve with Google?
Reserve with Google helps users book or purchase reservations from different types of businesses. Users can also join or request to join the waitlist of participating restaurants. Learn more on Reserve with Google here.
What impact, if any, will this migration have for merchants and users?
Only the Order with Google infrastructure will migrate from Actions on Google to the Partner Portal. As such, we do not anticipate impact for merchants and users.
What’s happening with Actions on Google? Does this mean you’re rethinking that platform entirely?
To better serve the needs of our partners, we’re migrating our Order with Google experience to the Partner Portal. By migrating to our Partner Portal, we’ll consolidate and streamline the products and tools available to our Food partners in one central place.
Why my project was not migrated?
- A different project was used for production while the other project(s) where used for testing purposes only. In this case only the production project is migrated.
- The amendment associated with the migration was never signed.
- The project was created for experimentation purposes and you didn't have a contract with OwG.
I received a notification "Your Order with Google migration is completed" but I'm not able to login or view my account?
Please submit a support request
What will happen with my integration config, feed ingestions history and analytics data on Actions on Google once the migration is complete?
All configuration will be migrated as explained in the Migration details above. Feeds history would be available for the few days ahead of migration date and can be found under Feeds > history and Dashboards > RTU Reporting. The analytics data will be available under Dashboards > Fulfilment API & Business Overview.
Will all my AoG projects including projects used for development get migrated to the new platform?
We will only be migrating AoG projects used for production. Projects that are used for testing would be deprecated once the migration has successfully taken place.
How should I be optimizing and testing on my project without a test account?
The new Partner Portal has a sandbox environment which you can utilize for testing and map to your test/staging env.
We are planning to implement new features or update our current implementation, how should we go about it?
Once the changes are made to your development env you can use the Quick Testing under Feeds in the Sandbox env and validate the changes and test the complete order flow. Next, make sure that the Endpoints for the Sandbox are correctly pointing to your development env and the Sandbox Feeds are updated with the latest changes you made then run Integration Testing under Inventory for Sandbox environment. Lastly, copy the changes to your production env and run Integration Testing for Production environment to avoid any regressions to the live user experience.
My integration references several AoG API endpoints and OAuth scopes. Will I need to update these for the migration?
No. All currently supported API endpoints and OAuth scopes will continue to work on Partner Portal.
When can I scale my new account to additional countries and brands?
Partners can expand to new countries where OwG is live for the same Brand right away after migration. Adding new Brands will be enabled in a future phase.
Will this migration impact my existing PAS or RwG integrations?
We will be migrating the OwG over to the Partner Portal as a new account and do not anticipate any disruption to your existing PAS or RwG integrations. The newly created account would have "(OwG)" appended to the end of account name to distinguish it from any other integrations' accounts you have. Once the migration has been completed for all partners, Google teams will reach out to discuss consolidating your integrations under one account.