Google Ads

Last updated on Mar 05, 2024

From Release 2.18 onwards, Hevo supports Google Ads API V15, which contains new and enhanced reporting capabilities. We recommend that you upgrade your existing Pipelines to Google Ads API V15 before January 15, 2024, for uninterrupted data replication. Refer to section, Migrating Pipelines to Google Ads API V15 to know about the updates in reports and the steps to upgrade the Pipeline.

Google Ads is an advertising platform by Google that allows businesses to create ads for their products and services. It also provides statistics for these ads to gather insights and grow your business faster.

Hevo uses the Google Ads API to ingest data from your Google Ads account and replicate it into the Destination of your choice. The Google Ads API is the next generation of Google AdWords API. It provides you with new features and improvements over the AdWords API that make it easy for you to manage large and complex accounts.


Source Considerations

  • Google Ads does not support custom metrics and dimensions in the reports.

  • For custom reports, you can only select the metrics and dimensions that are compatible with the segments you select. Read Segments to know more about the segments in Google Ads, and the metrics and dimensions compatible with these segments.

  • The Google Ads API does not return any Events in the report if an ad did not get any impressions. Therefore, the schema for that ad is not created in your Destination. This is because the Google Ads API does not support the includeZeroImpressions parameter.

  • The Google Ads API uses a querying approach to fetch data from your Google Ads account. Therefore, there are no readily available reports in Google Ads. Hevo aggregates the data in your Google Ads account and generates a report using the segments, dimensions, and metrics of the various resources in your account. It results in a higher number of ingestions for your Hevo Google Ads Pipeline. For example, let us say, while setting up your Pipeline in Hevo, you also set the aggregation window as last 30 days for 100 reports, and the ingestion frequency as 1 hour. Then, the number of reports ingested every 1 hour would be 30 x 100 = 3000 reports. In one day, the number of reports ingested would be 3000 x 24 = 72000 reports. As a result, the number of Events ingested per day is high.

  • Google Ads has removed support for exporting data for some Gmail-related metrics in the Ad Group Ad report in Version 12 of their API. As a result, from Release 2.09, Hevo does not support the ingestion of historical data for these metrics, and all existing Pipelines containing these metrics now load null values for these fields. Read Ad Group Ad to know about the metrics supported for this report in v12 of the Google Ads API.


Limitations

  • Hevo does not fetch data for the metrics that are not filterable by the segment, date.


Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Mar-05-2024 2.21 Updated the ingestion frequency table in the Data Replication section.
Nov-28-2023 2.18 - Added section, Migrating Pipelines to Google Ads API V15.
- Updated the page to add information about Google Ads API V15.
Jul-21-2023 NA Updated the page to add information according to the latest Hevo functionality.
Apr-04-2023 NA Updated section, Configuring Google Ads as a Source to update the information about historical sync duration.
Mar-09-2023 2.09 - Updated section, Source Considerations to add information about Google Ads not exporting data for some metrics.
- Updated section, Data Model to update the links of the reports to Version 12 of the Google Ads API.
Jan-10-2023 NA Updated section, Data Model to add descriptions for reports.
Oct-25-2022 2.00 Added the section, Granting Access to your Google Ads Account with steps to provide other users access to the Google Ads account.
Sep-21-2022 NA New document.

Tell us what went wrong