Beginning on February 15, 2022, Supermetrics has been migrating its services to the new Google Ads API.
The changes impacted all report types Supermetrics supports.
We have also updated the account discovery and fetch system with one that uses Google Ads API, which does not support all account types. This means you might have to make some adjustments to your Google Ads queries.
The Google Ads API doesn't support some of the fields that the previous one did.
If you're using any of these fields, please update your queries to remove them — they'll stop returning data otherwise.
- Average frequency
- Average position
- Bidding strategy source
- Click assisted conversions
- Click assisted conversion value
- Impression assisted conversions
- Impression assisted conversion value
- Impression reach
- Max CPA
- Free clicks
- Free click rate %
- Organic average position
The following reports are not supported in the Google Ads API and will be removed from the data source by April 27, 2022. We'll redirect the request to another relevant report type, based on the other fields selected, as we can no longer request data for the unsupported report types.
- Creative Conversion
- Campaign Group Performance
- Campaign Negative Placements Performance
- Campaign Negative Keyword Performance
Search Ads 360
Changes to account discovery mean that Search Ads 360 accounts (search engine accounts) will no longer be supported. These will be removed from the account drop-down, and any queries specifically requesting an account ID for one of these will fail. To prevent errors, you'll need to update your queries to remove these accounts.
- If you use the All Accounts setting, any Search Ads 360 accounts will be removed from your queries automatically. If a query specifically requests an account, it will need to be modified to remove that account ID.
- If you're unsure if you have any Search Ads 360 accounts in your account list, you can contact Google Ads help for assistance.
- If you still need to retrieve data from your Search Ads 360 accounts, Supermetrics offers a Google Search Ads 360 data source. Contact our sales team to talk about adding this data source to your plan.
Changes to Geographic reporting
There are major differences in how location data is aggregated between the AdWords and Google Ads APIs. This will impact what data is returned and could affect reports, especially if they depended on how the AdWords API handle it.
With the older API, combining several geographic fields in the same query (such as Country and City) would still return a row and calculate the unknown values even if there was no given values for one of those fields.
Example before migration:
However with the newer API, any empty values in the geographic dimensions will cause the whole row to be complete removed from the results.
Example after migration:
Note that the Finland row with no given city was removed from the data.
This change in behavior due to design decision by Google for the new API and should align results more closely to reporting UI in Google Ads. We realize this could be a very impactful change, with whole rows of data for unknowns not being returned by the API. So we will delay deploying the report until April 13th, 2022 to give time to make adjustments
To work around this, queries can be set to the single most important geographic dimension to ensure all possible rows are returned.
We also fixed the behavior of the "Enable user location view" setting to correctly return the user location-based data rather geographic location. With that setting enabled, data must be checked against the User location version of the location reporting, as it will not match the Geographic version.
Changes to Paid & Organic reporting
This report will be migrated on May 25th to the Google Ads API. The new API calculates this differently and to ensure that it aligns with Google Ads, both the query and the UI reporting should contain these dimensions:
- Search result type
- Matched search term
Failure to include these will lead to different aggregation being used and cause significant discrepancies.
Learn more: Changes and updates
As Supermetrics will pull data from a new version of Google Ads API, some fields will behave differently than when we used the older version of the API. Read about these changes below.
Changes in dimension values/categories
Some dimensions may report slightly different (and more current) values that what the AdWords API reports. Read our reference guide to learn about all the dimensions with values and what they've changed to.
We tried to maintain the existing mapping whenever possible, but in some cases it wasn't possible to keep it the same. If you were using filtering on any dimensions that return values (like Ad type, Network, or Campaign status, for example), check what the "new display value" column says and update any that haven't changed.
Incompatible field errors
While the old version of the API returned no data when a query used incompatible fields, the new API will show an incompatible fields error.
It is known that the "Slot" dimension is no longer compatible with video metrics. This is a new limitation in the Google Ads API.
"Product Title" currently does not work with impression share metrics due to compatibility issues. Use "Offer ID" instead. We will be investigating this post-migration to see if we can restore the compatibility.
Metrics with non-specific values (<10%)
Some metrics natively report as "< 10%" from the AdWords API. Those will now report as the actual values from these reports.
New functionality not yet supported
Not all fields that can be supported by the new API are for these reports. We are focusing on replicating existing functionality from AdWords into Google Ads API to ensure queries continue to work after the deprecation. We will evaluate adding new fields and functionality at a later time.
The new Google Ads API doesn't support the feature to "Include Zero Impressions", so we've replicated that behavior ourselves by filtering the data if "Enable zero impression rows" is not checked. It works slightly differently than the native feature in the old API, so there may be slight differences in how the data is returned.
One notable difference is that queries that contain segments (date, country, product, etc.) will not return data for rows that have all 0 metrics. They are simply missing from the data the API returns, so in those cases, even using "Include Zero Impressions" will not make those rows appear.