Configure destinations for Google Customer Match

Use Google Customer Match to create and publish search, display, and video ads across the Google-owned paid media ecosystem.

Caution

The values for firstname, lastname, email, and phone sent to Google Customer Match are SHA-256 hashed automatically by Amperity before sending. Do not use the TO_HEX() function with the firstname, lastname, email, and phone fields for queries that return results for Google Customer Match.

Note

The country field is normalized to an ISO 3166-1 alpha-2 country code before sending but is not hashed. The zip field is sent as-is without normalization or hashing.

What is Google Customer Match?

“Google Customer Match” is a unified ad creation tool that you can use to create and publish search, display, and video ads across the Google-owned paid media ecosystem.

For example:

• Use Discovery campaigns to reach customers in the Promotions and Social tabs in Gmail .

• Use Google Ads to configure campaign types for search, display, video, app, local, hotel, call, smart, goal-based, and shopping.

• Run ads within search results on Google.com .

• Run ads within the Shopping tab on Google.com .

• Send audiences to DV360, and then run video advertising campaigns in YouTube Ads or on web pages using any of the available placement options . DV360 supports advertiser and partner networks.

Use Amperity to build high-value product affinity segments that are based on first-party data, and then configure Amperity to use the Google Customer Match destination to send those segments to Google Customer Match.

Once uploaded, “Google Customer Match” hashes each record, and then matches all records against hashed user accounts that already exist in “Google Customer Match” to identify segments that contain records that match the ones sent from Amperity.

“Google Customer Match” builds audience lists that are reachable across the Google-owned paid media ecosystem.

Use these audience lists for precision cross-selling, to reach and convert new customers, and to improve the retention rate for your most loyal customers.

When to use Google Customer Match for sending audiences to Google Ads?

Use the Google Customer Match destination when you want to use the same Google Ads account to send an audience to Google Ads and Google Display & Video.

Get details

Review the following details before configuring credentials for Google Customer Match and before configuring Amperity to send audiences to Google Customer Match.

	Credential settings Refresh token A refresh token is generated by the OAuth process and authorizes Amperity to send data to Google Customer Match. The value for the refresh token is automatically updated. Important Authentication for “Google Customer Match” must be completed within Google before configuring Amperity to send audiences to Google Customer Match.
	Required configuration settings Customer product The Google advertising product to which Amperity sends audiences. May be one of “Google Ads”, “Display Video Advertiser”, or “Display Video Partner”. Customer ID The customer ID for your brand’s Google Customer Match account. This value must be 10 digits and may not contain dashes. Audience name (Required at orchestration) The name of the audience in Google Customer Match managed by Amperity. Amperity creates the audience if it does not exist. Audience names may only contain letters, numbers, underscores, dashes, and spaces. Any other characters are automatically removed. Upload key type The key to use for audience matching in Google Customer Match. May be one of “Contact Info”, “Mobile ID”, or “User Id”. The upload key type cannot be changed after an audience is created. To use a different key type, create a new audience.
	European Union user consent Important Review the user consent policy for the European Union (EU) and European Economic Area (EEA), and then add the required columns to your orchestration or campaign.

Configure credentials

OAuth is an open standard for access delegation, commonly used to grant websites or applications access to information on other websites.

Use OAuth to configure Amperity to send audiences to Google Customer Match.

Important

OAuth for “Google Customer Match” must be completed within Google before configuring OAuth in Amperity.

To configure OAuth for Google Customer Match

	Open the Destinations tab and click Add Destination. The Add Destination dialog box opens. Select Google Customer Match from the Plugin dropdown, and then from the Credential dropdown, select Create a new credential. This opens the Create New Credential dialog box.
	In the Create New Credential dialog box, click “Generate authorization URL”. Copy the URL, and then provide the URL to a user who has credentials that allow access to Google Customer Match. The user must log in and complete the steps required by the OAuth process for Google Customer Match. After this is completed, you will be redirected to the Credentials page in Amperity. Verify the credential is on the page, and then return to the Destinations tab.
	Open the Destinations tab and click Add Destination. The Add Destination dialog box opens. Select Google Customer Match from the Plugin dropdown, and then from the Credential dropdown, select the credential that is authorized to access Google Customer Match. Note The value for the Refresh Token setting is updated automatically after you select the credential.

Reauthorize Amperity

You may need to reauthorize access to Google Customer Match. This is necessary when an authorization token has expired or when it has been removed by someone with permission to manage access within Google Customer Match. To reauthorize access to Google Customer Match, follow the steps to configure OAuth and create a new credential.

Add destination

Use a sandbox to configure a destination for Google Customer Match. Before promoting your changes, send a sample audience, and then verify the results in Google Customer Match. After verifying the end-to-end workflow, push the destination from the sandbox to production.

To add a destination for Google Customer Match

	Open the Destinations page, select the New destinations button, and then select Orchestration. To configure a destination for Google Customer Match, do one of the following: Click the row in which Google Customer Match is located. Destinations list alphabetically and you can scroll up and down the list. Search for Google Customer Match. Start typing “google”. The list filters to show only matching destinations. Select “Google Customer Match”.
	Select the credential for Google Customer Match from the Credential dropdown, and then click Continue. Tip Amperity validates the connection when the destination is saved. If the connection cannot be validated, an error is shown and the destination is not saved.
	In the “Destination settings” dialog box, assign the destination a name and description that ensures other users of Amperity can recognize when to use this destination. Configure business user access By default a destination is available to all users who have permission to view personally identifiable information (PII). Enable the Admin only checkbox to restrict access to only users assigned to the Datagrid Operator and Datagrid Administrator policies. Enable the PII setting checkbox to allow limited access to PII for this destination. Use the Restrict PII access policy option to prevent users from viewing data marked as PII anywhere in Amperity and from sending data to downstream workflows.
	Configure the following settings, and then click “Save”. Customer product The Google advertising product to which Amperity sends audiences. May be one of “Google Ads”, “Display Video Advertiser”, or “Display Video Partner”. Customer ID The customer ID for your brand’s Google Customer Match account. This value must be 10 digits and may not contain dashes. Audience name (Required at orchestration) The name of the audience in Google Customer Match managed by Amperity. Amperity creates the audience if it does not exist. Audience names may only contain letters, numbers, underscores, dashes, and spaces. Any other characters are automatically removed. Audience description (Required at orchestration) A description of the audience managed by Amperity. Membership duration The length of time (in days), after which a customer is removed from this audience. This value may be between “0” - “540”. Set this value to “0” to remove all audience members. To ensure customers stay in this audience ensure the frequency at which Amperity sends the audience to Google Customer Match is less than the membership duration. Upload key type The key to use for audience matching in Google Customer Match. May be one of “Contact Info”, “Mobile ID”, or “User Id”. The upload key type cannot be changed after an audience is created. To use a different key type, create a new audience. Mobile app ID When the value of “Upload key type” is “Mobile ID”, the mobile ID for the iOS or Android app.
	After configuring this destination users may use: Orchestrations to send query results Orchestrations and campaigns to send audiences Orchestrations and campaigns to send events
	Validate the audience with Google Customer Match by using a sample audience with a very small membership. For example: 10 or 100 members or the minimum audience size recommended by Google Customer Match. Send the sample audience to Google Customer Match and verify the sample audience is correct in Google Customer Match. Make adjustments if necessary. Only send full audiences after validation is complete.

European Union user consent

The Google Ads API uses the Consent object to specify user consent signals for sending user data to Google for advertising purposes and for ad personalization.

Important

Customers must send the required user consent signals when uploading data for advertising to customers in the European Economic Area (EEA) and to adhere to the European Union (EU) user consent policy. Not including these signals may result in lower match rates.

Required Column		Description
ad-personalization		Sets consent for ad personalization. Possible values: GRANTED, UNSPECIFIED, or DENIED. Default value: UNSPECIFIED. Important This value must be set to GRANTED to indicate that your brand has received the required user consent.
ad-user-data		Sets consent for sending user data to Google for advertising purposes. Possible values: GRANTED, UNSPECIFIED, or DENIED. Default value: UNSPECIFIED. Important This value must be set to GRANTED to indicate that your brand has received the required user consent.