Stay organized with collections
Save and categorize content based on your preferences.
4.0.4 Access Levels and Required Minimum Functionality (RMF)
Value and Business Impact
Your Google Ads API developer token has multiple access levels.
Access Levels & Permissible Use provides an overview about these access
levels. To summarize:
Test account access: Execute up to 15,000 operations and make up to
1,000 requests per day using only test accounts. Once you complete the
Google Ads API sign up, you are issued a developer token set to this
level. See the test account guide to learn more about how to create a test
account.
Basic access: Execute up to 15,000 operations and make up to 1,000
requests per day using test and production accounts. This is the default access
level for all approved developer tokens. Production accounts are any accounts
that serve real, live Google ads (test accounts don't serve ads). To apply, see
Applying for Basic access.
Standard access: Execute unlimited operations and up to 1,000 requests
per day using test and production accounts. For details of limits and
exceptions, see API quotas. If you have basic access level and you would
like to apply for unlimited Google Ads API operations, fill out the
standard access application form.
This form asks you detailed
questions about the design of your software that uses the API, and also asks
for design documents of your software. Note that "MCC" in this application
refers to the Google Ads manager account.
Most partners need the Standard access level to scale their solution. The
recommended approach is to gain Basic access during early development and
testing. Then, a few weeks before you release your Performance Max integration
into production, you would apply for Standard access and demonstrate that you
meet the requirements for it (see next section).
Required Minimum Functionality (RMF)
Required Minimum Functionality (RMF) refers to the features and other
functionality that certain application developers must offer when using the
Google Ads API. RMF applies only to tokens with Standard access.
As an ecommerce provider managing multiple merchant accounts for Performance
Max advertisers, you are only required to implement the Google Ads API creation
and management features and reports listed in the
Performance Max Campaign feature list. Additionally, you must make
reasonable effort to ensure that each of the features is accessible and
functional.
RMF process for Standard access
The following summarizes the steps to gain Standard access and maintain
compliance:
Since your company manages advertiser accounts for clients, you must be in
compliance with our Third Party Policy to gain access to the Google Ads
API for production use.
In Europe, merchants can participate in Shopping ads through one or several
Comparison Shopping Services (CSSs) of their choice, including Google
Shopping (Google's CSS).
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-09-03 UTC."],[[["\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)."]]
