This integration allows you to write Treasure Data job results directly in the Google Ads Server to improve the accuracy of your conversion measurements.

This feature is in BETA. Contact your Customer Success Representative for more information.


Prerequisites

  • Basic knowledge of Treasure Data, including the TD Toolbelt.

  • 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

The static IP address of Treasure Data is the access point and source of the linkage for this Integration. Contact Technical Support or your Customer Success representative to determine the static IP address.

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 


Parameters

Description

Skip Invalid RecordsIf you check the errors as the data rows identify them, the export job continues and is successful. Otherwise, the job fails.

Example Query

custom object query
SELECT email, label, conversion_time, conversion_tracking_id, oid  FROM your_table;

Optionally Schedule the Query Export Jobs

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


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 ValueDescription
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.
NoneNo schedule.

Custom cron... Details

Cron Value

Description

0 * * * *

Run once an hour.

0 0 * * *

Run once a day at midnight.

0 0 1 * *

Run once a month at midnight on the morning of the first day of the month.

""

Create a job that has no scheduled run time.

 *    *    *    *    *
 -    -    -    -    -
 |    |    |    |    |
 |    |    |    |    +----- 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:

Field ValueExampleExample Description

A single value, within the limits displayed above for each field.



A wildcard ‘*’ to indicate no restriction based on the field. 

‘0 0 1 * *’ Configures the schedule to run at midnight (00:00) on the first day of each month.
A range ‘2-5’, indicating the range of accepted values for the field.‘0 0 1-10 * *’ Configures the schedule to run at midnight (00:00) on the first 10 days of each month.
A list of comma-separated values ‘2,3,4,5’, indicating the list of accepted values for the field.

0 0 1,11,21 * *’


Configures the schedule to run at midnight (00:00) every 1st, 11th, and 21st day of each month.
A periodicity indicator ‘*/5’ to express how often based on the field’s valid range of values a schedule is allowed to run.

‘30 */2 1 * *’


Configures the schedule to run on the 1st of every month, every 2 hours starting at 00:30. ‘0 0 */5 * *’ configures the schedule to run at midnight (00:00) every 5 days starting on the 5th of each month.
A comma-separated list of any of the above except the ‘*’ wildcard is also supported ‘2,*/5,8-10’‘0 0 5,*/10,25 * *’Configures the schedule to run at midnight (00:00) every 5th, 10th, 20th, and 25th day of each month.
5.  (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 imported to the specified container destination.

Scheduled jobs that continuously fail due to configuration errors may be disabled on the system side after several notifications.

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  
  • No labels