使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
4.0.4 访问权限级别和最低功能要求 (RMF)
价值和业务影响
您的 Google Ads API 开发者令牌具有多个访问权限级别。
访问权限级别和允许的用途简要介绍了这些访问权限级别。总结：
测试帐号访问权限：仅使用测试帐号每天最多可执行 15,000 次操作，最多可发出 1,000 次请求。完成 Google Ads API 注册后，您将获得一个级别对应的开发者令牌。请参阅测试帐号指南，详细了解如何创建测试帐号。
基本访问权限：使用测试帐号和生产帐号每天最多可执行 15,000 次操作和 1,000 次请求。这是所有已获批准的开发者令牌的默认访问权限级别。生产帐号是指投放真实的实时 Google 广告的所有帐号（测试帐号不投放广告）。如需进行申请，请参阅申请基本访问权限。
标准权限：使用测试帐号和生产帐号执行无限的操作，每天最多执行 1,000 次请求。如需详细了解限制和例外情况，请参阅 API 配额。如果您有基本访问权限级别，并且希望申请不受限制的 Google Ads API 操作，请填写标准访问权限申请表单。
此表单会就使用该 API 的软件设计提出详细问题，并要求提供软件的设计文档。请注意，此应用中的“MCC”是指 Google Ads 经理帐号。
大多数合作伙伴都需要使用标准访问权限级别来扩展其解决方案。建议在早期开发和测试期间获取基本访问权限。然后，在将效果最大化广告系列集成发布到生产环境之前的几周，您可以申请标准访问权限，并证明自己满足相关要求（请参阅下一部分）。
最低功能要求 (RMF)
最低功能要求 (RMF) 是指某些应用开发者在使用 Google Ads API 时必须提供的特性及其他功能。RMF 仅适用于拥有标准权限的令牌。
作为为效果最大化广告系列广告客户管理多个商家帐号的电子商务提供商，您只需实现效果最大化广告系列功能列表中列出的 Google Ads API 创建和管理功能及报告。此外，您必须采取合理措施，确保每个功能都可供访问和使用。
标准权限的最低功能要求流程
下面总结了获得标准权限并保持合规性的步骤：
| 有效令牌 |
基本访问权限 |
标准
访问权限 |
抗辩通知
拒绝 |
保持
合规性 |
→ 注册 Google Ads 经理帐号。
→ 激活开发者令牌。
✓ 开发者令牌处于有效状态，可用于测试帐号。 |
✩ 准备理由和简要设计（示例）。
→ 填写跟进表单。
⌛ 等待后续问题回答。
✓ 获批后，开发者令牌将授予基本访问权限。 |
✩ 确认需要标准权限（限制）。
✩ 准备详细设计（示例）。
→ 完成标准权限申请
⌛ 等待并回答后续问题
✓ 如果获得批准，开发者令牌将授予标准权限 |
✩ 如果被拒绝，请查看拒绝页面并评估原因。
→ 根据需要进行修改，然后重新申请。
✓ 获得批准后，开发者令牌将授予标准权限。 |
✩ 定期查看功能列表，确定在截止日期前未能满足的任何要求。
→ 完成许可使用表单的更改，以提供屏幕截图来展示产品已满足要求。
✓ 保持标准权限。 |
其他要求
在将效果最大化广告系列集成投入生产环境之前，最后一步是确保：
您的开发者令牌使用适当的访问权限级别，如访问权限级别和允许的用途中所述。如需详细了解违规费用，请参阅价目表和违规费用。如 4.1.1 OAuth 中所述，您还必须提供用于访问 Google OAuth2 服务器的凭据。
您提议与 Google Ads API 搭配使用的软件符合我们的条款及条件以及最低功能要求 (RMF)，具体如此步骤中所述。
由于您的公司为客户管理广告客户帐号，因此您必须遵守我们的第三方政策，才能获得用于生产用途的 Google Ads API 的访问权限。
在欧洲，商家可以通过他们选择的一项或多项购物比较服务 (CSS) 参与购物广告计划，其中包括 Google 购物（Google 的 CSS）。
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-07-25。
[null,null,["最后更新时间 (UTC)：2025-07-25。"],[[["\u003cp\u003eGoogle Ads API developer tokens have three access levels: Test, Basic, and Standard, each allowing different levels of operation and account usage.\u003c/p\u003e\n"],["\u003cp\u003eStandard access, necessary for scaling solutions, requires implementing specific features and reports, outlined in the Performance Max Campaign feature list, under Required Minimum Functionality (RMF).\u003c/p\u003e\n"],["\u003cp\u003eBefore production, ensure your developer token has the appropriate access level, your software complies with Google Ads API terms and RMF, and you adhere to the Third Party Policy if managing client accounts.\u003c/p\u003e\n"],["\u003cp\u003eMerchants in Europe can leverage Comparison Shopping Services, including Google Shopping, for Shopping ads.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Ads API best practices, including batch processing, can optimize application efficiency and performance.\u003c/p\u003e\n"]]],["Google Ads API developer tokens have three access levels: Test, Basic, and Standard. Test access allows limited operations on test accounts. Basic access, the default for approved tokens, permits limited operations on test and production accounts. Standard access enables unlimited operations on both account types, requiring a detailed application. Standard access also requires adherence to Required Minimum Functionality (RMF) and involves regular feature compliance reviews. Developers should initially pursue Basic access, then apply for Standard access before production release.\n"],null,["4.0.4 Access Levels and Required Minimum Functionality (RMF)\n------------------------------------------------------------\n\n### Value and Business Impact\n\n*** ** * ** ***\n\nYour Google Ads API developer token has multiple access levels.\n[Access Levels \\& Permissible Use](https://developers.google.com/google-ads/api/docs/access-levels) provides an overview about these access\nlevels. To summarize:\n\n- [Test account access](https://developers.google.com/google-ads/api/docs/access-levels#test_account_access): Execute up to 15,000 operations and make up to\n 1,000 requests per day using only test accounts. Once you complete the\n [Google Ads API sign up](https://developers.google.com/google-ads/api/docs/first-call/overview), you are issued a developer token set to this\n level. See the [test account guide](https://developers.google.com/google-ads/api/docs/first-call/overview#test_account) to learn more about how to create a test\n account.\n\n- [Basic access](https://developers.google.com/google-ads/api/docs/access-levels#basic_access): Execute up to 15,000 operations and make up to 1,000\n requests per day using test and production accounts. This is the default access\n level for all approved developer tokens. Production accounts are any accounts\n that serve real, live Google ads (test accounts don't serve ads). To apply, see\n [Applying for Basic access](https://developers.google.com/google-ads/api/docs/access-levels#applying_for_basic_access).\n\n- [Standard access](https://developers.google.com/google-ads/api/docs/access-levels#standard_access): Execute unlimited operations and up to 1,000 requests\n per day using test and production accounts. For details of limits and\n exceptions, see [API quotas](https://developers.google.com/google-ads/api/docs/best-practices/quotas). If you have basic access level and you would\n like to apply for unlimited Google Ads API operations, fill out the\n [standard access application form](https://www.google.com/appserve/fb/forms/standardaccess/). \n\n This form asks you detailed\n questions about the design of your software that uses the API, and also asks\n for design documents of your software. Note that \"MCC\" in this application\n refers to the Google Ads manager account.\n\nMost partners need the Standard access level to scale their solution. The\nrecommended approach is to gain Basic access during early development and\ntesting. Then, a few weeks before you release your Performance Max integration\ninto production, you would apply for Standard access and demonstrate that you\nmeet the requirements for it (see next section).\n\n### Required Minimum Functionality (RMF)\n\n[Required Minimum Functionality](https://developers.google.com/google-ads/api/docs/rmf) (RMF) refers to the features and other\nfunctionality that certain application developers must offer when using the\nGoogle Ads API. RMF applies only to tokens with [Standard access](https://developers.google.com/google-ads/api/docs/access-levels#standard_access).\n\nAs an ecommerce provider managing multiple merchant accounts for Performance\nMax advertisers, you are only required to implement the Google Ads API creation\nand management features and reports listed in the\n[Performance Max Campaign feature list](https://developers.google.com/google-ads/api/docs/rmf#performance_max_campaign_feature_list). Additionally, you must make\nreasonable effort to ensure that each of the features is accessible and\nfunctional.\n| **Note:** If you are unsure if the RMF policy applies to your software, [contact the API Compliance team](https://support.google.com/adspolicy/contact/contact_ads_api), who can audit your software to ensure compliance.\n\n### RMF process for Standard access\n\nThe following summarizes the steps to gain Standard access and maintain\ncompliance:\n\n| Active Token | Basic Access | Standard Access | Counter Rejections | Maintain Compliance |\n|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| → [Sign up for Ads Manager Account](https://support.google.com/google-ads/answer/7459399). → [Activate Dev Token](https://developers.google.com/google-ads/api/docs/first-call/dev-token). ✓ Developer token is active and works for test accounts. | ✩ Prepare justification and high-level design ([sample](/static/merchant/storebuilder/images/blueprint/4_0_4_sample.png)). → [Complete follow-up form](https://support.google.com/adspolicy/contact/new_token_application). ⌛ Wait for follow-up questions. ✓ Once approved, Developer token granted Basic Access. | ✩ Confirm need for standard access ([limits](https://developers.google.com/google-ads/api/docs/access-levels)). ✩ Prepare detailed design ([sample](/static/merchant/storebuilder/images/blueprint/4_0_4_sample.png)). → [Complete Standard Access application](https://support.google.com/adspolicy/contact/standard_token_application) ⌛ Wait and answer follow-up questions ✓ If approved, Developer token granted Standard Access | ✩ If rejected, review rejection page and evaluate reasons. → Revise as necessary and reapply. ✓ Once approved, Developer token granted Standard Access. | ✩ Review feature list regularly and identify any requirements not met with a due date. → [Complete change to permissible use form](https://support.google.com/adspolicy/contact/tool_change) to provide screenshots of requirements being met. ✓ Maintain standard access. |\n\n### Additional requirements\n\nThe last step before putting your Performance Max integration into production is\nto ensure the following:\n\n- Your developer token uses the appropriate access level, as described in\n [Access Levels \\& Permissible Use](https://developers.google.com/google-ads/api/docs/access-levels). For details about non-compliance fees,\n see [Rate Sheet and Non-Compliance Fees](https://developers.google.com/google-ads/api/docs/rate-sheet). Credentials for accessing Google's\n OAuth2 servers are also required as described in [*4.1.1 OAuth*](/merchant/storebuilder/online/sections/4_1_1_oauth).\n\n- The software you propose to use with the Google Ads API is in compliance with\n our [Terms and Conditions](https://developers.google.com/google-ads/api/terms) and [Required Minimum Functionality](https://developers.google.com/google-ads/api/docs/rmf) (RMF),\n described in this step.\n\n- Since your company manages advertiser accounts for clients, you must be in\n compliance with our [Third Party Policy](https://support.google.com/adspolicy/answer/6086450) to gain access to the Google Ads\n API for production use.\n\n- In Europe, merchants can participate in Shopping ads through one or several\n [Comparison Shopping Services](https://support.google.com/merchants/topic/9080307) (CSSs) of their choice, including Google\n Shopping (Google's CSS).\n\n| **Ads API Best Practices** \n| The [Google Ads API best practices guide](https://developers.google.com/google-ads/api/docs/best-practices/overview) covers some best practices you can implement to optimize the efficiency and performance of your apps, including [batch processing](https://developers.google.com/google-ads/api/docs/batch-processing/overview)."]]
