Skip to main content

What this is

Google Customer Match (Customer Contact Information) is a batch destination: it sends hashed email addresses and hashed phone numbers out of Zeotap CDP into your Google Ads or Google DV360 (Display & Video 360) account, where they arrive as Customer Match customer lists you can target or suppress in campaigns. You build the audience in Zeotap CDP, link it to this destination, and Zeotap CDP uploads the identifiers on the audience’s refresh schedule. Google Customer Match lets you use first-party data to share the unique insights you have about your customers beyond Google’s understanding. That can deepen existing customer relationships — or build new ones — across Google’s properties in a privacy-safe way. This is becoming increasingly important as Google phases out cookie-based re-marketing due to privacy, browser and regulation changes. Related pages for the same vendor:
Important Notice:To ensure compliance with the EU user consent policy and continue accessing Customer Match within the European Economic Area (EEA), Google is enhancing its enforcement measures. Google requires its partners to update to the latest Google Ads API v15 and begin transmitting consent signals for users in the EEA region. The following are the consent signals it covers:
  • ad_user_data: Indicates consent to send user data for advertising purposes to Google.
  • ad_personalization: Indicates consent for ad personalisation.
Note that commencing March 6th, 2024, Zeotap CDP will transmit a GRANTED consent status for the above mentioned consent signals. To ensure that only consented users meet the audience criteria, you are advised to perform the following actions:
  • Provide Zeotap CDP with the appropriate consent parameters covering the two consent signals requested by Google (ad_user_data and ad_personalization)
  • Establish relevant Consent Orchestration rules to ensure that only users who have consented to perform ad personalisation on Google Products are ingested.
Note: For the frequently asked questions about the consent update, refer to FAQs related to Google Consent Update.

Where the audience can be used

Customer Match is a useful advertising tool for many business goals, from increasing brand awareness to driving conversions. Audiences sent through this destination can be used as follows:
  • On the Search Network and the Shopping tab, you can optimise your campaigns by adjusting your bid based on what you know about your customers’ activities.
  • On Gmail, you can reach your customers or similar audiences using personalised ads at the top of their inbox tabs.
  • On YouTube, you can reach new audiences by targeting audiences similar to your most valuable customers.
  • On Display, you can reach your customers or similar audiences using personalised ads on the Google Display Network.

Common uses

  • Re-engage known customers. Upload email addresses from your CRM into Zeotap CDP, build tailored audience segments, and send them to Google Customer Match for targeted campaigns across Search, the Shopping tab, Gmail, YouTube and Display.
  • Suppress ads. Create suppression segments in Zeotap CDP for existing customers, or for people who do not wish to be targeted, and send them to Google Customer Match so those audiences are excluded from ad campaigns.
  • Reach similar prospects. Identify high-value customer segments in Zeotap CDP and send them to Google Customer Match to build lookalike audiences, allocating higher budgets to those segments and lower cost limits to low-LTV audiences.

Supported identifiers and actions

This integration supports hashed phone numbers in E164 format and hashed email addresses (mostly Gmail).
Note:Follow these guidelines to ensure proper data handling and audience segmentation when using Customer Match:
  • Ensure that the emails are hashed to SHA256 and cellphone numbers are converted to E164 format before hashing it to SHA256. For more information about how to convert it to E164, refer to our hashing guidelines.
  • When you send multiple identifiers, such as email addresses, phone numbers, and MAIDs, to Customer Match, Zeotap CDP creates multiple audience segments within GCM (AdWords), each with a unique segment ID. The data is uploaded to the corresponding segments based on these IDs. The segment IDs are displayed separately on the UI. The segment name in AdWords for the identifiers appears in the following format: {AudienceName}{DestinationName}_SegmentId

Available actions and supported features

The following table lists the action types available for the integration and their supported features: Delta and Delete functionality is released in phases and is activated per destination — see Delta Upload and Delete Functions, which lists this integration under the Delete-enabled integrations and describes how activation is requested.

Prerequisites

Customer Match is not available for all advertisers. To use Customer Match, the account must have the following details:
  • A good history of policy compliance
  • A good payment history
  • At least 90 days history in Google Ads
  • More than 50,000 USD total lifetime spend. For advertisers whose accounts are managed in currencies other than USD, your spend amount will be converted to USD using the average monthly conversion rate for that currency.
For complete information about the requirements for using Google Customer Match, refer to the Google Help documentation. These guidelines apply to advertisers using Customer Match for campaigns on Search, Shopping, Display, YouTube or Gmail. Ensure that you have the below details available before creating a Google Customer Match destination in Zeotap CDP.

Seat ID

This is the unique ID assigned to your Advertiser account that you can locate next to your account name within the respective Google products. Note that you can add a Seat ID for Google Ads and Google DV360 through this integration. Depending on the product that your Seat ID is associated with, you have to choose the corresponding Product Type.
The Google Ads top navigation bar. The account identifier that sits beside the account name in the header is outlined with a box and marked with an arrow, showing where in the interface to look for it.

Product type

Based on the platform you want to use and your role, choose the Google product that matches your requirement. You can either use Google Ads (AdWords) or Google DV360 (Display & Video 360).
  • If you are using Google Ads, then choose ADWORDS as your Product Type. This allows you to serve ad campaigns on Search, the Shopping tab, Gmail, YouTube and Display.
  • If you are using Google DV360, a demand-side platform (DSP) for managing and optimising digital ad campaigns across channels like display, video, and connected TV, then choose from the below options.
    • INVITE_PARTNER — Select this option if you are a Bid Manager Partner. A Partner manages multiple advertiser accounts under a single account, typically used by agencies or organisations handling campaigns for multiple clients.
    • INVITE_ADVERTISER — Select this option if you are a Bid Manager Advertiser. An Advertiser represents a single brand or organisation running its own campaigns in DV360. Key differences between a Partner and an Advertiser in DV360

Whitelist Zeotap on your Google product

To send audiences (segments) from Zeotap CDP to Google Ads or DV360, you must first whitelist Zeotap on the platform you wish to use. Whitelisting is required for successful audience/segment creation; without it, the segments will fail. Follow the instructions below for the platform you use:

Whitelist Zeotap on Google Ads

To send audience segments from Zeotap CDP to Google Ads, ensure that you whitelist Zeotap CDP by performing the following steps:
1
Log into your Google Ads account.
2
In the left panel, navigate to Tools > Data manager.
3
Under Data manager, open the Connected products tab, then click + Connect Product as shown below.
The Google Ads Data manager page on the Connected products tab, with annotations marking Data manager in the Tools menu and the + Connect Product button. The Connected products list shows YouTube and Zeotap entries.
4
In the search box, search for and select Zeotap, then click Authorise.
The Connect a product dialog in Google Ads. The Data source search box contains the text Zeotap and a matching Zeotap result appears in the dropdown, with an annotation reading 'Select Zeotap and click Authorise'. A grid of other available data sources sits below.
5
Once the data source is connected, the dialog shows Data source connected with Audiences selected as the use case. The Conversions use case is unavailable for this data source. Click Done.You can then use Zeotap CDP to create and send audiences to Google Ads as Customer Lists.
The Connect a product dialog in Google Ads showing Zeotap as the data source with a green 'Data source connected' confirmation, the Audiences use case selected, an Audience Segments section explaining that segments created in Zeotap appear in Audience manager as customer lists, and a Done button.

Whitelist Zeotap on Google DV360

You must complete a one-time mapping of your DV360 Partner or Advertiser ID to Zeotap before Zeotap CDP can send any data into DV360. Also, make sure you know which DV360 entity object (Partner or Advertiser) you are associated with, so that the matching Product Type — INVITE_PARTNER or INVITE_ADVERTISER — is selected when you create the destination. Perform the following steps to link Zeotap to your DV360 account:
1
Log into your DV360 account with the appropriate credentials.
2
Navigate to Partner Settings and select Linked Accounts.
3
Under Linked Accounts, click LINK NEW ACCOUNT and select External Data partner.
The Display & Video 360 Linked Accounts page under Partner Settings, with Linked Accounts highlighted in the left menu and the LINK NEW ACCOUNT control outlined. The panel reads 'Data sharing settings for Audience tab and Ads Data Hub' and 'No linked accounts found'.
4
Under Account, search for Zeotap.
5
Select CMU: Zeotap (Customer Match Upload: Zeotap) as shown below and click Link.
The Link External Data Partner dialog in Display & Video 360. The Account search box contains 'zeotap' and the results list shows two entries, DMP: Zeotap and CMU: Zeotap, with an arrow pointing at CMU: Zeotap.

Mapping of Zeotap CMU by Google on their interface

6
Once you complete the linking process, the Zeotap account appears under the linked accounts.

Create the Google Customer Match (Customer Contact Information) destination

Once you have completed the prerequisites above, perform the following steps to create the destination in Zeotap CDP:
1
Log into the Zeotap CDP App and go to Integrate > Destinations.
2
Click + Create Destination.
The Zeotap CDP Destinations list under Integrate, on the Private Destination tab, with the + Create Destination button outlined. The table columns are ID, Destination Name, Created Date, Last Updated On and Created By.
3
Under All Destinations, search for Google Customer Match (Customer Contact Information).
The All Destinations catalogue in Zeotap CDP with the 'Search for a Destination' box outlined, above a grid of destination tiles such as Adform, Adobe DMP, Airship Static Lists and AmazonDSP.
4
Click Google Customer Match (Customer Contact Information). A screen appears displaying details about the particular destination towards the left. On the right-hand side of the screen you will find the fields required for the integration to be established. Enter the required details as mentioned in the following steps:a. Enter a name for the Destination under Destination Name.b. Enter the Seat ID of the account on which you want the segment. Learn morec. Select the appropriate Product Type that the Seat ID belongs to. Learn mored. Click Next to proceed to mapping.
The 'Enter Destination Details' step of the Google Customer Match - Customer Contact Information destination in Zeotap CDP, showing the Destination Name, Seat ID and Product Type fields with ADWORDS chosen as the Product Type, a note that segments can take up to three business days to appear at the seat, and Back and Next buttons.
5
In the new screen that appears, choose the appropriate action and mapping as explained below.a. Under Choose your Action, you can choose either Send Identifiers to Google Customer Match - Customer Contact Information or Send Multiple User Identifiers as the action, based on your use case.i. If you choose Send Identifiers to Google Customer Match - Customer Contact Information, then the output identifiers email addresses and cellphone numbers are populated. Note that in this action, each identifier is sent as an individual user profile.
The Mapping step in Zeotap CDP with 'Send identifiers to Google Customer Match - Custom...' chosen under Choose your Action, and an Output Identifiers Mapping table pairing the Cellphone Number E164 catalogue field with the Mobile E164 destination field and the Email SHA256 catalogue field with the Email destination field.
ii. If you choose Send Multiple User Identifiers as your action, then the output identifiers such as Hashed email address, Hashed cellphone numbers, last name, first name, Country Code and Postal Code are populated. Note that in this action, all the identifiers selected under the mapping screen are sent as a single user profile.
Note:To increase the match rate, we recommend that you use Send Multiple User Identifiers as the action.
The Mapping step in Zeotap CDP with Send Multiple User Identifiers chosen under Choose your Action, and a 'Map the Fields' table under Identifiers pairing catalogue fields with the Email, Mobile E164 and Country Code destination fields.
6
Click Create Destination. The created Destination gets listed in the Audiences application, where it can be linked to an Audience/segment.
For information about how to link an Audience or segment to the created Destination in the Audiences application, refer to Activate Your Batch Audiences. It can take up to three business days for the segment to be available at the Google Customer Match (Customer Contact Information) seat. Note that the segments created on GCM appear in the format: {Audience Name}_{Audience Id}.
Note:The terms Audiences and Segments are used interchangeably to refer to customer cohorts belonging to a specific category. For example, an Audience or a segment can be a specific group of customers who are over 18 years of age and have performed an addToCart event within the last 30 days.

User disqualification from audiences

This integration supports user disqualification from audiences. That is, a user can be disqualified from an audience (segment) for various reasons, such as not meeting audience criteria, consent requirements or other conditions set for a particular audience.
  • When a user disqualifies from an audience, Zeotap CDP initiates a user deletion request in the next refresh cycle. These requests are sent to the audiences linked to the specific destination.
  • The disqualified users are excluded from the audiences based on the configured refresh frequency for a particular audience.
  • User disqualification is a programmatic process that works automatically. You do not need to specify anything to trigger the disqualification and exclusion of users from audiences.
Note:For more information about this functionality, refer to Delta Upload and Delete Functions.

Verify the segments reached Google Ads

Perform the following steps to view the segments pushed to Google Ads:
1
Log into your Google Ads account.
2
In the left panel, navigate to Tools.
3
Under Shared library, select Audience manager.
4
Under Your data segments, you can view the list of all the segments pushed. You can find the ‘Customer list’ for any segment pushed through Google Ads along with the customer contact information tied to the particular segment under the Customer Type column. For example, Customer list (Mobile Device IDs) or Customer list (Customer contact information).
The Google Ads Audience manager on the 'Your data segments' tab, reached from Shared library in the Tools menu. The table lists segments with Segment name, Customer Type, Segment Type, Membership status and per-network size columns.

Troubleshoot Google Customer Match deliveries

Next steps

Last modified on November 17, 2026