Send offline events to Google Enhanced Conversions

Google Enhanced Conversions improves the accuracy of conversion measurement by sending hashed first-party conversion data to Google using one-way SHA-256 hashing of first-party customer data.

Get details

Review the following details before configuring credentials for Google Enhanced Conversions and before configuring Amperity to send offline events to Google Enhanced Conversions.

	Credential settings Refresh token A refresh token is generated by the OAuth process and authorizes Amperity to send data to Google Enhanced Conversions. The value for the refresh token is updated automatically. Important Authentication for “Google Enhanced Conversions” must be completed within Google prior to configuring Amperity to send ads to Google Enhanced Conversions.
	Required configuration settings Customer ID TEMP: “Customer ID of the Google Enhanced Conversions account; might just be Google Ads account”

Configure credentials

Configure credentials for Google Enhanced Conversions before adding a destination.

An individual with access to Google Enhanced Conversions should use SnapPass to securely share “Customer ID” details with the individual who will configure Amperity.

To configure OAuth

	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 Enhanced Conversions. 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-ads” 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 Enhanced Conversions. The value for the refresh token is updated automatically.

Add destination

Use a sandbox to configure a destination for Google Enhanced Conversions. Before promoting your changes, send a test audience, and then verify the the results in Google Enhanced Conversions. After the end-to-end workflow has been verified, push the destination from the sandbox to production.

To add a destination for Google Enhanced Conversions

	Open the Destinations page, and then click the Add destination button. To configure a destination for Google Enhanced Conversions, do one of the following: Click the row in which Google Enhanced Conversions is located. Destinations are listed alphabetically and you can scroll up and down the list. Search for Google Enhanced Conversions. Start typing “google”. The list will filter to show only matching destinations. Select “Google Enhanced Conversions”.
	Select the credential for Google Enhanced Conversions from the Credential drop-down, and then click Continue. Tip Click the “Test connection” link on the “Configure destination” page to verify that Amperity can connect to Google Enhanced Conversions.
	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”. Conversion action name (Required at orchestration) TEMP: “Name of the Conversion Action. Will be created if it doesn’t exist.” Customer ID Required TEMP: “Customer ID of the Google Enhanced Conversions account; might just be Google Ads account”
	After this destination is configured, users may configure Amperity to use orchestrations to send query results Google Enhanced Conversions.