In anticipation of Google permanently turning off their Adwords API on April 27th, we will be migrating to the new Google Ads API on Tuesday, April 26th.
Here's what you need to know:
- All field names are changing. We have mapped the data coming into Grow upon ingestion to the new field names. However, transforms and metric selections may still be referencing the old field names and will need to be updated to reference the new field names to avoid metric errors. Google provides a field mapping resource which you can use as a guide to update your metrics and transforms.
- Some fields will be deprecated. These fields will no longer be visible in your reports. See the previous post for a full list of deprecated fields. If you have any metrics that reference these fields, you will need to remove the field reference from the transforms to avoid metric errors.
- Google Ads API is moving to a new query language, GAQL. If you previously had one or more custom queries in Grow using the AdWords Query Language (AWQL), you will need enter your queries into Google's Query Migration Tool to generate an equivalent query in GAQL.
We have followed Google's migration guide to map all of the fields from Google AdWords API to the Google Ads API, to ensure that all existing metrics and datasets reference the same exact fields (minus the deprecated fields) before and after the migration. Keep in mind, deprecated fields will no longer be available after this migration.
Our migration ensures that the data will be coming into Grow properly with the new field names. However, we are not able to accurately migrate metric selections and transforms because of the differentiation in the field names and schema. This means that you will need to manually update your metrics and data transforms to use the new field names coming being brought into Grow from the new Google Ads API.
If you are experiencing any technical difficulties with your Google Ads connection on or after April 26th, please don't hesitate to send us an email to firstname.lastname@example.org and our team will be happy to assist you.
Please sign in to leave a comment.