When updating to a newer version of UTAG, it is important to do thorough testing to ensure that changes made progressively throughout the different versions do not alter the tags firing or the data being sent with the tags. Ideally, once UTAG is updated to a newer version, the tags and the data sent with the tags should remain identical to the previous UTAG version. If the profile's version of UTAG is being updated, follow the steps below to ensure the profile retains its integrity.
In This Article:
Before updating, it's important to know which version of UTAG is currently running on the website as a starting point. If you have the Universal Tag Debugger tool, run it on your site and note the version number at the top right of the tool.
To retrieve the utag.js version from the browser console:
Based on the current UTAG version running on the website, there may be many changes that have occurred between that version and the latest version. It's always a good idea to read through all of the changes before updating your version. The release notes can be accessed here.
Since the changes made to the UTAG version are global (it is a profile template, which means the changes are implemented regardless of version publish or environment), it is recommended to ensure that all publish environments are identical before updating. That way the QA process only needs to occur once and will cover all environments.
We recommend creating a local copy of the UTAG version template before updating to the latest version. Should any issues occur, it makes it easier to roll back to the previous version.
Follow the instructions to update your UTAG Loader template .
Once the version is updated and published to a test environment, it is recommended to thoroughly test all load rules, tags, and extensions to ensure they match how they were sent in the previous version. Refer to the charts below for items to review when verifying the profile.
Review the data coming into each vendor's platform to ensure that it matches the data that was collected with the previous version. If the data seems off, it could be that an extension or mapping was affected by the update and needs to be corrected.
When validating a UTAG update, it's recommended to initially publish the update to a testing environment (DEV/QA) to preserve the original setup in PROD. The two versions can then be tested side by side to ensure that the tags and network requests align between versions, along with any data sent with tags.
|Profile Settings||If S2S was being used, note that support was removed completely. (Removed legacy s2s support, as this was previously removed from Tealium iQ)|
|Tags||If "Privacy Manager" is being used, check tags to ensure they are firing as expected based on cookie settings. (The OPTOUTMULTI cookie is re-checked with each call to utag.view() and utag.link().Tags triggered directly by UID also checks the OPTOUTMULTI cookie settings before firing)|
Review the chart above AND
Review BOTH charts above AND