Google Universal Analytics
This section discusses how to migrate the Adobe-built Google Analytics (Universal Analytics) extension to the Acronym-built Google Site Tag (gtag) extension.
Adobe's Google Analytics (Universal Analytics) extension uses Google's
analytics.js, which Google will likely deprecate in the next year or two.
analytics.jsand is considered as a single library for all of Google's marketing products, hence the "global site tag" name. It is important to keep in mind that migrating between
gtag.jsis not exact and some features were deprecated or automated.
The following sections cover the settings that exist in the Universal Analytics extension and where they should be mapped within the account configuration in the Gtag extension. It is highly recommend to read and understand how to configure the extension before making a migration. For almost all N/A values they no longer exist for the gtag library.
Currently, custom locations / library code is not supported by our extension.
These settings are the most commonly set settings, and largely map to similar names / settings in the gtag extension.
Unfortunately, Google has removed the ability to change the URL parameter keys for each of the campaign details. However, you can overwrite the campaign information (see below).
sourceare required if
idis not passed.
name: "acronym.com spring sales event",
An example of the custom campaign data element being set to overwrite campaigns.
The customize page code is roughly equivalent to the Custom Configuration Code within the gtag extension. However, it is important to note that the
trackerNameparameters will not exist, and the syntax for your custom code will very likely need to change.
The Adobe-built Google Universal Analytics extension providers three actions that can be used within your rules. This section covers how to migrate these actions to the Acronym-built gtag extension.
This action lets you send an event to Google's servers for your accounts. An event is typically an interaction on the page you want to track that may or may not require a browser refresh, such as a purchase, form submission, video view, or button click. This mirrors the Send an event action within the gtag extension.
The existing send event call, in this case for a purchase event.
Event Category, Action, Label, Value, and Non-interaction events have exact matching fields that you should migrate the values over to. For the event parameters, these can be migrated to the additional data fields. For dimensions and metrics, see Set Dimensions/Metrics for how those are now mapped in gtag. Otherwise, the data field name will provide a dropdown with hints on new key names.
The same event call, within the gtag extension.
This action lets you send a page view server call to Google — similar to what a browser load would send if the tag were directly on the page instead of in Launch. This mirrors the Send a page view action within the gtag extension.
The existing send page view options
If needed, you can set the Document Path, Title, and Location via a custom data field within the Google Analytics settings on the rule action (
A page view, passing both a custom document path and title.
Setting dimensions in metrics in gtag works differently than it did for Universal Analytics. Instead of directly updating
metricY, you must instead map the dimensions to a unified key/value pair (we call them "data fields" in the extension) that is then used in the Set persistent values action. Google has done this to provide unity across all of their products, simplifying the deployment. To map the dimensions to the data field names, you must do this within the gtag extension configuration, under the Custom Dimensions & Metrics section.
The existing set dimensions/metrics configuration
As an example, if your
dimension1is for the visitor's account type, in the extension configuration, you'd map the
The configuration for mapping the custom dimensions.
The account_type (dimension1 in Universal Analytics) being set to the value "foobar".