## 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](https://developers.google.com/google-ads/api/docs/access-levels) provides an overview about these access levels. To summarize: - [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 1,000 requests per day using only test accounts. Once you complete the [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 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 account. - [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 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](https://developers.google.com/google-ads/api/docs/access-levels#applying_for_basic_access). - [Standard access](https://developers.google.com/google-ads/api/docs/access-levels#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](https://developers.google.com/google-ads/api/docs/best-practices/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](https://www.google.com/appserve/fb/forms/standardaccess/). 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](https://developers.google.com/google-ads/api/docs/rmf) (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](https://developers.google.com/google-ads/api/docs/access-levels#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](https://developers.google.com/google-ads/api/docs/rmf#performance_max_campaign_feature_list). Additionally, you must make reasonable effort to ensure that each of the features is accessible and functional. > [!NOTE] > **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. ### RMF process for Standard access The following summarizes the steps to gain Standard access and maintain compliance: ![steps](https://developers.google.com/static/merchant/storebuilder/images/blueprint/4_09_steps.png) | Active Token | Basic Access | Standard Access | Counter Rejections | Maintain Compliance | |---|---|---|---|---| | → [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](https://developers.google.com/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](https://developers.google.com/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. | ### Additional requirements The last step before putting your Performance Max integration into production is to ensure the following: - Your developer token uses the appropriate access level, as described in [Access Levels \& Permissible Use](https://developers.google.com/google-ads/api/docs/access-levels). For details about non-compliance fees, see [Rate Sheet and Non-Compliance Fees](https://developers.google.com/google-ads/api/docs/rate-sheet). Credentials for accessing Google's OAuth2 servers are also required as described in [*4.1.1 OAuth*](https://developers.google.com/merchant/storebuilder/online/sections/4_1_1_oauth). - The software you propose to use with the Google Ads API is in compliance with 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), described in this step. - Since your company manages advertiser accounts for clients, you must be in compliance with our [Third Party Policy](https://support.google.com/adspolicy/answer/6086450) 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](https://support.google.com/merchants/topic/9080307) (CSSs) of their choice, including Google Shopping (Google's CSS). > [!TIP] > **Ads API Best Practices** > 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).