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.
API information
This connector uses the following vendor API:
- API Name: Google Ads API
- API Version: v18
- API Endpoint:
https://googleads.googleapis.com/ - Documentation: Google Ads API
Configuration
Go 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.
Create user list
To create a user list, click Create User List and enter the following information:
| Parameter | Description |
|---|---|
| List Name | (Required) User list name. |
| List Type | (Required) The list type. This affects the type of user identification information to be used with this list:
|
| App ID | Required for mobile advertising list types. A string that uniquely identifies the mobile application from which data is being sent to Google Ads API. |
| List Membership Lifespan | (Optional) The number of days a user stays on the list since their most recent addition to the list. Number must be between 0 and 540. The default lifespan is 540 days. |
| List Description | (Optional) List description. |
Actions
| Action Name | AudienceStream | EventStream |
|---|---|---|
| Add User to Remarketing List | ✓ | ✓ |
| Remove User from Remarketing List | ✓ | ✓ |
| Bulk Add Users to Remarketing List | ✓ | ✓ |
| Bulk Remove Users from Remarketing List | ✓ | ✓ |
Enter a name for the action and select the action type.
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 |
|
Batch Limits
This connector can use 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: 33,000
- Max time since oldest request: 60 minutes
- Max size of requests: 40 MB
Add User to Remarketing List (Non-Batched or Batched)
Parameters
| Parameter | Description |
|---|---|
| Remarketing List | Select a remarketing user list. For more information, see Google Ads: Remarketing and Audience Targeting. Available options contain only user lists of first-party CRM data type. To create a user list, see Create user list. |
| Customer ID Override | (Optional) Provide a customer ID to override the customer ID in the connector configuration. If using this option, you must also enter a User List ID Override. |
| Manager Customer ID Override | (Optional) Provide a Manager Customer ID if using a Customer ID Override and accessing a client customer. |
| User List ID Override | (Optional) Provide a user list resource name (list ID and type) to override the user list. This field lets you use EventStream variables to populate the user list ID. This is required if using a Customer ID Override. The value should be in the following format ID:TYPE, for example 123456:CONTACT_INFO. |
Consent
When using the Add User to Remarketing List action, the connector sends 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.
Remove User from Remarketing List (Non-Batched or Batched)
Parameters
| Parameter | Description |
|---|---|
| Remarketing List | Select a remarketing user list. For more information, see Google Ads: Remarketing and Audience Targeting. Available options contain only user lists of first-party CRM data type. |
| Customer ID Override | (Optional) Provide a customer ID to override the customer ID in the connector configuration. If using this option, you must also enter a User List ID Override. |
| Manager Customer ID Override | (Optional) Provide a Manager Customer ID if using a Customer ID Override and accessing a client customer. |
| User List ID Override | (Optional) Provide a user list resource name (list ID and type) to override the user list. This field lets you use EventStream variables to populate the user list ID. This is required if using a Customer ID Override. The value should be in the following format ID:TYPE, for example 123456:CONTACT_INFO. |
This page was last updated: December 17, 2025