Platforms release notes

Remote commands

• Updated Braze SDK version to support Apple privacy manifest requirements.

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 and targetSdkVersion 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.

• BugFix: ProGuard adjustment resolve missing BatchDispatch$Companion class.
• Minor lint warning fixes

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)

Low Impact Changes

• Fixed Privacy Manifest NSPrivacyAccessedAPITypeReasons for the disk space category.

Tealium for Nativescript

• Kotlin dependency upgraded to 1.4.1
• Swift dependency upgraded to 2.6.4
• Added overrideCollectProfile, overrideCollectDomain, and sessionCountingEnabled 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 Kotlin 1.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 the config option overrideConsentCategoriesKey to override the name of the consent categories attribute sent in consent events.

Tealium Universal Tag (utag.js)

Update your utag.js template to take advantage of the latest fixes and enhancements.

We 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:

  1. Update all utag.js templates to the latest version.
  2. Set the split_cookie override to false 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.
  3. Once all utag.js templates have been updated and are setting the split_cookie override to maintain the legacy cookie behavior, you can remove the cookie override on all profiles at the same time.

• If you have dependencies on the Visitor ID (v_id) outside of the Tealium Collect tag, set the always_set_v_id option to true 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, 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.
  • split_cookie_allowlist - Specifies an array cookie names that can be set using the utag_main namespace.
  • always_set_v_id - Forces utag.js to set the utag_main_v_id cookie or the v_id component of utag_main.
• Updates the following templates:
  • utag.js (loader) to version 4.50, to update cookie behavior
  • cmGeneral to version 3.0.12, to add centralized logic for generating or retrieving a device ID that can be called from consent logging templates
  • cmDoNotSell to version 1.4.0, to call the centralized logic
  • fullConsentEventHandler to version 1.0.3, to call the centralized logic
  • partialConsentEventHandler to version 1.0.3, to call the centralized logic
  • Collect to version tv: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.