使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
广告概述
本部分介绍了在构建 Google Ads 集成时需要做出的主要设计选择,以及需要完成的主要任务:
主要的设计选项:
必备知识:
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-25。
[null,null,["最后更新时间 (UTC):2025-07-25。"],[[["\u003cp\u003eThis guide outlines the crucial design decisions and tasks involved in integrating with Google Ads.\u003c/p\u003e\n"],["\u003cp\u003eYou'll need to choose a billing model (direct or indirect) and decide whether to redirect ads to Merchant Center.\u003c/p\u003e\n"],["\u003cp\u003eBefore starting, ensure you have a Google Ads manager account and meet the Required Minimum Functionality (RMF).\u003c/p\u003e\n"]]],["The core content outlines key design choices and prerequisites for building a Google Ads integration. Design decisions include selecting a billing model (direct or indirect) and determining if ads will redirect to Merchant Center. Necessary prerequisites involve setting up a Google Ads manager account and ensuring the integration meets the Required Minimum Functionality (RMF) standards. These steps are fundamental for successful integration.\n"],null,["Ads Overview\n------------\n\nThis section discusses the main design choices you need to make and the\noverarching tasks you need to complete when building a Google Ads integration:\n\n#### Key design choices:\n\n- [Billing model (direct billing versus indirect billing)](https://developers.google.com/merchant/storebuilder/online/sections/4_0_1_billing_model_choice#401_billing_model_choice)\n- [Ads Redirect to Merchant Center](https://developers.google.com/merchant/storebuilder/online/sections/4_0_2_ads_redirect#402_ads_redirect_to_merchant_center)\n\n#### Prerequisites:\n\n- [Setting up a Google Ads manager account](https://developers.google.com/merchant/storebuilder/online/sections/4_0_3_ads_manager_acct#403_setting_up_google_ads_manager_account)\n- [Meeting Required Minimum Functionality (RMF)](https://developers.google.com/merchant/storebuilder/online/sections/4_0_4_access_levels#404_access_levels_and_required_minimum_functionality_rmf)"]]