June 1, 2018
Tealium Universal Tag (utag.js)
- Adds support for the following new built-in variables:
tealium_session_number
- a duplicate of the existing value inutag.data['cp.utag_main__sn']
tealium_session_event_number
- the cookie value inutag.data['cp.utag_main__se']
that counts the number of tracking calls (utag.view()
,utag.link()
) in the current session (visit). This is useful for Single Page Apps (SPAs) where there is only one page load with many tracked events on that page. For pages using thenoview
flag, the value is ‘1’ for both page load (load rule evaluation) and the first call toutag.view()
.
- Adds support for an empty param list passed into
utag.link
,utag.view
orutag.track
calls. In previous versions, calls toutag.link()
orutag.view()
work fine, but gets an extracfg
object added to the data layer. Calls toutag.track()
causes an exception in previous versions. - For pages using
noview
flag, there are two things to keep in mind:- The data layer will have a ‘1’ value for
tealium_session_event_number
for both page load (utag.js
uses data layer to loads in tags) and first call toutag.view
(which fires tags and/or loads in more tags.) - Because cookies are used and initialized at page load time, if the
utag.view
call does not happen in time on the first page, and the page is refreshed in browser, it moves to ‘2’ for the firstutag.view
call which happens on second page. This is an edge case since most implementations callsutag.view
immediately afterutag.js
executes.
- The data layer will have a ‘1’ value for
- This update also includes fixes for the “OU” function used by legacy Privacy Manager Extension.
- The OPTOUTMULTI cookie is re-checked with each call to
utag.view/link
(no page refresh required) - Tags fired directly by tag’s UID also checks the OPTOUTMULTI cookie settings before firing
- The OPTOUTMULTI cookie is re-checked with each call to