Google Universal Analytics

Google is a multinational technology company focusing on online advertising, search engine technology, cloud computing, and computer software. Google Universal Analytics (UA) is a web analytics service that tracks and reports website traffic. Using this destination, you can take advantage of the Measurement Protocol by sending data via server-side. This version is related to the previous generation of Google Analytics. See Google Analytics 4 destination for the newest and recommended version.

Google Universal Analytics will be deprecated on July 1, 2023, meaning it will stop processing data. Analytics 360 properties will stop working on October 1, 2023.

Key features

The Google Universal Analytics destination provides the following key features:

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

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

• Refined data: you can freely push additional information based on your specific needs (E.g. adding custom events and custom properties).

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

Destination setup

Configuration

Settings	Description
Tracking ID	Required The tracking identifier is a string like "UA-XXXXXX-Y". It must be included in your tracking code to tell Analytics which account and property to send data to.
Custom Event Properties	Map your custom event properties by setting their field names in Event property name and adding the field name holding the value in Commanders Act event property or static value. E.g. if you inputsizein the Event property name anditems.0.product.size [1] in Commanders Act event property or static value, you will have a custom event property in GA4 calledsizewith a value based on the content of the fielditems.0.product.size. You also have the option to set a static string/numeric value in Commanders Act event property or static value. In the column Commanders Act event property position you should keep the value Default as it better fits most scenarios. E.g. this can be used to set Custom Dimensions and Metrics and/or Content Groups. In case you select either In "Item List" (E.g. {items.X}) or In "Item List" Product (E.g. {items.X.product}) this destination will look for the input event property starting from the items or product level respectively and add Product Custom Dimensions and/or Product Custom Metrics depending on your input Event property name. If you select In "Item Impression List" (E.g. {items_impression.X}), you will add Product Impression Custom Dimensions and/or Product Impression Custom Metrics still depending on your input Event property name.
Client Id Cookie Name	Cookie name holding the Google Analytics "Client Id" that uniquely identifies a user instance of a web client. Default value: "_ga". The "Client Id" is the right most string in the cookie, including a single dot. E.g. see the following blue highlighted string "GA1.1.XXXXXXXXXX.XXXXXXXXXX".

[1] Using "dots" (".") you can navigate deeper to the specific field you want to get the value of. See Events reference for more details on the standard field names by event. You can also freely set custom fields: there are no boundaries.

Quick reference

As recommended by Google, Enhanced Ecommerce hits are used in place of Ecommerce hits. See more details on UA "Hit Types" following this LINK.

Commanders Act Events	UA Hit Types
add_payment_info add_shipping_info begin_checkout page_view purchase	pageview [1] screenview [1]
add_to_cart add_to_wishlist generate_lead login refund remove_from_cart search select_content select_item sign_up view_cart view_item view_item_list [Custom Event]	event
[Custom Event]	social [2]

[1] This is eitherpagevieworscreenview, depending if the "Smart Mapping" field App Name (an)is set with an empty value or a non-empty one. [2] You can specify a custom social event by setting the "Smart Mapping" field Social Event.

Field mappings

Most properties can be remapped using our "Smart Mapping" feature.

Commanders Act Properties	UA Properties
Tracking ID	tid
partners.ga.client_id Client Id Cookie Name user.tcId	cid [1]
user.id	uid
context.device.ip	uip [2]
partners.ga.ad_id	gclid
context.page.url	dl
context.page.title	dt
context.page.referrer	dr
context.page.url	dh [3]
context.page.url	dp [3]
id	ti
value	tr
shipping_amount	ts
tax_amount	tt
coupon	tcc
partners.ga.affiliation	ta
currency	cu
partners.ga.product_action [Default Value]	pa [4]
partners.ga.event_category	ec [5]
partners.ga.event_action event_name	ea [6]
partners.ga.event_label search_term item_id method	el [7]
items.X.id	pr(X+1)id
items.X.product.name	pr(X+1)nm
items.X.product.category_1 / items.X.product.category_2 / items.X.product.category_3 / items.X.product.category_4 / items.X.product.category_5	pr(X+1)ca
items.X.product.brand	pr(X+1)br
items.X.variant	pr(X+1)va
items.X.list_position	pr(X+1)ps
items.X.product.price	pr(X+1)pr
items.X.quantity	pr(X+1)qt
items.X.coupon	pr(X+1)cc
items_impression.X.0.list_name	il(X+1)nm
items_impression.X.Y.id	il(X+1)pi(Y+1)id
items_impression.X.Y.name	il(X+1)pi(Y+1)nm
items_impression.X.Y.brand	il(X+1)pi(Y+1)br
items_impression.X.Y.category_1	il(X+1)pi(Y+1)ca
items_impression.X.Y.variant	il(X+1)pi(Y+1)va
items_impression.X.Y.list_position	il(X+1)pi(Y+1)ps
items_impression.X.Y.price	il(X+1)pi(Y+1)pr
items_promotion.X.id	promo(X+1)id
items_promotion.X.name	promo(X+1)nm
items_promotion.X.creative	promo(X+1)cr
items_promotion.X.position	promo(X+1)ps
items_promotion.X.action	promoa
partners.ga.campaign_name	cn
partners.ga.campaign_source	cs
partners.ga.campaign_medium	cm
partners.ga.campaign_keyword	ck
partners.ga.campaign_content	cc
partners.ga.campaign_id	ci
partners.ga.queue_time	qt
context.app.name	an
context.app.namespace	aid
context.app.namespace	aiid
context.app.version	av
context.page.title	cd
(partners.ga.event_npa)	npa [8]
(partners.ga.non_iteration)	ni [9]
partners.ga.checkout_step	cos
partners.ga.checkout_step_option	col
partners.ga.social_name	sn
partners.ga.social_action	sa
partners.ga.social_action_target	st
Custom Event Properties	[Custom Property Name] [10]

[1]partners.ga.client_idhas priority overClient Id Cookie Nameanduser.tcId. [2] Always anonymized just as thoughaip(anonymize IP) is used. [3] Retrieved by parsing the provided "Smart Mapping" fieldDocument Location (dl). [4] Ifitemsis not set, then this property won't be present. Ifpartners.ga.product_actionis not set, depending on the incoming event, the following values are used as default:detail(page_view event or if your event is not one of the following being listed),purchase(purchase event),click(search, add_to_wishlist, login, select_content, select_item, sign_up, view_cart, view_item and view_item_list events),refund(refund event),checkout(begin_checkout, add_shipping_info and add_payment_info events),add(add_to_cart event), remove(remove_from_cart event). [5] Ifpartners.ga.event_categoryis not set, since this property is required for "event" hit types, this gets the default value:UX. [6] Ifpartners.ga.event_actionis not set, then your event name is used. [7] Ifpartners.ga.event_labelis not set, depending on the incoming event, the following fields are used as default:search_term(search event),item_id (select_content event) andmethod(sign_up and login events). [8] Ifpartners.ga.event_npais set with one of the following values:1(string or integer) ortrue(boolean), thennpais set with1. [9] Ifpartners.ga.non_iterationis set with one of the following values:1(string or integer) ortrue(boolean), thennpais set with1. [10] SeeCustom Event Propertiesin Configuration for more details on how you can bridge custom properties to UA.