Google Enhanced Conversions for Leads

Google is a multinational technology company focusing on online advertising, search engine technology, cloud computing, and computer software. This destination let you improve the accuracy of your offline conversion measurement by uploading click conversions that contain hashed user identifiers and some optional additional details that help Google Ads match the conversion to the ad that initiated the lead.

Key features

The Google Enhanced Conversions for Leads destination provides the following key features:

• Events structure: our Events reference covers Google method uploadClickConversions, meaning that your data is properly bridged to the expected fields in an optimized way.

• Prebuilt mappings: data mapping for event-based destinations happens automatically, which simplifies user inputs.

• Automatic hashing: information is automatically hashed matching partner specifications.

• Smart mapping: data mapping can be readjusted using your datalayer defined fields.

• Support for multi-item data: information included in the item array is dispatched to the partner.

Destination setup

Before configuring this destination, see the following prerequisites:

Login into Google Ads and:

• Click Goals

• Click the Conversion drop down in the menu section.

• Click Summary → View all conversion actions

• In this section, look for either Qualified leads or Converted lead: only these conversion action types can be used with the Google Enhanced Conversions for Leads:

If you need to create a supported conversion action, you can follow these steps:

• Click Goals

• Click the Conversion drop down in the menu section.

• Click Summary → + Create conversion action

• Flag Conversions offline only, and click on Edit data sources

• Select Skip this step and set up a data source later

• Select either Qualified lead or Converted lead and complete your conversion action configuration.

In Google Ads, you must complete the following actions: • Accept Customer data terms under Goals → Conversions → Settings • Flag Turn on enhanced conversions for leads under Goals → Conversions → Settings → Enhanced conversions for leads .

The conversion action type must be UPLOAD_CLICKS , and must exist in the Google Ads conversion customer of the Google Ads account associated with the click. Please follow the above steps to view your current conversion actions and/or create a new supported conversion action. More details are available following this LINK.

Configuration

Settings	Description
Authentication	Required Your credentials with Google Ads as set in the Commanders Act interface following: Administration ➜ Connector Credentials ➜ Add connector credentials ➜ Google Ads
Mapping Conversion Names	Required Map your Google Ads conversion names, where enhanced conversions are applied, with your events by setting the fields Conversion name and Your event name . At least one line is required. Conversion names can be found in the Google Ads interface following: Goals ➜ Summary ➜ Conversion actions (column).
Mapping Custom Variables	Custom variables add richer data to your conversions so that you can further segment your reports. You can map your custom variable names with your values by setting the fields Custom variable name and Your value . More details are available by following this LINK.
Google Analytics Measurement Id	You can add the Google Analytics "Measurement Id", which is a string like "SE23QCQ1Q8" without the intial "G-" part. It's used as an additional method to retrieve your gclid from available cookies.
Validate Only	If flagged, the request is validated but not executed!. Only errors are returned, not results, in the tab Event Inspector.
Debug Enabled	If flagged, Google endpoint will perform all upload checks and return errors if any are found. If false, it will perform only basic input validation, skip subsequent upload checks, and return success even if no click was found for the provided user identifiers. More details are available by following this LINK.

Quick reference

Commanders Act Events	Google Tracking
[Any Event] [1]	customers.uploadClickConversions

1. See Mapping Conversion Names in Configuration for more details.

Field mappings

At least one of the following identifiers must be provided:

• User email

• User phone

Properties can be remapped using our Smart Mapping feature. Google Enhanced Conversions for Leads supports consent signals. More details are available following this LINK. Google properties are set starting from the path conversions[0] .

Commanders Act Properties	Google Properties
id	orderId
partners.google.gclid Google Analytics Measurement Id	gclid [1]
partners.google.gbraid	gbraid [2]
partners.google.wbraid	wbraid [3]
partners.google.email_source partners.google.phone_source	userIdentifierSource [4]
user.email_sha256	hashedEmail [4][5]
user.phone	hashedPhoneNumber [4][5]
user.google_consent_mode.ad_user_data	consent.adUserData
user.google_consent_mode.ad_personalization	consent.adPersonalization
partners.google.aduserdata	consent.adUserData [6]
partners.google.adpers	consent.adPersonalization [6]
partners.google.merchant_id	cartData.merchantId
partners.google.feed_country_code	cartData.feedCountryCode
partners.google.feed_language_code	cartData.feedLanguageCode
partners.google.local_transaction_cost	cartData.localTransactionCost
items.X.id	cartData.items.X.productId
items.X.product.price	cartData.items.X.unitPrice
tems.X.quantity	cartData.items.X.quantity
Mapping Conversion Names	conversionAction [7]
value	conversionValue
currency	currencyCode
Custom variable name	conversionCustomVariable [8][9]
Your value	value [8][10]
Validate Only	validateOnly [11]
Debug Enabled	debugEnabled [11]

1. See Google Analytics Measurement Id in Configuration for more details. 2. Google click identifier for clicks associated with app conversions and originating from iOS devices starting with iOS14. 3. Google click identifier for clicks associated with web conversions and originating from iOS devices starting with iOS14. 4. Set in the userIdentifiers.X . Accepted values: FIRST_PARTY , THIRD_PARTY or UNSPECIFIED . Default value: FIRST_PARTY . 5. Automatically hashed if provided in clear text. 6. Accepted values: true , 1 or granted when user granted the consent or false , 0 or denied otherwise. If consent is not specified use unspecified . All string values are case insensitive. Default value granted . 7. Conversion resource name in the following format: customers/[CUSTOMER_ID]/conversionActions/[CONVESION_ACTION_ID] 8. Set in the path customVariables.X . 9. Resource name of the custom variable in the following format: customers/[CUSTOMER_ID]/conversionCustomVariables/[VARIABLE_ID] 10. Your value for the custom variable. See Mapping Custom Variables in Configuration for more details. 11. Set in the base path. See Configuration for more details.