Configure Google Ads as a Source in your Pipeline

Perform the following steps to configure your Google Ads Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select Google Ads.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. On the Select Pipeline Type page, click Edge, and then click Continue.

   

   Note: This page appears only if the selected Destination type is supported in Edge and your Team has an existing Google Ads Pipeline with the same Destination type. Otherwise, you can proceed to create an Edge Pipeline.

6. In the Configure Source screen, specify the following:

   

   Connect to your Google Ads account

   

   • Click Authenticate your Google Ads account, log in to your Google Ads account, and click Allow to grant Hevo access to your account.

   • Customer ID: The 10-digit customer ID of the Google Ads account that you obtained, containing the data you want to sync.

   Accounts to sync

   • Select Google Ads Account: Choose whether to sync data from all accessible accounts, only specific accounts, or every child account under a specific manager (MCC) account. Default value: Sync all accounts.

     • Sync all accounts: Hevo syncs data for all ad accounts accessible to your authorized Google Ads account, including any accounts added later.

     • Sync specific accounts: Hevo ingests data only for the accounts you select from the Accounts to sync drop-down.

       

     • Sync by manager accounts: Hevo ingests data from every child account under the manager (MCC) accounts you select from the Manager accounts to sync drop-down.

       

       Note: Only the child accounts directly under the selected manager (MCC) accounts are synced. If a selected manager account contains sub-manager accounts, their child accounts are not synced automatically. To sync those accounts, select the relevant sub-manager accounts separately.

   Sync Settings

   • Historical Sync Duration: The duration for which you want to ingest existing data from the Source. This cannot be changed after the Pipeline is created. Default duration: 12 Months.

   Advanced Options

   • Show Advanced Options: Enable this toggle to reveal optional settings that fine-tune how stats are re-fetched. These settings are only necessary in specific cases. Default value: Off.

     • Conversion Window Size (optional): The duration during which a conversion is recorded. Select Auto if you want the window size to be detected automatically. Default value: 30 days.

   Custom Reports (optional)

   • Custom Reports: Hevo allows you to create your own reports by choosing a valid combination of metrics and dimensions. Each report syncs to its own Destination table. For each report, specify the following:

     

     • Destination Table: Specify a unique name for the Destination table where Hevo loads the data for this report.

     • Report Type: The type of Google Ads data to include in the report. The fields available for the report are based on the value in this field. Default: ad_group.

     • Report Fields: The fields to include in the report. You can choose a report template to automatically add fields, or select them manually. The available fields depend on the selected Report Type value.

     Note:

     • Click Save to add each report. Any report that is not saved before you click Test & Continue is not included in the Pipeline.

     • If you add a new custom report or edit an existing one after the Pipeline is created, resync the corresponding object to apply the changes and load the data using the updated configuration.

7. Click Test & Continue to test the connection to your Google Ads Source.

   Note: If any custom report is configured incorrectly, such as with an unsupported field combination, an invalid aggregation, or a duplicate table name, clicking Test & Continue fails the Source configuration. Hevo lists all configuration issues in your custom reports. You can fix these issues by editing the reports before retrying.

---

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline.

Hevo ingests the following types of data from your Source objects:

• Historical Data: The first run of the Pipeline ingests all available historical data for the selected objects, for the duration specified in the Historical Sync Duration field, and loads it into the Destination.

• Incremental Data: Once the historical load is complete, new and updated records for objects are ingested as per the sync frequency.

For the following objects, Hevo re-fetches data within the configured Conversion Window Size to capture delayed conversions:

• account_stats

• account_hourly_stats

• ad_group_stats

• ad_group_hourly_stats

• ad_stats

• audience_stats

• campaign_stats

• campaign_hourly_stats

• click_stats

• keyword_stats

• landing_page_stats

• search_keyword_stats

• search_term_keyword_stats

• search_term_stats

For the following objects, Hevo ingests only the incremental data in subsequent Pipeline runs:

For the following objects, Hevo ingests the entire data during each Pipeline run:

• account_history

• account_label_history

• campaign_budget_history

• campaign_bid_modifier_history

• campaign_conversion_goal_history

• ad_group_label_history

• ad_group_criterion_label_history

• campaign_label_history

• ad_label_history

• audience

• combined_audience

• custom_audience

• geo_target

• label

• mobile_device

• operating_system_version

• topic

• user_interest

• user_list

Note: The geo_target table is synced once every 15 days.

Google Ads API enforces rate limits using a token bucket algorithm, applied independently for each developer token and each linked account. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

You can create a Pipeline with this Source using either the Merge or Append load mode.

---

Schema and Primary Keys

Hevo uses the following schema to upload the records to the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

---

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

---