Tag Archives: rmf

Google Ads API v10 RMF Update

Effective with Google Ads API version 10, we updated the Required Minimum Functionality (RMF) to use the Google Ads API. This is to reflect the evolution of the Google Ads platform, including the upgrade of Smart Shopping and Local Campaigns to Performance Max. We also published the requirements for Standard Shopping, Hotel-only and App Promotion-only tools.

There is a new product specific RMF for Smart Campaigns. This is not a requirement for all tools, only those that implement Smart Campaigns. If you use Smart Campaigns, this defines the minimum set of features that are required.

The minimum set of features for Performance Max campaigns are now available.

These changes will affect the following tools:
  • Shopping-only, Smart Shopping-only API tools
  • Special purpose tools that offer campaign creation or management functionality
These changes will not affect full-service, Hotel-only, App Promotion-only or reporting-only tools.

For precise details, see the updated Google Ads API Required Minimum Functionality.

Requirements for the AdWords API remain unchanged.

Standard Shopping Campaigns
With the release of Google Ads API v9, we simplified RMF requirements for Full-service tools. We are now making the same changes to Standard Shopping Campaigns.

The following features are still required but simplified or reduced in scope:
Item Number Functionality Change
C.190 Create ad group Optional: ability to create multiple ad groups
C.525 Add first (root) product partition This is a required step for creating a shopping campaign and it is done automatically. It is not separately invoked by the merchant. A new campaign should have a root partition otherwise it would not serve.
M.10 Edit campaign settings Only settings required at creation time would be required at change time (e.g. NetworkSettings would not be required to edit, since C.50 is no longer a requirement).
R.10 Customer Optional if only implementing one campaign.

The following features are no longer required. Developers may continue to use these features (unless already sunset), but they are no longer required in order to maintain compliance with the Terms & Conditions of using the Google Ads API. All these features, unless already sunset, are considered optional.

Item Number Functionality
C.14 Set mobile platform bid adjustment
C.15 Set tablet and desktop platform bid adjustments
C.21 Enable distance targeting
C.25 Set geo bid adjustment
C.50 Opt in/out of networks
C.90 Set bidding option: Manual CPC
C.95 Set bidding option: Enhanced CPC
C.101 Set bidding option: Maximize clicks (Portfolio)
C.140 Set delivery method
C.191 Set ad group max CPC bid
C.192 Set ad group max CPA
C.193 Set ad group target ROAS
C.320 Account-level tracking template
C.321 Campaign-level tracking template
C.325 Campaign-level custom parameters
C.326 Ad group-level custom parameters
C.328 Account-level final URL suffix
C.329 Campaign-level final URL suffix
C.700 Create ad group/campaign criterion that targets/excludes user list
C.710 Set userlist targeting bid adjustment for search network campaigns and ad groups
M.15 Edit mobile, tablet, and desktop platform bid adjustments
M.20 Edit ad group settings (all ad group-related required settings in Creation Functionality)
M.25 Edit geo bid adjustment
M.101 Edit bidding option: Maximize clicks (Standard)
M.120 Pause / enable / remove ad group
M.180 Edit product partition max CPC*
M.320 Manage all tracking templates in creation functionality
M.325 Manage all custom parameters in creation functionality
M.328 Manage all final URL suffixes in creation functionality
M.700 Edit ad group/campaign criterion that targets/excludes user list
M.710 Edit userlist targeting bid adjustment for search network campaigns and ad groups
R.30 Ad Group
R.80 Geographic View
R.150 Campaign Audience View
Ad Group Audience View

For more information
If you have questions specific to RMF, please contact the Google Ads API Compliance team at https://services.google.com/fb/forms/apicontact/.

If you have any questions or need additional help with the API, contact us via the forum.
, Google Ads API Team

Reducing RMF to help migration to the Google Ads API

Effective with the Google Ads API v9, we’re significantly reducing the Required Minimum Functionality (RMF) to use the Google Ads API. This is to help accelerate your migration to the new API prior to the sunset of the AdWords API on April 27, 2022 while decreasing the burden on your engineering team. Requirements for the AdWords API remain unchanged.

This will affect the following tools:
  • Full-service
  • Shopping-only, Smart Shopping-only, Hotel-only and App Promotion-only API tools
  • Special purpose tools that offer campaign creation or management functionality
  • Reporting-only tools
This will not affect Internal-only tools because they are not subject to RMF.

For precise details, see the updated Google Ads API Required Minimum Functionality.

The following features are not changing and are still required:
Item Number Functionality
C.10 Create campaign
C.96 Set bidding option: Target CPA (Portfolio and Standard)
C.97 Set bidding option: Target ROAS (Portfolio and Standard)
C.98 Set bidding option: Maximize Conversions (Standard)
C.120 Set budget
C.260 Add keyword
C.300 Set keyword match type
M.96 Edit bidding option: Target CPA (Portfolio and Standard)
M.97 Edit bidding option: Target ROAS (Portfolio and Standard)
M.98 Edit bidding option: Maximize Conversions (Standard)
M.110 Pause / enable / remove campaign
M.130 Pause / enable / remove ad
M.140 Pause / enable / remove keyword
R.40 Ad Group Ad
R.50 Keyword View
R.70 Search Term View
R.130 Bidding Strategy

The following features are still required but simplified or reduced in scope:
Item Number Functionality Change
C.20 Enable geo targeting Required. Optional to expose to the user if only one country is relevant for the user base.
C.30 Enable language targeting Required. Optional to expose to the user if only one language is relevant for the user base.
C.65 Create website / call conversion and generate code snippet Requires at least one type of conversion tracking.
C.75 Callout extensions Required account level only.
C.80 Callout extensions Required account level only.
C.190 Create ad group Optional: ability to create multiple ad groups.
C.270 Add ad group negative keywords Change from Ad Group level to Campaign level.
M.10 Edit campaign settings Only settings required at creation time would be required at change time (e.g. NetworkSettings would not be required to edit, since C.50 is no longer a requirement).
R.10 Customer Optional if only implementing one campaign.
R.20 Campaign Remove requirements for segments.ad_network_type and segments.device.
R.100 Dynamic Search Ads Search Term View Required only if implementing Dynamic Search Ads.

The following features are no longer required. Developers may continue to use these features (unless already sunset), but they are no longer required in order to maintain compliance with the Terms & Conditions of using the Google Ads API. All these features, unless already sunset, are considered optional.

Shopping-only features (indicated by *) are still required for shopping-only tools, but are no longer required for Full-service tools.
Item Number Functionality
C.14 Set mobile platform bid adjustment
C.15 Set tablet and desktop platform bid adjustments
C.21 Enable distance targeting
C.25 Set geo bid adjustment
C.41 Set Expanded Dynamic Search Ads
C.42 Set campaign DSA settings
C.50 Opt in/out of networks
C.70 Location extensions
C.72 App extensions
C.90 Set bidding option: Manual CPC
C.95 Set bidding option: Enhanced CPC
C.101 Set bidding option: Maximize clicks (Portfolio)
C.140 Set delivery method
C.191 Set ad group max CPC bid
C.192 Set ad group max CPA
C.193 Set ad group target ROAS
C.200 Add expanded text ad
C.290 Set keyword max CPC
C.311 Set keyword final URL
C.320 Account-level tracking template
C.321 Campaign-level tracking template
C.325 Campaign-level custom parameters
C.326 Ad group-level custom parameters
C.328 Account-level final URL suffix
C.329 Campaign-level final URL suffix
C.500 Create shopping campaign*
C.505 Set merchant identifier*
C.506 Set sales country*
C.510 Set inventory filter*
C.520 Create product ad*
C.525 Add first (root) product partition*
C.530 Local inventory ads*
C.610 Call ads
C.700 Create ad group/campaign criterion that targets/excludes user list
C.710 Set userlist targeting bid adjustment for search network campaigns and ad groups
M.15 Edit mobile, tablet, and desktop platform bid adjustments
M.20 Edit ad group settings (all ad group-related required settings in Creation Functionality)
M.25 Edit geo bid adjustment
M.35 Enable ad rotation
M.40 Edit keyword max CPC
M.100 Edit expanded text ad
M.101 Edit bidding option: Maximize clicks (Standard)
M.120 Pause / enable / remove ad group
M.150 Edit inventory filter*
M.160 Subdivide (add product partition)*
M.170 Remove product partition*
M.180 Edit product partition max CPC*
M.190 Exclude product partition (delegate)*
M.320 Manage all tracking templates in creation functionality
M.325 Manage all custom parameters in creation functionality
M.328 Manage all final URL suffixes in creation functionality
M.700 Edit ad group/campaign criterion that targets/excludes user list
M.710 Edit userlist targeting bid adjustment for search network campaigns and ad groups
R.30 Ad Group
R.80 Geographic View
R.110 Shopping Performance View*
R.120 Product Group View*
R.150 Campaign Audience View
Ad Group Audience View

* These features are not required for Full-service tools. Shopping-only RMF tools still need to implement these features.

If you have questions specific to RMF, please contact the Google Ads API.
If you have any questions or need additional help about the API, contact us via the forum.
, Google Ads API Team

Updated RMF Schedule and Non-Compliance Fees on the AdWords API Rate Sheet

If you're a software developer that builds tools for agencies or other advertisers to manage AdWords campaigns, or if you use the AdWords API to provide reporting dashboards to clients, please take a minute to review these updates.

In May 2014, we extended the deadline for all Required Minimum Functionality (RMF) until December 31, 2014. Now that the extension period has expired, we’d like to explain how we’ll review RMF in 2015. If you’re subject to RMF, you’ll receive emails in the days and weeks ahead explaining the details, so please be sure to update your contact information in the AdWords API Center of your MCC account.

At a high level, the review will look like this: first you’ll confirm your contact information and help ensure the demo account for your tool is working properly. Then, if any requirements are missing from your tool, you’ll receive a detailed non-compliance email followed by a 30-day “fix-it” period to bring your tool into compliance. We hope this will provide sufficient time to address any shortcomings. After that, if you’re not in compliance after the 30-day fix-it period, you’ll be subject to non-compliance fees (which have been reduced) as specified on the updated API rate sheet. And if you’re still not in compliance within 120 days of receiving the initial non-compliance email, your token may be downgraded to Basic Access. Throughout the process, we’ll send you reminder emails of the important milestones and deadlines.

Please note again that we’ve reduced the fees associated with non-compliance. You can see a full list of changes to the API rate sheet.

If you have any questions please feel free to reach out directly to the API Review Team.

-- AdWords API Team