Google Enhanced Conversion 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

This integration allows you to write Treasure Data job results directly in the Google Ads Server to improve the accuracy of your conversion measurements. It only works with existing conversions, and only supports website conversions.

Prerequisites

• Basic knowledge of Treasure Data, including the TD Toolbelt.
• Documentation: Google Enhanced Conversions Setup Guideline, Google Enhanced Conversions API doc
• A Google Ads Account.
• Authorize the Treasure Data Google OAuth app to access your Google Ads account. Otherwise, provide your Custom App information.

Requirements and Limitations

You must specify columns with exact column names (case sensitive) and data types.

Static IP Address of Treasure Data Integration

If your security policy requires IP whitelisting, you must add Treasure Data's IP addresses to your allowlist to ensure a successful connection.

Please find the complete list of static IP addresses, organized by region, at the following link:
https://api-docs.treasuredata.com/en/overview/ip-addresses-integrations-result-workers/

Use the TD Console to Create Your Connection

There are two ways to connect to Google Enhanced Conversion Export Integration. You can authorize the Treasure Data Google OAuth app or provide your Custom App information. |

Create a New Connection

You must create and configure the data connection in Treasure Data before running your query. You provide authentication to access the integration as part of the data connection.

1. Open TD Console.

2. Navigate to Integrations Hub > Catalog.

3. Search for and select Google Enhanced Conversion.

4. Select Create Authentication.

5. Select Data Provider. You can either select Treasure Data or User account.  If you select OAuth from the Authentication drop-down, click on Sign in with Google to authorize the connection. If you select Custom App from the Authentication drop-down, enter your credentials in the fields displayed. Select Continue.

6. Create a name for your authentication.

7. Select Done.

Define your Query

Your query should include the following:

• Required columns -
  • email or address (the address includes columns [first_name, last_name, street_address, city, region, postcode, country]) or both.
  • label or conversion_type or both.
  • conversion_time, conversion_tracking_id, oid.
• Optional columns - phone_number, value, currency_code, user_agent, gclid, pcc_game.
• Other columns will be ignored.

Required columns don't accept a null or empty value (else the record is considered invalid and skipped, or an error is thrown).

Email value must follow the pattern \S+@\S+.\S+.

Phone number (if any) must follow the pattern +\d{11,15}

The data type for different column names is listed below:

• String - mail, first_name, last_name, street_address, city, region, postcode, country, label, conversion_type, oid, phone_number, value, currency_code, user_agent, gclid.
• Long - conversion_time, conversion_tracking_id, pcc_game.

Note: Column names are case-sensitive and cannot be duplicated.

Integration Parameters for Google Enhanced Conversion

Example Query

custom object query

SELECT
  email,
  label,
  conversion_time,
  conversion_tracking_id,
  oid  
FROM your_table;

(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.

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.

With Authentication Method:  OAuth

_export:
  td:
    database: google_enhanced_conversion_db

+google_enhanced_conversion_export_task:
  td>: export.sql
  database: ${td.database}
  result_connection: new_created_google_enhanced_conversion_auth
  result_settings:    
    type: google_enhanced_conversion
    skip_invalid_records: true  

With Authentication Method:  Custom App

_export:
  td:
    database: google_enhanced_conversion_db

+google_enhanced_conversion_export_task:
  td>: export.sql
  database: ${td.database}
  result_settings:    
    type: google_enhanced_conversion
    client_id: "************************"
    client_secret: "************************"
    refresh_token: "************************"    
    skip_invalid_records: true