Release Notes
Administration
Updates and fixes
Tealium’s infrastructure is being expanded to maintain seamless operations with increased server-side traffic. We are adding IP addresses to all of our data processing regions.
If you are using allowlists (also known as safelists or whitelists), include the new IP addresses to continue operating without increased error rates.
The additional IP addresses will be introduced on the following dates:
- Apr 29, 2024 - US (Oregon)
- May 6, 2024 - EU (Ireland and Frankfurt)
- May 13, 2024 - APJ (Hong Kong, Sydney, Tokyo)
- May 20, 2024 - US (US East 1)
If the new IP addresses are not added to your current allowlist before the roll-out date, you may notice increased connector errors, function action errors, and files not being read from non-S3 file services.
For a full list of IP addresses to allow and how to test your configuration for any issues after the change, see Tealium IP addresses to allow.
API
Updates
- V3 Visitor Privacy and V3 Visitor Profile APIs are now available under General Availability (GA).
Client-side consent management
Updates and fixes
- Updated the Consent Manager
cmGeneral
template to v3.1.0, addingtealiumConsentRegister
functionality to make consent signals easier to access.
Client-side tags
Updates and fixes
- Updated the Google Ad Manager 360 Audience Pixel tag to fix an issue where the Network Code and Segment ID fields for the tag configuration were not saving.
- Update the Trade Desk Universal Pixel tag to add custom parameters in Standard data mapping category.
Consent Integrations
Updates and fixes
- Added click to edit functionality for rows in overview tables (integrations, exemptions, and purpose groups) in Consent Integrations.
Data layer
Fixes
- Fixed an issue where applying a data layer variable that contains special characters to a page view event would result in a JavaScript error that prevented iQ Tag Management from loading.
- Updated event trigger variables executed in
utag.js
to no longer have extra single quotes ('
) added into the resulting value if the value contains double quotes ("
).
Data mappings
Fixes
- Fixed an issue where variables deleted from the New Tag window failed to delete.
Events
Updates and fixes
- Update to YouTube event to resolve issue with collecting video data.
Extensions
Updates and fixes
- Fixed an issue with the jQuery onHandler extension where localStorage and sessionStorage variables were incorrectly available in the variables menu.
Labels
Fixes
- Corrected an issue where labels are lost when an error occurs during a label request.
Load rules
Fixes
- Updated Load Rules screen to add an icon and count for consents associated with the load rule.
Moments API
Updates
- Now available under General Availability (GA). Moments API is the Tealium flagship personalization API for real-time moments that matter.
Remote commands
- Updated Braze SDK version to support Apple privacy manifest requirements.
Save and publish
Updates and fixes
- Enhancements to the Publish Details table in the Save/Publish screen. Information is more granular which enables better filters, sorting, and searching.
Server-side administration
Fixes
- Updated the server-side versions screen to fix incorrect date formatting in the calendar.
Server-side connectors
Updates and fixes
- Updated the Snapchat Conversions connector to rename the following actions:
- V2(older version) to Send Conversion V2.
- V2(newer version) to Send Conversion V3.
- Updated the Sailthru connector to allow mapping arrays when mapping user attributes.
- Updated the Webhook OAuth2 (3-Legged) and Webhook OAuth2 (2-Legged) connectors to have the same actions as the standard Webhook connector.
- Removed the following deprecated connectors:
- Nexmo
- CallRail
- Co-SENDER
- AutoPilotHQ
- Apsalar Events
- AppLovin
New connectors
- New marketplace connector: Snowflake Streaming connector
Server-side consent management
Fixes
- Exposed the Global Privacy Control header (Sec-GPC) as
global_privacy_control_opt_out
in incoming event payloads.- No event-level attribute is automatically added.
- Possible values are
true
, (Sec-GPC: 1),false
(Sec-GPC:0) or unassigned (if there is no header). - For more information about GPC and how to respect the GPC signal with Tealium, see About Global Privacy Control.
- Removed consent-based filtering of Tealium consent change events in EventStream.
- These events can now be streamed to any consent logging destination.
- There are no changes to consent-related filtering of other events or AudienceStream behavior.
Tags
Updates and fixes
- Updated the Tags screen to hide the Run Tag Template Status Checker button for client-side profiles without access.
Tealium for .NET MAUI
- Updates to our NuGet packaging. Due to changes in the packaging format, users on version 1.0.0 may experience issues.
Tealium for Android (Java)
For a complete list of changes to Tealium for Android, see the GitHub change log.
- Gradle updates, and Android
compileSdkVersion
andtargetSdkVersion
increased to version 33 for all modules.
Tealium for Android (Kotlin)
For a complete list of changes to Tealium for Android (Kotlin), see the GitHub change log.
- Core 1.6.0
HttpClient
now supports only retrying on response codes that support retries.- Fix:
ResourceRetriever
refresh interval affecting library settings being fetched too often. - Fix: Reinstated missing
ResourceEntity
class
- RemoteCommandDispatcher 1.4.0.
- Adding a RemoteCommand with a remote URL config now supports falling back to loading from an
Asset
named{command id}.json
on the first launch.- If a file name is also provided, then it will use that name to lookup the
Asset
. - It is now safe to omit the
.json
extension on thefilename
parameter when adding a new remote command, although the.json
extension of the actual file should still be present. - Fix: Refresh interval was not being adhered to
- If a file name is also provided, then it will use that name to lookup the
- Updated the module dependency minimum on
com.tealium:kotlin-core
to1.6.0
.
- Adding a RemoteCommand with a remote URL config now supports falling back to loading from an
- TagManagementDispatcher 1.2.2
- The webview is refreshed on new sessions to ensure that the latest IQ configuration is available.
Tealium for Cordova
- Upgrade native iOS and Android Tealium dependencies to the latest versions.
- Target XCode 15 for iOS and bump iOS minimum deployment target to iOS 12.
- Fixed Firebase plugin installation ordering issue that could cause Firebase not to work if installed before the main plugin.
Tealium for Flutter
- Updated iOS dependencies to support XCode 15.
- Increased minimum iOS deployment target to 12.0.
- Updated Android dependencies to the latest version.
Tealium for iOS (Swift)
Medium Impact Changes
- Improved local
RemoteCommands
to accept files path with or without the extension - Fixed remote commands and remote settings refresh mechanism and caching
- Improved remote commands and remote settings retry mechanism
- Allow URL
RemoteCommands
to use a bundled local file with thecommandId
as the name while downloading the remote file or if it can’t be downloaded and is not cached - Added a
TagManagementWebview
refresh after a session is expired
Tealium for Java
- Removed unnecessary reference to
javax.xml.ws.http.HTTPException
to support newer JDKs without additional dependencies.
Tealium for Nativescript
- Kotlin dependency upgraded to 1.4.1
- Swift dependency upgraded to 2.6.4
- Added
overrideCollectProfile
,overrideCollectDomain
, andsessionCountingEnabled
keys to the config - Added
gatherTrackData
method to Tealium instance
Tealium for React Native
- Updated Android
build.gradle
files to allow the use of Kotlin version from parent project.
Tealium for Xamarin
- Updated Tealium native libraries dependencies. Tealium Swift
2.9.1
and Tealium Kotlin1.5.1
. - Implemented methods to support visitor switching:
- Added support for config option
visitorIdentityKey
to specify the key used to identify multiple users the app. - Added the method
ResetVisitorId()
to clear and generate a new visitor ID. - Added support for config option
clearStoredVisitorIds
to clear all stored visitor IDs on the device.
- Added support for config option
- Added the config option
overrideConsentCategoriesKey
to override the name of the consent categories attribute sent in consent events.
Tealium Insights
Updates
- Updated to enable custom dashboards to be exported and imported.
Tealium Universal Tag (utag.js)
Update your utag.js
template to take advantage of the latest fixes and enhancements.
utag.js
version 4.50 or laterWe recommend the following steps to ensure a smooth transition when updating to version 4.50 or later:
Be sure to update the Tealium Collect tag and all active Consent management templates, especially the Event Logging feature.
-
If you have multiple iQ profiles running on the same site, complete these steps to ensure that all instances of
utag.js
on your site start using the new cookie behavior simultaneously, preventing conflicts or compatibility issues:- Update all
utag.js
templates to the latest version. - Set the
split_cookie
override tofalse
on each profile to use legacy cookie behavior and maintain compatibility with older versions of utag.js still running on your site for the duration of the transition. - Once all
utag.js
templates have been updated and are setting thesplit_cookie
override to maintain the legacy cookie behavior, you can remove the cookie override on all profiles at the same time.
- Update all
-
If you have dependencies on the Visitor ID (
v_id
) outside of the Tealium Collect tag, set thealways_set_v_id
option totrue
to ensure that value continues to be set in time. The most common examples of Visitor ID use are:- Cookie sync tags.
- Mapping
tealium_visitor_id
to an analytics tag such as Adobe or GA4 for troubleshooting and use in downstream data warehouses.
For more information, see Settings: always_set_v_id
.
(September 2023)
- Fixes cookie expiration issues, including one in specific browser and timezone/region settings when using
utag.js
version 4.50.
(September 2023)
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
.
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, setsplit_cookie
tofalse
. - Moves responsibility for
utag_main_v_id
fromutag.js
to the Tealium Collect tag. To forceutag.js
to set theutag_main_v_id
cookie, setalways_set_v_id
totrue
. - Adds a new
id
element in the Consent Manager cookie for logging consent. When this cookie is first set, it will match anyutag_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 tofalse
to use the legacy single multi-value cookie.split_cookie_allowlist
- Specifies an array cookie names that can be set using theutag_main
namespace.always_set_v_id
- Forcesutag.js
to set theutag_main_v_id
cookie or thev_id
component ofutag_main
.
- Updates the following templates:
utag.js
(loader
) to version 4.50, to update cookie behaviorcmGeneral
to version 3.0.12, to add centralized logic for generating or retrieving a device ID that can be called from consent logging templatescmDoNotSell
to version 1.4.0, to call the centralized logicfullConsentEventHandler
to version 1.0.3, to call the centralized logicpartialConsentEventHandler
to version 1.0.3, to call the centralized logicCollect
to versiontv:20064.20230519
(released in May 2023)
For more information about the new settings for enhanced transparency in utag 4.50 or later, see Enhancing Cookie Transparency with utag 4.51.
Templates
Updates and fixes
- Fix an issue that incorrectly allowed inherited tag templates to be editable. Inherited tag templates are now read-only.
Trace
Updates and fixes
- Fixed a rendering issue so that image or non-text responses will no longer be displayed.