In order to launch, you must be approved by Google. Google evaluates your readiness based on the following criteria:
- Integration policy: Verify that your integration follows the policies outlined in the Policies section.
- Feed ingestion evaluation: Verify that there are no feed validation errors and the feeds are uploaded for the last 3 days. Feed validation issues appear in Feed History.
- Onboarding Plan: Verify that the Onboarding Plan is complete in Actions Center. This includes that feeds are uploaded consecutively for 3 days with at least 10 entities in each feed. If you are launching with Fees and or ETAs, the service feed should meet this criteria. If you are launching with Menus, the menu feed should also meet this criteria.
- Contact information: Fill out all required fields in the Contact Information (documentation) page in the Actions Center. These fields are mandatory before launch.
- Brand name: The user-facing brand name is set in the Brands page.
- Brand configuration: The company logo, domain, merchant sign-up URL, and merchant opt-out URL are set in the Brands page.
- Real-time updates (Optional): If you are launching with Real-time updates, verify that there are at least 3 successful calls over the last 3 days. The RTU entity failure rate should be less than 3% for the last 3 days. You can find the RTU requests and error counts in the RTU Reporting dashboard.
- Conversion Tracking (Optional): If you are launching with Conversion Tracking, verify that there are at least 3 successful calls over the last 7 days. The failure rate should be less than 3% for the last 7 days. You can find the Conversion Tracking requests and error counts in the Conversion Tracking dashboard.
- Feed data evaluation: After you upload your feeds, Google processes and evaluates them for quality and completeness. We look at several factors:
- Feeds meet the specifications.
- Feeds include all required fields.
- Each merchant or entity has an action
urldefined. - The majority of your entity data matches with Google Maps locations. You can find all unmatched entities in Food Ordering Entities by setting the Matched filter to No. Entity matching issues can be resolved by updating the Entity feed with accurate details, or by creating a match described in Merchant Matching and Testing.
- Action links are working and are not returning HTTP status codes in the 400 or 500 ranges. Action links with errors are reported in the Data Quality Dashboard. An Action link with an error will automatically be disabled and won't be shown to users until the error is resolved.
After the above-mentioned conditions are satisfied, you can click the button to request a production review from the Onboarding Plan in the Actions Center, and we will enable all of your feeds in our production environment. This completes the integration, and allows any external user to navigate to your action link through Google.