# Google Customer Match Export Integration

Customer Match enables businesses to match their owned and consented customer data with Google's extensive customer database, empowering them to engage with their customers through various Google platforms such as Search, the Shopping tab, Gmail, YouTube, and Display

This TD export integration enables the uploading of Customer Match data, such as user emails or phone numbers, directly to either Google Ads or Google Display & Video 360 (DV360) platform.

## Related Integrations

The TD Console provides a few integration options to upload the Customer Match data to Google platforms:

- [Google Ads V2](/int/google-ads-v2-export-integration): update audience data to Google Ads, using its API feature. Currently, there is a limitation that the mailing address which includes first name, last name, country code, and postal code is not supported
- [Google Display & Video 360 API](/int/google-display-and-video-360-api-export-integration): update audience data to DV360, using its API feature. Currently, the connector doesn't support user opt-out yet
- This integration has been implemented in such a way that Treasure Data is an official data partner of Google, and it solves all above mentioned limitations


## Prerequisites

- Basic Knowledge of Treasure Data™
- Basic knowledge of the [Customer Match](https://support.google.com/google-ads/answer/6379332?hl=en&ref_topic=10551292&sjid=7513164071054933331-AP) topic
- The user OAuth has direct admin access to the target Google Ads or DV360 account


## Requirements and Limitations

### Limitations

- Upload at least 5,000 members to increase the chance of having enough matched
- The user list size is displayed as zero until it reaches a minimum of 1,000 members. Beyond this threshold, the size is rounded to the nearest two significant figures
- It can take up to 24 hours for a list to be populated with members
- It is recommended to append audience data to a user list once per day
- Avoid running multiple uploading jobs of the same user list


### Requirements

It is recommended to follow Google's [policies](https://support.google.com/adspolicy/answer/6299717?hl=en) for Customer Match, in particular:

- A good history of policy compliance​
- A good payment history.
- Upload only customer information that you collected in the first-party context
- Restrictions on sensitive categories


## Use TD Console

### Create a new Connection

On TD Console, you must create and configure the data connection before running your query. As part of the data connection, you provide authentication to access the integration following the below steps

1. Open **TD Console**
2. Navigate to **Integrations Hub > Catalog**
3. Search for and select **Google Customer Match**
4. Select **Create Authentication**, and provide the credential information for the integration as described below
5. Select **Continue,**enter a name for the Authentication, and select **Done**.


### Authentication Fields

| Field Name | Type | Description |
|  --- | --- | --- |
| **Platform** (Required) | string | The target platform, Google Ads or Google Display & Video 360, to upload the audience data to |
| **OAuth Connection** (Required) | OAuth | Authorize from an account having ADMIN access to the target Google Ads (or DV360) account |


## Configure a Query Result for Export

The TD Console supports multiple ways to export data. Please follow the below steps to export data from the Data Workbench

1. Navigate to **Data Workbench > Queries**
2. Select **New Query**, and define your query
3. Select **Export Results** to configure the data exporting


![](/assets/screenshot-2024-05-27-at-13.08.60.c660e2874c5efd5898076c87205c9c1c3579e1232c32206db66443388b0163ee.9c1a955f.png)

1. Select an existing authentication, or create a new one following the above section
2. Configure the exporting parameters as described in the [Configuration Parameters](/int/google-customer-match-export-integration#h2_2111705584) below, and select **Done**


### Define your Query

Your query should include the required columns for the target Identifier type, other columns will be ignored. Required columns don't accept a null or empty value (else the record is considered invalid and skipped).

**Data requirement:**

- Normalization: all plain text data should be in lowercase, and be removed any extra spaces before, and after
- SHA-256 hashing: email, phone, first name, and last name should be hashed using the SHA-256 algorithm. If not, they are hashed automatically by the connector


| **Column name** | **Description** | Required |
|  --- | --- | --- |
| email | Only Google emails are considered in the matching process. | At least email ​or phone or mailing address is required for the `Contact information` identifier type.  The mailing address must includes all 4 columns [first_name, last_name, country_code, postal_code]. Phone must follow E.164 format. Visit https://en.wikipedia.org/wiki/E.164 for more detail. Country code must follow https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 |
| phone | The [E.164](https://en.wikipedia.org/wiki/E.164) standard is applied |  |
| first_name | Mailing address - first name. |  |
| last_name | Mailing address - last name. |  |
| country_code | Mailing address - country code (2-letter code in [ISO-3166-1 alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2)) |  |
| postal_code | Mailing address - postal code |  |
| mobile_id | Identifier for Advertising (IDFA) or Google Advertising ID (AAID) mobile device IDs | Required for the `Mobile Advertising ID` identifier type |


### Configuration Parameters

| Parameter Name | Type | Description |
|  --- | --- | --- |
| **Advertiser ID** (Required) | string | The ID of the target Google Ads account, or DV360 account, with or without dashes |
| **List name** (REQUIRED) | string | Name of the user list |
| **Mode** (REQUIRED) | string | The operation mode- **Add** (default): Query results are appended to an existing user list, or a new user list is created, if none exists by the specified List name.- **Remove**: Query results will be removed from an existing user list. |
| **Identifier type** (REQUIRED) | string | Two types of user identifiers are supported- **Contact information**: matching user profile using email, phone, or mailing address- **Mobile advertising ID**: matching user of a mobile application by uploading IDFA or AAID. If selected, the Application ID is mandatory |
| **Application ID** (OPTIONAL) | string | The ID of the mobile application. Required if Identifier type is **Mobile advertising ID** |
| **Membership days** (REQUIRED) | number | The number of days a user's contact information stays on the user list (if a value between 0 and 540 is specified). Default value: 10000 - no expiration |
| **Ad consent** (OPTIONAL) | string | Uploading data of the users from required regions, such as The European Economic Area, requires an explicit ad consent declaration |
| **Ad personalize consent** (OPTIONAL) | string | The consent flag for ad personalization |


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


![](/assets/ouput.b2c7f1d909c4f98ed10f5300df858a4b19f71a3b0834df952f5fb24018a5ea78.8ebdf569.png)

- 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 Columns**to 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.


1. Set a **Schedule**.


![](/assets/snippet-output-connector-on-audience-studio-2024-08-28.a99525173709da1eb537f839019fa7876ffae95045154c8f2941b030022f792c.8ebdf569.png)

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


1. Select **Create**.


If you need to create an activation for a batch journey, review [Creating a Batch Journey Activation](/products/customer-data-platform/journey-orchestration/batch/creating-a-batch-journey-activation).

## (Optional) Export Integration Using the 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](https://api-docs.treasuredata.com/en/tools/cli/api/#workflow-commands).


```yaml
_export:
  td:
    database: google_customer_match

+google_customer_match_export_task:
  td>: export.sql
  database: ${td.database}
  result_connection: new_created_google_customer_match
  result_settings:
    type: google_customer_match
    advertiser_id: 123456789
    list_name: test
    identifier_type: contact_info
    membership_life_span: 100
    mode: add
    ad_user_data_consent: granted
    ad_personalization_consent: granted
```


```yaml
_export:
  td:
    database: google_customer_match

+google_customer_match_export_task:
  td>: export.sql
  database: ${td.database}
  result_connection: new_created_google_customer_match
  result_settings:
    type: google_customer_match
    advertiser_id: 123456789
    list_name: test
    identifier_type: mobile_advertising_id
    app_id: test
    membership_life_span: 100
    mode: remove
    ad_user_data_consent: granted
    ad_personalization_consent: granted
```