在地生活服務廣告端對端整合政策
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
下列整合政策適用於端對端在地生活服務廣告整合。
如要查看端對端在地生活服務廣告整合功能的平台政策,請參閱「在地生活服務平台政策」。
端對端政策
請先閱讀下列整合資格條件,再著手整合。合作夥伴必須符合下列規定和政策,才有資格與 Actions Center 的在地生活服務廣告端對端整合整合。
雖然下列規定是「動作中心」計畫的必要資格條件,但符合這些規定不保證合作夥伴能夠與「動作中心」整合或上線。
如果不符合規定和政策,整合、商家或服務可能會遭到停權或從平台移除。
一般平台規定
- 合作夥伴收集與處理所有商家和使用者資料 (包括所有的個人識別資訊) 的方式,必須遵循《一般資料保護規則》(GDPR) 和其他任何適用的隱私權相關法律。
- 合作夥伴必須獲得其所代表商家的授權,才可代商家進行預訂。
合作夥伴必須能即時直接存取商家的預訂情形/時段 (意即合作夥伴必須能夠在 1 秒內回應 Google 送出的預訂情形要求)。
- 特殊情況:Google 可支援需要商家非同步確認的預訂,但預訂流程必須以可供預訂的時段為準。合作夥伴必須掌握並呈現即時預訂情形 (透過商家的線上系統),就算只能在商家確認後才完成預訂也是如此。
合作夥伴必須擁有其合作商家的完整庫存清單;提供部分庫存或滯銷庫存的商家可能不符資格。
合作夥伴必須擁有至少 30 天的商家預訂情形資訊。
合作夥伴必須支援線上取消預訂服務。
要求預付費用的合作夥伴必須遵守 Actions Center 的付費政策,其付款處理方必須名列下方支援名單,並接受透過代碼化技術支付的款項。
合作夥伴必須能夠提供服務費用的精確計費方式資料,並遵守 Actions Center 的價格政策。
合作夥伴必須符合「行動中心」在地生活服務廣告端對端整合技術規定。
合作夥伴必須遵守「動作中心」的商家與服務資格規定。
合作夥伴必須遵守 Actions Center 的支援與維護指南。
合作夥伴必須維持啟動和監控指南中定義的可接受錯誤率。
所有預訂都必須在即時自動確認,但使用非同步整合功能完成的預訂除外。透過非同步整合功能完成的預訂必須遵守非同步指南。
合作夥伴必須遵守行動中心的特定產業或功能政策 (優惠、付款、線上服務和餐廳)。
合作夥伴必須依據規範,維持商家名稱、地址、服務名稱和說明的標準品質。
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2024-11-26 (世界標準時間)。
[null,null,["上次更新時間:2024-11-26 (世界標準時間)。"],[[["\u003cp\u003ePartners integrating with Local Services Ads End-to-End must adhere to data privacy regulations like GDPR and have authorization for booking services on behalf of merchants.\u003c/p\u003e\n"],["\u003cp\u003eReal-time access to merchant availability, comprehensive inventory, online cancellation capabilities, and accurate pricing are crucial requirements for integration.\u003c/p\u003e\n"],["\u003cp\u003ePartners need to comply with payment policies, including using supported processors and accepting tokenized payments, and meet technical integration requirements.\u003c/p\u003e\n"],["\u003cp\u003eMaintaining acceptable error rates, ensuring automatic booking confirmations (with exceptions for async integrations), and adhering to vertical-specific policies are essential.\u003c/p\u003e\n"],["\u003cp\u003ePartners are expected to uphold content quality standards for merchant and service information, including names, addresses, and descriptions.\u003c/p\u003e\n"]]],["Partners integrating with the Local Services Ads End-to-End platform must adhere to specific requirements, including GDPR compliance and real-time access to merchant availability. They must handle bookings, cancellations, and potentially payments online, supported by tokenized transactions. Comprehensive, 30-day+ merchant inventory is required. Partners must meet technical standards, provide accurate pricing, and comply with various policies, like support guidelines. All bookings must be confirmed in real time, with the exception of the ones using the async integration. Additionally, content quality standards must be met.\n"],null,["# Local Services Ads End-to-End Integration Policies\n\nThe following integration policies apply to the Local Services Ads End-to-End\nintegration.\n\nLocal Services Ads End-to-End platform policies\n-----------------------------------------------\n\nTo read the platform policies for the Local Services Ads End-to-End integration, see [Local Services platform\npolicies](https://support.google.com/adspolicy/answer/6245891).\n\nEnd-to-End Policies\n-------------------\n\nPlease read through the following integration eligibility criteria before\nbeginning an integration. Partners must meet the following requirements and\npolicies to be eligible to integrate with the Actions Center's\n[Local Services Ads End-to-End integration](/actions-center/verticals/local-services/e2e/policies/platform-policies#merchant_and_service_eligibility).\n\nWhile the following requirements are necessary components of eligibility for the Actions Center program, meeting the requirements does not guarantee a partner will be eligible to integrate or go live with the Actions Center.\n\nFailure to meet the requirements and policies may result in integration, merchant or services being suspended or removed from the platform.\n\n### General Platform Requirements\n\n1. Partners must collect and handle all merchant and user data, including any personally identifiable information, in a manner compliant with the General Data Protection Regulation (GDPR) and any other applicable privacy laws.\n2. Partners must be authorized to make bookings on behalf of their merchants.\n3. Partners must have direct access to merchants' availability/time slots in real time (ie. partners must be able to respond to availability requests from Google in less than 1 second).\n\n - *Special case*: We do support reservations that require asynchronous confirmation from the merchant, but the reservation flow must be based on an available time slot. Partners must have real time availability, i.e. through merchant online systems, even if it requires confirmation from the merchant to finalize the reservation.\n4. Partners must have comprehensive inventory for their merchants. Merchants with partial or distressed inventory may not be eligible.\n\n5. Partners must have 30 days or more of merchants' availability.\n\n6. Partners must support online cancellation of bookings.\n\n7. Partners requiring pre-payments must abide by the Actions Center's [payment policy](/actions-center/verticals/local-services/e2e/policies/integration-policies#payments-policies), their payment processors must be in the following [supported list](/pay/api) and accept tokenized payments.\n\n8. Partners must be able to provide accurate pricing data for the cost of services and abide by the Actions Center's [pricing policy](/actions-center/verticals/local-services/e2e/policies/integration-policies#pricing-policies).\n\n9. Partners must be able to meet the Actions Center technical\n [Local Services Ads End-to-End integration](/actions-center/verticals/local-services/e2e/overview)\n requirements.\n\n10. Partners must abide by the Actions Center's [merchant and services eligibility requirements](/actions-center/verticals/local-services/e2e/policies/platform-policies#merchant_and_service_eligibility).\n\n11. Partners must abide by the Actions Center's [support and maintenance guidelines](/actions-center/verticals/local-services/e2e/policies/platform-policies#support_and_maintenance_guidelines).\n\n12. Partners must maintain acceptable error rates defined in\n [Launch and Monitoring guidelines](/actions-center/verticals/local-services/e2e/integration-steps/launch-and-monitoring).\n\n13. All bookings must be confirmed automatically in real time with the exception of bookings made with an async integration. Bookings made through an async integration must adhere to the\n [Async guideline](/actions-center/verticals/local-services/e2e/add-ons/add-async).\n\n14. Partners must abide by the Actions Center's vertical or feature specific policies ([Offers](/actions-center/verticals/local-services/e2e/policies/integration-policies#offers-policy), [Payment](/actions-center/verticals/local-services/e2e/policies/integration-policies#payments-policies), [Online services](/actions-center/policies/virtual-policy) and [Dining](/actions-center/verticals/local-services/e2e/policies/integration-policies#dining-policies)).\n\n15. Partner must maintain standard quality content for merchant name, address, services name and description per [guideline](/actions-center/verticals/local-services/e2e/policies/platform-policies#content_quality_standards)."]]