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 CampaignsWith 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 informationIf 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.
David Wihl, Google Ads API Team