Google Data Manager for Conversions Export Integration

The Google Data Manager for Conversions connector allows you to export conversion event data from Treasure AI directly to Google Ads. It uses the Google Data Manager API to upload Offline, Online, and Store Sales conversion events tied to conversion actions in your Google Ads account.

• Basic knowledge of Treasure AI, including the TD Toolbelt.
• A Google account with access to Google Ads.
• A Google Ads ID (operating account) with permissions to upload conversions.
• A Conversion Action ID configured in Google Ads.
• For Store Sales conversions: the Google Ads account must be on Google's allowlist.

• Each event may contain a maximum of 10 userIdentifiers entries.
• Address-based userIdentifiers require all four address fields for the same numeric suffix: first_name, last_name, region_code, and postal_code.
• IP address matching is not supported for users in the European Economic Area (EEA), United Kingdom (UK), or Switzerland (CH).
• For Store Sales conversions, Google removes the entire cartData object if any item is missing merchantProductId or unitPrice. The event is still accepted without cart data.
• Request status diagnostics require waiting at least 30 minutes after upload before checking, and may take up to 24 hours to finalize.

Before running your query, you must create and configure the data connection on the Treasure Console. As part of the data connection, you provide authentication to access the integration.

1. Open Treasure Console.
2. Navigate to Integrations Hub > Catalog.
3. Search for and select Google Data Manager for Conversions. Select Create Authentication.

4. Select the credentials to authenticate.

5. Optionally, select Sign in with Google and log in to Google.
6. Return to Integrations Hub > Catalog.
7. Search for and select Google Data Manager for Conversions.
8. The New Authentication dialog opens.
9. Select the OAuth connection with your account name in the dropdown list.
10. Select Continue.
11. Name the connection.
12. Select Done.

The Treasure Console supports multiple ways to export data. Complete the following steps to export data from Data Workbench.

1. Navigate to Data Workbench > Queries.
2. Select New Query and define your query.
3. Select Export Results to configure the data export.
4. Select an existing Google Data Manager for Conversions authentication or create a new one as described previously.
5. Configure the export parameters.
6. Select Done.

To upload conversion data to Google Ads, your export query must include a combination of required and optional columns. Column names are matched case-insensitively and whitespace is trimmed. Columns with NULL values are skipped for that record; if the column is required, the record is considered invalid.

These columns populate the userIdentifiers array on each event. Multiple identifiers can be provided using numeric suffixes (e.g., email, email1, email2). A record may contain at most 10 userIdentifiers entries total.

Email

Phone Number

Address Info (all four fields required per suffix)

Offline Conversion with gclid:

SELECT
    event_timestamp,
    event_source,
    gclid,
    transaction_id,
    conversion_value,
    currency,
    email
FROM conversions_tbl

Online Conversion:

SELECT
    event_timestamp,
    transaction_id,
    gclid,
    conversion_value,
    currency
FROM online_conversions_tbl

Store Sales Conversion:

SELECT
    event_timestamp,
    transaction_id,
    conversion_value,
    currency,
    store_id,
    email,
    phone_number,
    first_name,
    last_name,
    region_code,
    postal_code,
    merchant_id,
    merchant_feed_label,
    merchant_feed_language_code,
    cart_item_merchant_product_id,
    cart_item_quantity,
    cart_item_unit_price
FROM store_sales_tbl

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.

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.

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

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.

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.

The TD Toolbelt can trigger the Query Result exporting from a CLI. You need to specify the parameters for the exporting job using the --result option of the td query command. For more information, please refer to this article.

The format of the option is JSON, and the general structure is as follows.

{
  "type": "google_data_manager_for_conversions",
  "td_authentication_id": "${authentication_id_from_td_console}",
  "conversion_type": "OFFLINE",
  "operating_account_id": "123456789",
  "conversion_action_id": "your_conversion_action_id",
  "ad_user_data_consent": "CONSENT_GRANTED",
  "ad_personalization_consent": "CONSENT_GRANTED",
  "skip_invalid_records": true,
  "waiting_for_request_status": false
}

Offline Conversion Upload:

td query \
  --result '{"type":"google_data_manager_for_conversions","td_authentication_id":"xxxx","conversion_type":"OFFLINE","operating_account_id":"123456789","conversion_action_id":"conv-123","skip_invalid_records":true}' \
  -d my_database \
  "SELECT event_timestamp, event_source, gclid, conversion_value, currency FROM offline_conversions" \
  -T presto

Online Conversion Upload:

td query \
  --result '{"type":"google_data_manager_for_conversions","td_authentication_id":"xxxx","conversion_type":"ONLINE","operating_account_id":"123456789","conversion_action_id":"conv-123"}' \
  -d my_database \
  "SELECT event_timestamp, transaction_id, gclid, conversion_value, currency FROM online_conversions" \
  -T presto

Store Sales Upload:

td query \
  --result '{"type":"google_data_manager_for_conversions","td_authentication_id":"xxxx","conversion_type":"STORE_SALES","operating_account_id":"123456789","conversion_action_id":"conv-123"}' \
  -d my_database \
  "SELECT event_timestamp, transaction_id, conversion_value, currency, store_id, email FROM store_sales" \
  -T presto