Send audiences to Google Customer Match

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

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 updated automatically. Important Authentication for “Google Customer Match” must be completed within Google prior to configuring Amperity to send audiences to Google Customer Match.

Required configuration settings Customer product The Google advertising product to which audiences will be sent. 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 that is managed by Amperity. This audience will be created by Amperity if it does not exist. Upload key type The type of key to use for audience matching in Google Customer Match. May be one of “Contact Info” or “Mobile ID”.

Configure credentials

Configure credentials for Google Customer Match before adding a destination.

An individual with access to Google Customer Match should use SnapPass to securely share “refresh token” details with the individual who will configure Amperity.

To configure credentials for Google Customer Match

	From the Settings page, select the Credentials tab, and then click the Add credential button.
	In the Credentials settings dialog box, do the following: From the Plugin dropdown, select Google Customer Match. Assign the credential a name and description that ensures other users of Amperity can recognize when to use this destination.
	The settings that are available for a credential are determined by the credential type. For the “google-customer-match” credential type, configure settings, and then click Save. 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 updated automatically.

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 test audience, and then verify the the results in Google Customer Match. After the end-to-end workflow has been verified, push the destination from the sandbox to production.

To add a destination for Google Customer Match

	Open the Destinations page, and then click the Add destination button. To configure a destination for Google Customer Match, do one of the following: Click the row in which Google Customer Match is located. Destinations are listed alphabetically and you can scroll up and down the list. Search for Google Customer Match. Start typing “google”. The list will filter 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 Click the “Test connection” link on the “Configure destination” page to verify that Amperity can connect to Google Customer Match.
	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 users with limited access to PII access to this destination. Restricted PII access is enabled when the Restrict PII access policy option that prevents users who are assigned to that option from viewing data that is marked as PII anywhere in Amperity and from sending that data to any downstream workflow.
	Configure the following settings, and then click “Save”. Customer product The Google advertising product to which audiences will be sent. 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 that is managed by Amperity. This audience will be created by Amperity if it does not exist. Audience description (Required at orchestration) A description of the audience that is managed by Amperity. Membership duration The length of time (in days), after which a customer will be removed from this audience. This value may be between “0” - “540”. Set this value to “0” to remove audience member. To ensure customers stay in this audience ensure the frequency at which the audience is sent to Google Customer Match is less than the membership duration. Upload key type The type of key to use for audience matching in Google Customer Match. May be one of “Contact Info” or “Mobile ID”. Mobile app ID When “Upload key type” is set to “Mobile ID”, the ID for the iOS or Android app from which the mobile ID was collected.
	After this destination is configured: Use orchestrations to send query results Use orchestrations and campaigns to send audiences Use orchestrations and campaigns to send offline events