Google Ads Store Sales

This destination is currently under final review and will be available soon.

Google Ads is an online advertising platform where businesses pay to show their ads across Google’s ecosystem, mainly in search results, websites, apps, and videos. Using this destination you can leverage Data Manager API to send event data for Google Ads store sales conversions.

Key features

The Google Ads Store Sales destination provides the following key features:

• Events structure: our Events reference model matches Google's event structure, 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.

• Custom properties: you can freely push custom properties based on your specific needs.

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

• Support batch mode: multiple events are sent, with a single request, instead of one at a time.

Destination setup

Store sales conversions are only available to accounts on a Google allowlist. More details are available by following this LINK.

Configuration

Settings	Description
Credentials	Required Your credentials with Google Ads as set in the Commanders Act interface following: Administration ➜ Connector Credentials ➜ Add connector credentials ➜ Google Ads
Store Identifier Property Path	Required The property path holding the value of the identifier that represents a physical store where the event happened. More details are available by following this LINK.
Mapping	Required Map your Google Ads conversion names with your events by setting the fields Google Ads Conversion Name and Your event name. The conversion name must be of the type STORE_SALES. At least one line is required. Conversion names can be found in the Google Ads interface following: Goals ➜ Summary ➜ Conversion action (column)
Custom Variables	Custom variable for ads conversions. Map your Custom variable name with Your value. More details are available by following this LINK.
Experimental Fields	Experimental fields represent unofficial fields. Map your Experimental field name with Your value. More details are available by following this LINK.
Additional User Properties	Additional user properties for the user associated with this event. Map your User field name with Your value. More details are available by following this LINK.
User identifiers from third-party	Set this flag if your user identifiers are from a third-party source.
Validate only	For testing purposes. If this is checked, the request is validated but not executed. Only errors are returned, not results.

Field mappings

Properties can be remapped using our Smart Mapping feature. The Data Manager API currently removes the entire cartData property from a store sales event if any item in the cartData is missing either of the following Google properties: merchantProductId or unitPrice. More details are available by following this LINK.

Smart Mapping Fields	Commanders Act Default Properties	Google Properties
-	Store Identifier	eventLocation.storeId [*]
Transaction Id	id	transactionId [*][1]
Transaction Value	value	conversionValue [*][1]
Currency	currency	currency [*][1]
Event Timestamp	context.event_timestamp	eventTimestamp [1][2]
User Email	user.email	emailAddress [3][4]
User Phone	user.phone	phoneNumber [3][4]
User First Name	user.firstname	address.givenName [3][4]
User Last Name	user_lastname	address.familyName [3][4]
User Country	user.country	address.regionCode [3]
User ZIP Code	user.zipcode	address.postalCode [3]
Consent adUserData	partners.google.consent_ad_user_data	consent.adUserData [5]
Consent adPersonalization	partners.google.consent_ad_pers	consent.adPersonalization [5]
Merchant Identifier	partners.google.merchant_id	merchantId [6]
Merchant Feed Label	partners.google.merchant_feed_label	merchantFeedLabel [6]
Merchant Feed Language Code	partners.google.merchant_feed_lang_code	merchantFeedLanguageCode [6]
Transaction Discount	discount_value	transactionDiscount [6]
Item List	items	items [6]
Merchant Product Id	items.X.product.id	merchantProductId [7][8]
Quantity	items.X.quantity	quantity [7][9]
Price	items.x.product.price	unitPrice [7][10]
Conversion Value	items.x.product.conv_value	conversionValue [7][11]
-	Custom Variables	customVariables.X.value [12]
-	Experimental Fields	experimentalFields.X.value [13]
Customer Type	partners.google.customer_type	customerType [14][15]
Customer Value Bucket	partners.google.customer_value_bucket	customerValueBucket [14]
-	Additional User Properties	additionalUserProperties.X.value [14][16]
User Id	user.id	userId
City	partners.google.city	city [17]
Subdivision Code	partners.google.subdiv_code	subdivisionCode [17]
Region Code	partners.google.region_code	regionCode [17]
Subcontinent Code	partners.google.subcont_code	subcontinentCode [17]
Continent Code	partners.google.cont_code	continentCode [17]

* Mandatory property. 1. Set in events.X . 2. If not passed, the current timestamp is used. 3. Set in events.X.userData.userIndentifiers.X . 4. If set in clear text, it's automatically normalized and hashed via SHA256. 5. This is automatically set if the consent is passed via client-side. Smart Mapping fields Consent adUserData and Consent adPersonalization have priority over the consent passed via client-side. 6. Set in cartData . 7. Set in cartData.items.X . 8. The product identifier within the Merchant Center account. More details are available by following this LINK. 9. Default value if not set: 1 . 10. The unit price excluding tax, shipping, and any transaction level discounts. If the item has an item scoped discount, use the discounted unit price. E.g. if an item has a unit price of 27.67 and a unit discount of 6.66, then set unitPrice to 21.01. 11. The conversion value for a single unit of this item. For example, if two units of an item are purchased for 10.00 each, set this wit 10.00 and quantity to 2. Note that while this field is optional for individual items, the Transaction Value Smart Mapping field is required. 12. See Custom Variables in Configuration for more details. 13. See Experimental Fields in Configuration for more details. 14. Set in userProperties . 15. This is automatically set if the property user.status is set with proper information. The "Smart Mapping" field Event Source has priority over user.status. 16. See Additional User Properties in Configuration for more details. 17. Set in eventLocation .