Configure events for 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.

When a customer purchases something from your brand’s website, you likely collect some first-party data from that customer to complete the transaction. For example, a physical address, an email address, a phone number, and a full name.

First-party customer data that is associated with online transactions can be sent to Google Enhanced Conversions, after which it can be used to enhance conversion measurement in Google Ads. For example:

• Track sales and events that happen on a website.

• Track sales that happen from a website.

• Match customers to their Google accounts, which were signed-in to when they engaged with one of your ads.

• Attribute customer engagment with a Google Ads campaign by matching data collected on your website with the signed-in Google accounts that engaged with your ads.

How to send events to Google Enhanced Conversions?

First-party customer data that is associated with offline transactions can be uploaded to Google Enhanced Conversions, after which it can be used to enhance conversion measurement in Google Ads.

Configure Amperity to send a CSV file to Google Enhanced Conversions using SFTP.

Get details

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

	Configure Google Ads Enable enhanced conversions for leads in Google Ads: Enable conversion tracking in Google Ads . Accept customer data terms and opt-in to enhanced conversions for leads. Set up tagging through Google Tag Manager. Create at least one ConversionAction. The conversion_action_type must be set to UPLOAD_CLICKS. Configure Google tag settings to enable enhanced conversions for leads.
	Events data Load to Amperity data that tracks events data for carts, items in carts, and customer consent. This dataset should include the Google Ads click ID. Some of this data may be sent to Google Enhanced Conversions for customer attribution.
	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 automatically updated. 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 The Customer ID of the Google Enhanced Conversions 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 configures 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 vary by 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 automatically updated.

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 results in Google Enhanced Conversions. After verifying the end-to-end workflow, push the destination from the sandbox to production.

To add a destination for Google Enhanced Conversions

	Open the Destinations page, select the New destinations button, and then select Orchestration. To configure a destination for Google Enhanced Conversions, do one of the following: Click the row in which Google Enhanced Conversions is located. Destinations list alphabetically and you can scroll up and down the list. Search for Google Enhanced Conversions. Start typing “google”. The list filters to show only matching destinations. Select “Google Enhanced Conversions”.
	Select the credential for Google Enhanced Conversions from the Credential dropdown, and then click Continue. Tip If there are any issues with destination connectivity, an error message will display in the destination setup dialog. If the destination saves successfully, the connection is ready for use.
	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”. Conversion action name (Required at orchestration) The name of the conversion action. Customer ID Required The Customer ID of the Google Enhanced Conversions account.
	After configuring this destination users may use orchestrations to send query results Google Enhanced Conversions.
	Test the connection with Google Enhanced Conversions by using an audience with a very small membership. For example: 10 or 100 members or the minimum audience size recommended by Google Enhanced Conversions. Send the test audience to Google Enhanced Conversions and verify the audience is correct in Google Enhanced Conversions. Make adjustments if necessary. Only send full audiences after validation is complete.

Fields for enhanced conversions

Fields for enhanced conversions must include hashed customer profile data–email addresses and phone numbers–and should include a transaction identifier and the Google Ads click ID.

The following table describes the fields that may be sent to Google Enhanced Conversions for customer attribution. You should send as many of these fields as you can for each potential attribution to customer activity.

Amperity	Google	Description
Varies.	ad_personalization	The customer consent status for personalization for Google Ads. Note This field should be in the table that contains online events data for websites and mobile apps collected by Google Ads, but may be located in a table for consent tracking.
Varies.	ad_user_data	The customer consent status for Google Ads. Note This field should be in the table that contains online events data for websites and mobile apps collected by Google Ads, but may be located in a table for consent tracking.
Varies.	conversion_environment	The environment in which the conversion occurred. For example: APP or WEB. Note This field should be in the table that contains online events data for websites and mobile apps collected by Google Ads.
Varies.	currency_code	The currency code for the conversion_value.
Email	email	The email address for the customer. The value for the email address must be SHA-256 hashed. Tip Use the email field in the Merged Customers table.
Varies.	feed_language_code	The language code used in Google services to set the language of an advertising feed.
Varies.	feed_country_code	The country code used in Google services to set the language of an advertising feed.
Varies.	gbraid	A gbraid is a URL parameter present when a user clicks on an ad on the web, and then is directed to your brand’s iOS app. Note This field should be in the table that contains online events data for websites and mobile apps collected by Google Ads.
Varies.	gclid	A gclid is an identifier captured from URL parameters when a customer clicks on an ad, and then navigates to your brand’s website. This is the best identifier for online events and Google Ads. Important Send all relevant data for a conversion even if the gclid is unavailable. Converstions data that only includes user-provided data is still useful. Note This field should be in the table that contains online events data for websites and mobile apps collected by Google Ads.
Item Cost	local_transaction_cost	The individual cost for each item in the order. Tip Use the Item Cost field in the Unified Itemized Transactions table.
Store ID	merchant_id	A store ID is a unique identifier for the location of a store. Tip Use the Store ID field in the Unified Itemized Transactions table.
Order ID	order_id	An order ID is the unique identifier for the order. It links together all items in the same transaction. For returns and cancellations, the order ID is the unique identifier for the original order, including returned or canceled items. Google Enhanced Conversions refers to this as the transaction ID for the conversion. This field is optional, but strongly recommended. Tip Use the Order ID field in the Unified Itemized Transactions table.
Phone	phone	The phone number for the customer. The value for the phone number must be SHA-256 hashed. Tip Use the phone field in the Merged Customers table.
Product ID	product_id	The unique identifier for a product. Tip Use the Product ID field in the Unified Itemized Transactions table.
Item Quantity	quantity	Item quantity is the total number of items in an order. For returned and canceled items, item quantity is the total number of returned or canceled items. Tip Use the Item Quantity field in the Unified Itemized Transactions table.
Varies.	timestamp	The date and time of the conversion. The value must have a timezone and the format must be yyyy-mm-dd HH:mm:ss+|-HH:mm. Daylight Savings Time (DST) may be ignored. Note This field should be in the table that contains online events data for websites and mobile apps collected by Google Ads or it may be the Order Datetime field in the Unified Itemized Transactions table.
Unit List Price	unit_price	Unit list price is the manufacturer’s suggested retail price (MSRP) for a single unit of an item. Tip Use the Unit List Price field in the Unified Itemized Transactions table.
Varies.	wbraid	A wbraid is a URL parameter that is present when a user clicks on an ad in an iOS app and is directed to a webpage. Note This field should be in the table that contains online events data for websites and mobile apps collected by Google Ads.