预订型商品集成政策
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
以下集成政策适用于“预订型商品”集成。
优惠政策
着陆页(移动页面和应用)
- 您与 Google 分享的任何餐厅的所有优惠都应至少在移动版着陆页上显示,并附带所有相关信息。
- 优惠价值和说明文本必须直接显示在着陆页上。
- 着陆页必须清晰、全面地说明每项优惠的资格要求。这包括与细分用户群、付款方式、特定日期或时间、最低消费金额和优惠的使用次数相关的限制。
- 所有其他优惠限制(例如资格条件、兑换说明、条款等)都必须显示在着陆页上,或者在点击一次着陆页后即可访问(例如弹出式对话框)。
- 对于
OFFER_MODE_WALK_IN
优惠以外的所有优惠,与优惠关联的操作流程(例如预订餐桌)必须允许用户选择与其选择(例如对于预订,显示适用于所选时间空档和人数的优惠)
- 兑换说明和方法必须明确说明且可操作(例如,如果兑换优惠需要在结账时通过合作伙伴系统支付账单,则应说明如何在该系统中付款,并且用户应能够在结账时通过合作伙伴系统支付账单)。
- 当商品网址重定向到合作伙伴已安装的移动应用时,该应用的着陆页必须满足本节中针对商品着陆页列出的所有要求。
- 在 Google 体验中与商品互动后立即返回(例如,使用返回按钮、手势导航)时,用户必须返回原始 Google 体验。
优惠数据和格式
- 合作伙伴必须遵守相关文档中列出的指定技术要求和数据格式。不符合这些要求可能会导致 Feed 处理错误或延迟。
- 优惠必须面向所有用户。商品可能需要付费订阅,但只要任何人都可以订阅,就符合条件。
- 提供的所有元数据在 Feed 上传时都必须准确无误且最新(必须至少每天上传一次)。所列优惠必须有效,并且可以立即或在
ValidityPeriod
中指明的时间提供给用户;已过时、已售罄或已过期的优惠必须从 Feed 中移除。
- 合作伙伴必须在各个平台上使用一致的商品格式。禁止 Feed 中的商品详情与合作伙伴应用或网站上显示的详情不一致。
- 合作伙伴必须在
offer_display_text
字段中提供清晰简洁的优惠详情,准确反映优惠的价值和任何限制。
- 合作伙伴必须明确指明每项优惠的优惠类别(基本优惠或附加优惠)和适用的优惠模式(
OFFER_MODE_FREE_RESERVATION
、OFFER_MODE_PAID_RESERVATION
、OFFER_MODE_WALK_IN
)。
- 合作伙伴必须确保准确地为每项商品映射付款工具类型。
- 合作伙伴必须每天至少自动提供一次更新,或按照开发者文档中的说明提供更新。数据更新频率必须足够高,才能达到 95% 的准确度。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-05-26。
[null,null,["最后更新时间 (UTC):2025-05-26。"],[],[],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."]]