Integration Policies

The following integration policies apply to the Offers integration.

Offers policy

Landing Page (mobile page & application)

  • The first step of the deep linked landing page must not be a login wall. Users must be able to view the offer, including terms and conditions, without signing in or creating an account.
  • All offers shared with Google must be visible with all relevant information on the mobile web 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, the number of times the offer can be used, meal types (lunch/dinner), course limitations, and subscription requirements.
    • All other offer restrictions (such as conditions of eligibility, redeeming instructions, and terms) must be visible directly on the landing page or accessible within 1 click of the landing page (for example, in a dialog).
  • The entire user journey up to checkout (such as selecting reservation details, building an order cart, or selecting a voucher) must be fully functional on the mobile web landing page without requiring a mobile application download.
    • During the web flow, users must be able to select and apply the applicable offer(s) for their selection (for example, choosing offers applicable to a selected reservation time slot and party size).
    • The final payment or transaction step may occur on the mobile web, offline, or inside a mobile application (including third-party payment applications). The web flow must inform a user before they leave the web flow (such as to open a mobile application).
  • Redeeming instructions and methods must be clearly stated and actionable.
  • When an offer URL redirects to an installed mobile application, the application's landing page must meet all requirements outlined in this section for offer landing pages.
    • Upon navigating back immediately after interacting with an offer on a Google experience, users must be returned to the originating Google experience.

Offer eligibility

  • Cashback offers are only allowed if the cashback is credited directly back to the payment method used for the payment. It is not allowed to credit the cashback as another form (such as loyalty or platform points).

Branding

  • The brand (logo and name) associated with an offer (through the brand_id field and the brand setting in the Action Center) must either be:
    • The primary brand of the partner.
    • The most prevalent brand visible on the landing page.

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.
  • Offer title detail text must fulfill these requirements:
    • Must not include special characters to emphasize a certain part (examples: !, ★, ☆, ♪, ◇, ◆, ◎, ■, \, /).
    • Must not include half-width katakana. Use full-width katakana instead.
    • Must not include full-width numbers. Use half-width numbers instead.
    • Must not include full-width symbols (e.g. '％'). Use half-width symbols (e.g. ‘%’)
  • Offers are required to present a genuine discount from the standard price or deliver additional value. Offers merely reflecting the standard retail price of an item or service are not permissible.