Google Enhanced Conversions

Google is a multinational technology company focusing on online advertising, search engine technology, cloud computing, and computer software. Taking advantage of the Google Ads API, you can leverage the enhanced conversions feature to send first-party data in the form of conversion adjustments. Google uses this additional data to improve the reporting of your online conversions driven by ad interactions. The enhanced conversions supplement your existing conversion tags by sending hashed first-party conversion data from your website to Google in a privacy-safe way.

You must complete the setup and configuration steps before you can bridge enhanced conversions via the Google Ads API.

Key features

The Google Enhanced Conversions destination provides the following key features:

• Events structure: our Events reference covers Google method uploadConversionAdjustments, 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.

Destination setup

Your user account needs admin rights in the Google Ads Manager Accounts where the conversion action is located. When available, this destination will also include the gclid value by looking for the following cookies in this priority order:

1. _gcl_aw

2. _gcl_dc

3. _gac_[GA_PROPERTY_ID]

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	Required Map your Google Ads conversion names, where enhanced conversions are applied, with your events by setting the fields Google Ads 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 action (column) [1] If a conversion action is not found the event will be discarded.
Google Analytics Property Id	The GA Tracking Id is a string like "UA-XXXXXX-Y" or "G-XXXXXXXXXX" for Google Analytics 4. It's used as an alternative method to retrieve the gclid from cookies. See Destination setup for more details.

[1] Enhanced conversions must be enabled for your conversion action. This is done in the Google Ads interface following these steps: click on the conversion action ➜ expand Enhanced conversions ➜ flag Turn on enhanced conversions ➜ select API .

Flag "Turn on enhanced conversion" and select "API".

Quick reference

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

[1] See Mapping for more details.

Field mappings

At least one of the following identifiers must be provided:

• User email

• User phone

• User first name

• User last name

• User street address

• User city

• User state

• User country

• User zip code

Most properties can be remapped using our "Smart Mapping" feature. Google properties are set starting from the path conversionAdjustments.0 or conversionAdjustments.0.userIdentifiers.X with the latter for user properties.

Commanders Act Properties	Google Properties
id	orderId [*]
context.device.user_agent	userAgent
event_timestamp	gclidDateTimePair.conversionDateTime [1] adjustmentDateTime [1]
value	restatementValue.adjustedValue
currency	restatementValue.currencyCode
user.email user.email_sha256	hashedEmail [2]
user.phone	hashedPhoneNumber [3]
user.firstname	addressInfo.hashedFirstName [3]
user.lastname	addressInfo.hashedLastName [3]
user.streetAddress	addressInfo.hashedStreetAddress [3]
user.city	addressInfo.city
user.state	addressInfo.state
user.country	addressInfo.countryCode
user.zipcode	addressInfo.postalCode
Cookie _gcl_aw Cookie _gcl_dc Cookie _gac_[GA_PROPERTY_ID]	gclidDateTimePair.gclid [4]

[*] Mandatory property. [1] This value is automatically adjusted. See GclidDateTimePair for more details. [2] If user.email is provided, it's hashed using SHA256, otherwise , user.email_sha256 is used. [3] Normalized and hashed via SHA256. [4] See Destination setup for more details.