Google Campaign Manager Enhanced Conversions Export Integration

The Google Campaign Manager 360 (CM360) Enhanced Conversions connector allows you to export conversion data from Treasure AI directly to Google Campaign Manager 360. It uses the Campaign Manager 360 API to upload or update conversion records tied to Floodlight activities.

• Basic knowledge of Treasure AI, including the TD Toolbelt.
• A Google account with access to Campaign Manager 360.
• A Campaign Manager User Profile ID with permissions to upload conversions.
• The Floodlight Configuration ID and Floodlight Activity ID for the conversion actions you want to upload.

• Each conversion record may contain a maximum of 5 userIdentifiers entries. Records exceeding this limit are invalid.
• userIdentifiers entries must each contain exactly one identifier type: email, phone number, or address info. Mixing types within the same numeric suffix is not allowed and is enforced at schema validation time.
• Address-based userIdentifiers require all seven address fields for the same numeric suffix: first_name, last_name, city, state, country_code, postal_code, and street_address.
• The query schema must include exactly one conversion identifier column (or one group of encrypted_user_id_candidates* columns). Having zero or more than one identifier group is rejected at schema validation before any records are processed.
• When using encrypted user IDs (include_encrypted: true), the encryption_entity_id must be provided.
• Custom variable entries require both custom_variable_type and custom_variable_value for the same suffix.
• Cart data item entries require all three item fields for the same suffix: cart_data_item_id, cart_data_item_quantity, and cart_data_item_unit_price.

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 Campaign Manager Enhanced 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 Campaign Manager Enhanced 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 CM360 Enhanced Conversions authentication or create a new one as described previously.
5. Configure the export parameters.
6. Select Done.

To upload conversion data to Campaign Manager, 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.

*Only one of these fields must have a non-null value per record.

These columns populate the userIdentifiers array on each conversion, which is used for enhanced user matching. Multiple identifiers can be provided using numeric suffixes (e.g., email, email1, email2). Each suffix groups related fields into a single UserIdentifier entry. A record may contain at most 5 userIdentifiers entries total.

Each UserIdentifier entry must be one of the following types:

Email

Phone Number

Address Info (all seven fields required per suffix)

Cart data enriches conversion records with shopping cart information. When any cart data column is present, the three top-level cart data fields are required.

Top-level cart data fields (required when any cart data is used)

Cart data item fields (use numeric suffixes for multiple items)

Each set of three item fields grouped by the same numeric suffix represents one cart item. All three fields must be present for each suffix.

Custom variables can be attached to each conversion to pass additional data to Floodlight.

Both custom_variable_type and custom_variable_value must be present for each numeric suffix.

SELECT
    floodlight_configuration_id,
    floodlight_activity_id,
    timestamp_micros,
    value,
    quantity,
    ordinal,
    gclid,
    email,
    phone_number1,
    first_name2,
    last_name2,
    city2,
    state2,
    country_code2,
    postal_code2,
    street_address2,
    ad_user_data_consent,
    merchant_id,
    merchant_feed_label,
    merchant_feed_language,
    cart_data_item_id1,
    cart_data_item_quantity1,
    cart_data_item_unit_price1,
    custom_variable_type1,
    custom_variable_value1
FROM conversions_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_cm360_enhanced_conversions",
  "td_authentication_id": "${authentication_id_from_td_console}",
  "profile_id": "123456789",
  "mode": "ADD",
  "include_encrypted": true,
  "encryption_entity_type": "ENCRYPTION_ENTITY_TYPE_UNKNOWN",
  "encryption_entity_id": "123",
  "encryption_source": "ENCRYPTION_SCOPE_UNKNOWN",
  "skip_invalid_records": true
}

ADD mode (insert new conversions)

td query \
  --result '{"type":"google_cm360_enhanced_conversions","td_authentication_id": "xxxx","profile_id":"123456789","mode":"ADD","skip_invalid_records":true}' \
  -d my_database \
  "SELECT floodlight_configuration_id, floodlight_activity_id, timestamp_micros, value, quantity, ordinal, gclid FROM conversions" \
  -T presto

UPDATE mode

td query \
  --result '{"type":"google_cm360_enhanced_conversions","td_authentication_id": "xxxx","profile_id":"123456789","mode":"UPDATE","skip_invalid_records":true}' \
  -d my_database \
  "SELECT floodlight_configuration_id, floodlight_activity_id, timestamp_micros, value, quantity, ordinal, gclid FROM conversions" \
  -T presto