Introduction

Find out how the differences between the new Google Ads API and old Adwords API connectors be resolved.

• Recommendations to Resolve Differences
• Causes
  1. Segments with null values will not return rows in the report
  2. Report Types are now Resources
  3. Differences in fields
  4. More available campaign types
  5. Label data in reports is synced differently
  6. Other changes and differences

Environment

Connector: Google Ads - Using the new Google Ads API vs the old Adwords API

Recommendations to Resolve Differences

Data match between the Fivetran synced report data and the UI report

Build the report in the Google UI Report Editor using the same fields that are configured in the connector report.

Data match with the old API report and new report

If you are seeing a reduction in records or summed values (Cause 1 below), the solution is to recreate the report with only the segments.date fields configured to ensure all rows are returned.

• If you want to sync data for the other segments, you can create another report for each segment.
  Note: You always need to include the segments.date field.
• If needed to view a report with multiple segments together, create separate reports for each segment and join the outputted reports using your warehouse queries.

If you are seeing differences in the campaign metrics between the old and new API connectors (Cause 4 below):

1. Verify what the campaign channel subtypes are
2. Exclude the channel subtypes from your queries that are not present in both API's

To understand combinations of fields that will work together

Use the Google Ads Query Builder to build custom queries and verify if they will work successfully for your required report.

To view label data that was previously part of the report

Use the label table and *_label_history table to join it with your required report.

Causes

1. Segments with null values will not return rows in the report

If any of the segment values configured for a report have a null value, this will result in the row not returned. This will happen even if the other segments configured contain values. This is discussed in, Google Ads API Support Discussion.

Example

The old Adwords API "Geo Performance Report" and the new Google Ads API version of the report, "geographic_view" report contain differences for fields which now makes some of them Segments:

• The old report had Attributes of CityCriteriaId and RegionCriteriaId.
• The new report now has Segments of geo_target_city and geo_target_region respectively.

If these Segments are configured in the report and either contains a null value, no row will be returned in the report. If the old report Attributes were configured and contained a null value, a row with data would still be returned as other attributes and segments may contain values. 

2. Report Type is now Report Name

Instead of report types in the AdWords API, you have resources, such as campaign, and resource views, such as keyword_view in the Google Ads API.

Links:

• You can see all available resources at Google Ads API - Reports - List of all resources.
• To see the mapping of the old report types to new resources, refer to Google Ads API - Migration - Resource Mapping

3. Differences in fields

The new Google Ads API contains different field names and a change in the use of fields in some cases. To understand why your migrated report has different fields or how to create a new report matching an old one, refer to Google's 
If you want to create a report that is most similar to an AdWords report, refer to Google’s Field mappings for AdWords API reports.

4. More available campaign types

There are now more Campaign Types available from the new API that were not available with the Adwords API. There are also some Campaigns that are no longer available in the new API. 

For full info on this, see our Google Ads - Available Campaigns Documentation. 

5. Label data in reports is synced differently

Label data in reports is not synced in the same report. Reports are now Resources, and label data is synced in the ad_group_ad_label resource. 

As an example for the Ad Performance Report resource mappings, We can see the "Labels" field is now to be found in "Select label.name from the resource ad_group_ad_label". 
Fivetran does not sync the resource "ad_group_ad_label". Instead, the data can be found in the label table and *_label_history tables.

6. Other changes and differences 

For more info on Changes and Differences between the new Google API vs. older Adwords API, refer to our Google Ads API Documentation.