Reservations Offers Integration Policies
Stay organized with collections
Save and categorize content based on your preferences.
The following integration policies apply to the Reservations Offers integration.
Offers policy
Landing Page (mobile page & application)
- All Offers shared with Google for any restaurant should be visible with all
relevant information on at least the mobile landing page.
- The offer value and description text must be visible on the landing page
directly.
- Landing pages must clearly and comprehensively outline the eligibility
requirements for each offer. This includes restrictions related to user
segments, payment methods, specific days or times, minimum spending
amounts, and the number of times the offer can be used.
- All other offer restrictions (ex: conditions of eligibility, redeeming
instruction, terms …) must be visible on the landing page or accessible
within 1 click of the landing page (ex: pop-up dialog).
- For all offers except
OFFER_MODE_WALK_IN offers, the action flow
associated with the offer (ex. reserving a table) must allow the user to
select the offer(s) applicable associated with their selection (ex. For
reservation, offers applicable for the time slot and party size selected)
- The redeeming instructions and methods must be clearly stated and actionable
(ex: if redeeming the offer requires paying the bill on the partner system
at checkout, the instruction to pay on the system should be mentioned and
the user should be able to pay the bill on the partner system at checkout).
- When an offer URL redirects to a partner's installed mobile application, the
application's landing page must meet all requirements outlined in this
section for offer landing pages.
- Upon navigating back (e.g., using the back button, gesture navigation)
immediately after interacting with an offer on a Google experience,
users must be returned to the originating Google experience.
Offers Data & Format
- Partners must adhere to the specified technical requirements and data
formats outlined in the relevant documentation. Failure to meet these
requirements can result in feed processing errors or delays.
- The offer must be generally available to any user. Offers may require a paid
subscription, as long as anyone can subscribe.
- All metadata provided must be accurate and up-to-date at the time of feed
upload (must be uploaded at least on a daily basis). Offers listed must be
active and available to users either immediately or in advance as indicated
using in the
ValidityPeriod; outdated, sold out or expired offers must be
removed from the feed.
- Partners must use consistent offer formats across platforms. Discrepancies
between the offer details in the feed and those displayed on the partner's
app or website are prohibited.
- Partners must provide clear and concise offer details in the
offer_display_text field, accurately reflecting the offer's value and any
limitations.
- Partners must clearly indicate the offer category (Base Offer or Add-On
Offer) and applicable offer modes (
OFFER_MODE_FREE_RESERVATION,
OFFER_MODE_PAID_RESERVATION, OFFER_MODE_WALK_IN) for each offer.
- Partners must ensure accurate mapping of payment instrument types for each
offer.
- Partner must provide updates automatically at least once a day or as per the
developer documentation.
Data update frequency must be sufficient to meet 95% accuracy.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-06-30 UTC.
[null,null,["Last updated 2025-06-30 UTC."],[],[],null,["# Reservations Offers Integration Policies\n\nThe following integration policies apply to the Reservations Offers integration.\n\nOffers policy\n-------------\n\n### Landing Page (mobile page \\& application)\n\n- All Offers shared with Google for any restaurant should be visible with all relevant information on at least the mobile landing page.\n - The offer value and description text must be visible on the landing page directly.\n - Landing pages must clearly and comprehensively outline the eligibility requirements for each offer. This includes restrictions related to user segments, payment methods, specific days or times, minimum spending amounts, and the number of times the offer can be used.\n - All other offer restrictions (ex: conditions of eligibility, redeeming instruction, terms ...) must be visible on the landing page or accessible within 1 click of the landing page (ex: pop-up dialog).\n- For all offers except `OFFER_MODE_WALK_IN` offers, the action flow associated with the offer (ex. reserving a table) must allow the user to select the offer(s) applicable associated with their selection (ex. For reservation, offers applicable for the time slot and party size selected)\n- The redeeming instructions and methods must be clearly stated and actionable (ex: if redeeming the offer requires paying the bill on the partner system at checkout, the instruction to pay on the system should be mentioned and the user should be able to pay the bill on the partner system at checkout).\n- When an offer URL redirects to a partner's installed mobile application, the application's landing page must meet all requirements outlined in this section for offer landing pages.\n - Upon navigating back (e.g., using the back button, gesture navigation) immediately after interacting with an offer on a Google experience, users must be returned to the originating Google experience.\n\n### Offers Data \\& Format\n\n- Partners must adhere to the specified technical requirements and data formats outlined in the relevant documentation. Failure to meet these requirements can result in feed processing errors or delays.\n- The offer must be generally available to any user. Offers may require a paid subscription, as long as anyone can subscribe.\n- All metadata provided must be accurate and up-to-date at the time of feed upload (must be uploaded at least on a daily basis). Offers listed must be active and available to users either immediately or in advance as indicated using in the `ValidityPeriod`; outdated, sold out or expired offers must be removed from the feed.\n- Partners must use consistent offer formats across platforms. Discrepancies between the offer details in the feed and those displayed on the partner's app or website are prohibited.\n- Partners must provide clear and concise offer details in the `offer_display_text` field, accurately reflecting the offer's value and any limitations.\n- Partners must clearly indicate the offer category (Base Offer or Add-On Offer) and applicable offer modes (`OFFER_MODE_FREE_RESERVATION`, `OFFER_MODE_PAID_RESERVATION`, `OFFER_MODE_WALK_IN`) for each offer.\n- Partners must ensure accurate mapping of payment instrument types for each offer.\n- Partner must provide updates automatically at least once a day or as per the [developer documentation](/actions-center/verticals/reservations/offers/integration-steps/overview). Data update frequency must be sufficient to meet 95% accuracy."]]