Google Ads V2 Export Integration

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

There are several Google Ads integrations available. This article describes Google Ads Remarketing V2.

You can export user profiles, such as email or phone numbers, directly into the Google Ads Remarketing user list by leveraging this integration. Execute your TD SQL query job results to upload CRM data in bulk, and append or remove data to a Google Remarketing user list.

You can export the data for the userId column. And you can remove users from existing segments.

Prerequisites

• Basic knowledge of Treasure Data, including the TD Toolbelt.
• A Google Ads Account.
• Authorized Treasure Data Google OAuth app access to your own Google Ads account. In your Google Ads account, your access level needs to be Standard or Admin.

Limitations

The following limitations are described in the Google Ads API document "Remarketing and Audience Targeting" and the Support articles.

• Minimum of 5000 users. Advertisements are served to user lists that have at least 5000 users. See the section "Customer Match Limitations." The document states: "Upload at least 5,000 members to the list to ensure that ads start serving."

• Google Account email. An email must be connected using Google Account. See the section "Customer Match with email address, address, or user ID."

• Non-@gmail.com addresses ignored. Only emails with the form @gmail.com can be used for targeting in Gmail. See the section "Customer Match with email address, address, or user ID."

• User list rounding. On the Google Ads manager site, the number of user list is not precisely displayed:

  • It is rounded to a hundred if the number of users is less than 1000.
  • Is rounded to the 2 most significant digits otherwise. See the section "Customer Match Limitations."

• Google Display Network customer match. Customer match is not available for third-party sites within Google Display Network. See the section "Customer Match with email address, address, or user ID."

• 48-hour delay. It takes up to 48 hours for Google to populate new users to the list. See the section "Note" from https://support.google.com/google-ads/answer/7474263.

• If you run replace mode, it may run for up to 72 hours. See Remove data from a Customer Match audience list.

Column Naming

Output results must use predefined column names. Supported column names are:

• mobile_id: IDFA (Identifier for Advertising) or AAID (Google Advertising ID) mobile device IDs. Example: AEBE52E7-03EE-455A-B3C4-E57283966239 (the format is: 8-4-4-4-12 hex characters)
• email: Email addresses
• phone_number: Phone numbers
• user_id: Advertiser generated and assigned user ID. To use this feature, you need to be a whitelisted Google account. For more information visit Customer Match Policy.

If no supporting columns are found in the query result, you receive an error. The column alias is case-insensitive, for example, you can use email or EMAIL.

You have to use aliases in your query if column names don't match supported values. For example:

SELECT an_email_column AS email,another_phone_column AS phone_numberFROM your_table;

Data Normalization and Hashing

Treasure Data's result output normalizes and hashes your values automatically to follow Google’s formatting and privacy guidelines. The only hashing algorithm supported is SHA-256.

CRM data must follow specific formatting guidelines to be accepted. Incorrect formatting can lead to an upload error or a low number of matched records.

The following conversion behavior is applied, according to data type, during result output for normalization.

• Mobile Advertising ID: no normalization.

• Email:

  • If data is plain text, trim leading and trailing whitespaces, convert all characters to lowercase, then hash before sending
  • If data is already hashed, apply no conversion

• Phone Number: use the E.164 format, for example, +1234567890

  • If data is plain text, hash the value
  • If data is already hashed, apply no conversion

• User ID: no normalization.

Google Ads Policies

Treasure Data encourages you to adhere to Google Ads policies, in particular:

• Google Ads Policy for Personalized Advertising
• Google Ads Policy for Customer Match: upload only customer information that you collected in the first-party context

Use TD Console

Create a New Connection

In Treasure Data, you must create and configure the data connection prior to running your query. As part of the data connection, you provide authentication to access the integration.

1. Open TD Console.
2. Navigate to Integrations Hub > Catalog.
3. Search for and select Google Ads V2.

4. Select Create Authentication. Optionally, create an authentication via an activation in the Audience Studio.
5. Select the credentials to authenticate.

6. Optionally, select Click here and log in to Google.

7. Return Integrations Hub > Catalog.
8. Search for and select Google Ads.
9. Select New Authentication.
10. Review the OAuth connection field definition.
11. Select Continue.
12. Type a name for your connection.
13. Select Done.

Define your Query

Output results must use predefined column names.

You must query the user_id column to upload the user_id to Google.

Treasure Data's result output normalizes and hashes your values automatically to follow Google’s formatting and privacy guidelines. The only hashing algorithm supported is SHA-256.

1. Complete the instructions in Creating a Destination Integration.
2. Navigate to Data Workbench > Queries.
3. Select a query for which you would like to export data.
4. Run the query to validate the result set.
5. SelectExport Results.
6. Select an existing integration authentication.

7. Define any additional Export Results details.

8. Select Done.

9. Run your query.

10. Validate that your data moved to the destination you specified.

Integration Parameters for Google Ads Remarketing V2

Example Query

From TD Console, Queries page, run a query similar to the following with output results specified to go into the Google Ads connection. The query is an example only.

SELECT
  email,
  phone_number
FROM
  (VALUES ('demo1@example.com', '+1234567890'), ('demo2@example.com', '+9876543210'),('demo3@example.com', '+9988776655')) tbl (email, phone_number)

The above query uses sample values; you must choose a database and tables like following.

SELECT email FROM app_users

Your query can include:

• Only mobile_id
• Only email and/or phone_number
• Only user_id
• All other columns are ignored

The query should be complete in a few seconds.

Optionally Validate your Query Results

Validate your Audience List to view the newly populated data:

(Optional) Schedule Query Export Jobs

You can use Scheduled Jobs with Result Export to periodically write the output result to a target destination that you specify.

Treasure Data's scheduler feature supports periodic query execution to achieve high availability.

When two specifications provide conflicting schedule specifications, the specification requesting to execute more often is followed while the other schedule specification is ignored.

For example, if the cron schedule is '0 0 1 * 1', then the 'day of month' specification and 'day of week' are discordant because the former specification requires it to run every first day of each month at midnight (00:00), while the latter specification requires it to run every Monday at midnight (00:00). The latter specification is followed.

Scheduling your Job Using TD Console

1. Navigate to Data Workbench > Queries

2. Create a new query or select an existing query.

3. Next to Schedule, select None.

4. In the drop-down, select one of the following schedule options:

   Drop-down Value	Description
   Custom cron...	Review Custom cron... details.
   @daily (midnight)	Run once a day at midnight (00:00 am) in the specified time zone.
   @hourly (:00)	Run every hour at 00 minutes.
   None	No schedule.

Custom cron... Details

 *    *    *    *    *
 -    -    -    -    -
 |    |    |    |    |
 |    |    |    |    +----- day of week (0 - 6) (Sunday=0)
 |    |    |    +---------- month (1 - 12)
 |    |    +--------------- day of month (1 - 31)
 |    +-------------------- hour (0 - 23)
 +------------------------- min (0 - 59)

The following named entries can be used:

• Day of Week: sun, mon, tue, wed, thu, fri, sat.
• Month: jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec.

A single space is required between each field. The values for each field can be composed of:

1. (Optional) You can delay the start time of a query by enabling the Delay execution.

Execute the Query

Save the query with a name and run, or just run the query. Upon successful completion of the query, the query result is automatically exported to the specified destination.

(Optional) You can delay the start time of a query by enabling the Delay execution.

Activate a Segment in Audience Studio

You can also send segment data to the target platform by creating an activation in the Audience Studio.

1. Navigate to Audience Studio.
2. Select a parent segment.
3. Open the target segment, right-mouse click, and then select Create Activation.
4. In the Details panel, enter an Activation name and configure the activation according to the previous section on Configuration Parameters.
5. Customize the activation output in the Output Mapping panel.

• Attribute Columns
  • Select Export All Columns to export all columns without making any changes.
  • Select + Add Columns to add specific columns for the export. The Output Column Name pre-populates with the same Source column name. You can update the Output Column Name. Continue to select + Add Columnsto add new columns for your activation output.
• String Builder
  • + Add string to create strings for export. Select from the following values:
    • String: Choose any value; use text to create a custom value.
    • Timestamp: The date and time of the export.
    • Segment Id: The segment ID number.
    • Segment Name: The segment name.
    • Audience Id: The parent segment number.

6. Set a Schedule.

• Select the values to define your schedule and optionally include email notifications.

7. Select Create.

Troubleshooting

Question: After one or two days of having the status of 'Populating', my user lists status changes to 'Error with the last upload'. Why is that?

Answer: During our tests, it seems that Google API has this issue when you upload multiple lists at the same time. The number of user lists that can cause an issue is unknown, but you should limit your uploads to 3 to 5 user lists at a time.

Question:  Why does the value of Size for my user lists keep changing?

Answer: According to our observation, the size of each network might change daily, based on the number of active users:

Question:  Why do my lists have the status: 'Populating...'?

Answer: It takes 6 to 12 hours for a list to be populated with members, so you'll most likely see a "Populating..." status on the Ads UI if you upload to an audience list more frequently than once every 12 hours. In most cases, it can take up to 48 hours until the list becomes finalized.

Question:  Even though we set a user who has enough permission, got "Caused by: io.grpc.StatusRuntimeException: PERMISSION_DENIED: Request had insufficient authentication scopes." error. Why is that?

Answer: The set user would be MCC account. You have to use your Google account because the MCC account is for management, and it doesn't have enough permission for export jobs completion.

Question:  Is there an alternative for synchronizing the opt-out user list? Our list are updated daily, and it's difficult to manage with up to 48 hours of delay for the list to be replaced and updated.

Answer: You can utilize the Membership Lifespan parameter. For example, you can set this value to 3 days (which means all audiences which have not been updated are automatically removed after 3 days). If you were to upload an existing audience again the next day, the time would be reset. However, be aware of the "up to 48 hours of delay" as you use the Membership Lifespan parameter.

Optionally Configure Export Results in Workflow

Within Treasure Workflow, you can specify the use of a data connector to export data.

Learn more at Using Workflows to Export Data with the TD Toolbelt.

Example Workflow - Append user_id to UserList

_export:
  td:
    database: google_ads_v2_db

+google_ads_v2_export_task:
  td>: append_user_id.sql
  database: ${td.database}
  result_connection: new_created_google_ads_v2_auth
  result_settings:
    type: google_adwords_v2
    client_customer_id: "xxx-yyy-zzzz"
    name: "test_append_user_id"
    mode: "append"
    ad_user_data_consent: "granted"
    ad_personalization_consent: "denied"

Example Workflow  - Remove user_id from UserList

_export:
  td:
    database: google_ads_v2_db

+google_ads_v2_export_task:
  td>: remove_user_id.sql
  database: ${td.database}
  result_connection: new_created_google_ads_v2_auth
  result_settings:
    type: google_adwords_v2
    client_customer_id: "xxx-yyy-zzzz"
    name: "test_remove_user_id"
    mode: "remove"
    ad_user_data_consent: "granted"
    ad_personalization_consent: "denied"

Learn more at Using Workflows to Export Data with the TD Toolbelt.