Google Ads Customer Match (Tealium-Provided Credentials) Connector Setup Guide
This article describes how to set up the Google Ads Customer Match connector, which uses Tealium-Provided Credentials.
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: v17
- 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 the Ads account customer ID to manage. - Manager Customer ID
Optional: If you’re accessing a client customer, the Manager Customer ID must be set and have full access to the Ads account.
Action settings - parameters and options
Enter a name for the action and select the action type from the drop-down menu.
The following section describes how to set up parameters and options for each action.
User Identifiers
Each action requires a user identifier. The vendor requires that these values are normalized and hashed using SHA-256. Each mapped user identifier value is expected to meet the following requirements:
- Lowercase
- Trimmed whitespace from the beginning 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 type can be one of the following:
CONTACT_INFOCRM_IDMOBILE_ADVERTISING_ID
The following user identifier fields are supported:
| User Identifier Field | Description |
|---|---|
CONTACT_INFO |
Provide hashed email, hashed phone number, or address information. All address information fields listed below are required for this user data type.
|
CRM_ID |
|
MOBILE_ADVERTISING_ID |
|
Action - Add User to Remarketing List
Batch Limits
This action uses batched requests to support high-volume data transfers to the vendor. For more information, see Batched Actions. Requests are queued until one of the following thresholds is met or the profile is published:
- Max number of requests: 33000
- Max time since oldest request: 60 minutes
- Max size of requests: 40 MB
Parameters
| Parameter | Description |
|---|---|
| Remarketing List | Select a remarketing user list. For more information, see Remarketing and Audience Targeting. Available options contain only user lists of first party CRM data type. |
Consent
When using the Add User to Remarketing List action, the connector will send values of GRANTED for the adUserData and adPersonalization parameters. To prevent non-consented visitors from being added to lists, create an audience with rules that check visitor profile consent status. Then use the Remove from Remarketing List action to remove visitors that have not given consent from lists
Action - Remove User from Remarketing List
Batch Limits
This action uses batched requests to support high-volume data transfers to the vendor. For more information, see Batched Actions. Requests are queued until one of the following thresholds is met or the profile is published:
- Max number of requests: 33000
- Max time since oldest request: 60 minutes
- Max size of requests: 40 MB
Parameters
| Parameter | Description |
|---|---|
| Remarketing List | Select a remarketing user list. For more information, see Remarketing and Audience Targeting. Available options contain only user lists of first party CRM data type. |
This page was last updated: June 28, 2024