Google Ads Import Integration V2

Copy

• Copy for LLM

  Copy page as Markdown for LLMs
• View as Markdown

  Open this page as Markdown
• Open in ChatGPT

  Get insights from ChatGPT
• Open in Claude

  Get insights from Claude
• Connect to Cursor

  Install MCP server on Cursor
• Connect to VS Code

  Install MCP server on VS Code

Google Ads is an online advertising platform that allows businesses to promote their products and services through digital ads across millions of Google partner websites and its services such as Google Search, YouTube, and Maps. This integration allows you to import Google Ads reports and metrics into Treasure Data to tailor-made your customer experiences, make data-driven decisions to optimize your campaigns, and achieve better marketing results

Prerequisites

• Basic knowledge of Treasure Data™
• Basic understanding of Google Ads performance data

Requirements and Limitations

• The import job could fail if the data is too big. Using paging could fix that problem.
• Google might change the default views of its performance data from time to time, thus the below pre-defined metric collection of each report type might not be the same as the corresponding reports found on the Google Ads. However, missing metrics could be added to fulfill the data requirement.
• This article doesn't intend to list all available attributes, segments, metrics, and explanations for them. For more details, please refer to Google Ads Query Builder, or the Report Editor feature which can be found on the Google Ads UI (Campaigns > Insights and reports > Report Editor)

Import from Google Ads via TD Console

You must create and configure the data connection on TD Console before importing data. As part of the data connection, you provide the OAuth authentication of your Google Ads account to deploy the integration using the following steps.

1. Open TD Console
2. Navigate to Integrations Hub > Catalog
3. Search for and select Google Ads V2
4. Select Create Authenticationand provide the OAuth of a Google account with access to the target Google Ads account
5. After being redirected back to the Integration Hub, repeat the above steps (this time your provided OAuth will be shown), enter a name for your authentication, and select Done.

Create a Source

1. Open TD Console
2. Navigate to Integrations Hub > Authentications
3. Locate your new authentication and select New Source
4. On the first step **1 - Connection**, type a source name in the Data Transfer Name field, and select Next

Identify a Source Table

Identify what data to be ingested into Treasure Data using the parameters below, and select Next.

This integration supports flexible ways to define your target data:

• Choose one of the 4 pre-defined report types, and pick up the desired Attributes, Segments, and Metrics. Or,
• Fill in a custom query valid for Google Ads to import necessary data. It is recommended to use this option together with the Google Ads Query Builder

Source Table Parameter

Source Table Parameter - Custom Query

Define Data Settings

Optionally, you can modify advanced data settings. Select Next to move to the next step.

Preview Your Data

• On the **4 - Data Preview** step, select Generate Preview to see an approximated view of your data before running the import (optional)
• Select Next to continue

Data Placement

For data placement, select the target database and table where you want your data placed and indicate how often the import should run.

1. Select Next. Under Storage, you will create a new or select an existing database and create a new or select an existing table for where you want to place the imported data.

2. Select a Database > Select an existing or Create New Database.

3. Optionally, type a database name.

4. Select a Table> Select an existing or Create New Table.

5. Optionally, type a table name.

6. Choose the method for importing the data.

   • Append (default)-Data import results are appended to the table. If the table does not exist, it will be created.
   • Always Replace-Replaces the entire content of an existing table with the result output of the query. If the table does not exist, a new table is created.
   • Replace on New Data-Only replace the entire content of an existing table with the result output when there is new data.

7. Select the Timestamp-based Partition Key column. If you want to set a different partition key seed than the default key, you can specify the long or timestamp column as the partitioning time. As a default time column, it uses upload_time with the add_time filter.

8. Select the Timezone for your data storage.

9. Under Schedule, you can choose when and how often you want to run this query.

Run once

1. Select Off.
2. Select Scheduling Timezone.
3. Select Create & Run Now.

Repeat Regularly

1. Select On.
2. Select the Schedule. The UI provides these four options: @hourly, @daily and @monthly or custom cron.
3. You can also select Delay Transfer and add a delay of execution time.
4. Select Scheduling Timezone.
5. Select Create & Run Now.

After your transfer has run, you can see the results of your transfer in Data Workbench > Databases.

Import from Google Ads via CLI (Toolbelt)

Prerequisites:

• TD Toolbelt: install the latest version of the TD CLI tool: TD Toolbelt
• Authentication ID: follow the steps above to create an Authentication for this integration on the TD Console. Then the ID could be seen at the last portion of its URL on the Authentication screen.

General steps:

1. Create a YML configuration file, ex: **load.yml**, referencing the created authentication in the `td_authentication_id' field. Refer to the below Parameter Reference and Example for more details
2. Preview the input data (optional) using the command: $ **td connector:preview** load.yml
3. Trigger the data import using the command: $ **td** **connector:issue** load.yml --database db-name --table table-name
4. Schedule the execution using the command: $ **td** **connector:create** daily\_import "10 0 \* \* \*" db-name table-name load.yml

Refer to this page for more reference information

Parameters Reference

Examples

Disable custom query

in:
  type: google_adwords_v2
  td_authentication_id: 330392
  enable_custom_query: false
  client_customer_id: xx-xxxx-xxxx
  target: AD_PERFORMANCE_REPORT
  date_range: "CUSTOM_DATE"
  include_predefined_metrics: false
  incremental: true
  start_date: 2020-03-01
  end_date: 2020-03-02
  segments: ["segments.date"]
  metrics: ["metrics.absolute_top_impression_percentage"]
out:
  mode: append

Enable custom query

in:
  type: google_adwords_v2
  td_authentication_id: 330392
  enable_custom_query: true
  client_customer_id: xx-xxxx-xxxx
  date_range: "CUSTOM_DATE"
  enable_date_range: true
  incremental: true
  start_date: 2020-03-01
  end_date: 2020-03-02
  select_columns: ad_group_criterion.criterion_id, ad_group.id, ad_group.name, segments.date
  from_target: keyword_view
  other_conditions: "AND ad_group_criterion.type = 'KEYWORD'"
out:
  mode: append

Use with Manager Ads Account

in:
  type: google_adwords_v2
  td_authentication_id: 330392
  enable_custom_query: true
  client_customer_id: xx-xxxx-xxxx
  login_customer_id: xx-xxxx-xxxx
  date_range: "CUSTOM_DATE"
  incremental: true
  start_date: 2020-03-01
  end_date: 2020-03-02
  select_columns: ad_group_criterion.criterion_id, ad_group.id, ad_group.name, segments.date
  from_target: keyword_view
  other_conditions: "AND ad_group_criterion.type = 'KEYWORD'"
out:
  mode: append

Import from Google Ads V2 via Workflow

You can import data from Google Ads by using the TD Workflow. Refer here for more detailed information.

How to convert Google Ads Query Language to a custom query in the connector

Query language reference: https://developers.google.com/google-ads/api/docs/query/overview?hl=en

Example:

SELECT
  campaign.id,
  campaign.name,
  campaign.status,
  metrics.impressions,
  segments.date,
FROM campaign
WHERE segments.date during LAST_30_DAYS
  AND campaign.status = 'PAUSED'
  AND metrics.impressions > 1000
ORDER BY campaign.id
in:        type: google_adwords_v2  enable_custom_query: true  client_id: xxx  client_secret: xxx  refresh_token: xxx  client_customer_id: xx-xxxx-xxxx  date_range: "LAST_30_DAYS"  developer_token: xxx  select_columns: campaign.id, campaign.name, campaign.status, metrics.impressions, segments.date  from_target: campaign  other_conditions: "AND campaign.status = 'PAUSED' AND metrics.impressions > 1000"
in:        type: google_adwords_v2  enable_custom_query: true  client_id: xxx  client_secret: xxx  refresh_token: xxx  client_customer_id: xx-xxxx-xxxx  login_customer_id: xx-xxxx-xxxx  date_range: "LAST_30_DAYS"  developer_token: xxx  select_columns: campaign.id, campaign.name, campaign.status, metrics.impressions, segments.date  from_target: campaign  other_conditions: "AND campaign.status = 'PAUSED' AND metrics.impressions > 1000"

Note: The query should have time and it should present the where condition, other_conditions  should start with AND as in the example.

Predefined Metrics

Available Date Ranges