Google Ads Customer Match Connector Setup Guide
This article describes how to set up the Google Ads Customer Match (Customer-Provided Credentials and Tealium-Provided Credentials) connectors.
This connector replaces the deprecated Google AdWords Customer Match connectors.
Connector actions
Action Name | AudienceStream | EventStream |
---|---|---|
Add User to Remarketing List | ✓ | ✓ |
Remove User from Remarketing List | ✓ | ✓ |
API information
This connector uses the following vendor API:
- API Name: Google Ads API
- API Version: v10
- API Endpoint:
<https://googleads.googleapis.com/>
- Documentation: Google Ads API
Configure settings
Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see the About Connectors article.
When you add this connector you are prompted to accept the vendor’s data platform policy.
After adding the connector, configure the following settings:
-
Customer ID
- Required
- Provide Ads account customer ID to manage.
-
Manager Customer ID
- Optional
- If you are accessing a client customer, the Manager Customer ID must be set.
-
Developer Token
- Required
- Provide the API developer token that has been approved by Google to make production volume API requests.
- Obtaining and approving a developer token is a multi-step process that you will need to own and manage. To get started, see Obtain Your Developer Token.
Actions settings - parameters and options
Click Next or go to the Actions tab. This is where you configure connector actions.
This section describes how to set up parameters and options for each action.
User Identifiers
Each action requires a user identifier and the vendor requires these values to be normalized and hashed using SHA-256. Each user identifier value mapped is expected to be:
- Lower-case
- Trimmed whitespace from the front and end of the text
- Hashed with SHA-256
You can map attributes that are already normalized and hashed or you can allow the connector to normalize and hash them for you. Select the appropriate mapping for your scenario.
The required user identifier is based on the user list type selected. The user list types are:
- CONTACT_INFO
- CRM_ID
- MOBILE_ADVERTISING_ID
The following user identifier fields are supported:
User Identifier Field | Description |
---|---|
CONTACT_INFO |
|
CRM_ID |
|
MOBILE_ADVERTISING_ID |
|
Action - Add User to Remarketing List
Parameters
Parameter | Description |
---|---|
Remarketing List |
|
User Identifier |
|
Action - Remove User from Remarketing List
Parameters
Parameter | Description |
---|---|
Remarketing List |
|
User Identifiers |
|
This page was last updated: August 19, 2022