Fixes cookie expiration issues, including one in specific browser and timezone/region settings when using utag.js version 4.50.
Version 4.50 provides more transparency and control over cookies written by utag.js.
Previously, we recommended using multi-value cookies (multicookies). However, due to the increasing demand for transparency and simplicity, particularly for data privacy audits, we have revised our recommendation. Now, we advise using standalone cookies, which is now the default behavior in utag.js.
Be sure to update the Tealium Collect tag and all active Consent management templates, especially the Event Logging feature, when you update to utag.js version 4.50.
This release includes the following updates:
Writes separate utag_main cookies instead of a single multi-value cookie. To use the legacy behavior that stores multiple values in a single cookie, set split_cookie to false.
Moves responsibility for utag_main_v_id from utag.js to the Tealium Collect tag. To force utag.js to set the utag_main_v_id cookie, set always_set_v_id to true.
Adds a new id element in the Consent Manager cookie for logging consent. When this cookie is first set, it will match any utag_main_v_id values found, after which it won’t be changed. That behavior prioritizes maintaining the link between the user and the logged events, but means that a match isn’t guaranteed in all cases.
Can easily be upgraded by updating the relevant templates.
Adds the following utag settings:
split_cookie - Set to false to use the legacy single multi-value cookie.