Skip to main content

Release Notes, March 10, 2022

Hi everyone!

Today's release features some new and much requested improvements. We greatly appreciate all your feedback, so please keep it coming. You will notice that the design of Console has changed. In the coming weeks we will be updating the Console design even further to bring it in line with LiveRamp’s new branding.

ATS Mobile SDK

New

  • ATS Mobile SDK is now available for app publishers as a part of our closed beta program. The ATS SDK will allow apps to monetize their logged-in (authenticated) user base. If you would like to get started, please reach out to ats@liveramp.com to speak with our team to learn more.

ATS

New

  • New level of permissioning has been introduced for ATS and ATS.js. User access permissions to specific ATS Placements and ATS JS configurations can now be individually controlled. More info on this topic can be found here.

Improved

  • Unnecessary polyfills and code to support IE11 have been removed, reducing the overall library size by 15%.

LaunchPad

Improved

  • The trigger condition for ATS now uses "contains" instead of "equals".

Privacy Manager for Web and AMP

Improved

  • Unnecessary polyfills and code to support IE11 have been removed, reducing the overall library size by 22%.

  • The granularity of the timestamp in the TCstring has been reduced to comply with the latest changes in the TCF policy.

  • The vendors are now shown in alphabetical order in the Privacy Manager UI vendors overview.

  • We have added additional types for Google Consent Mode.

  • The functionality to force the vendor’s legal basis to consent has been improved to only include TCF vendors.

Privacy Manager for Mobile In-app

Improved (iOS v1.1.9 and Android v1.1.11)

  • The granularity of the timestamp in the TCstring has been reduced to comply with the latest changes in the TCF policy.

PreferenceLink

New

  • It’s now possible to manually set a token for webhook encryption and webhook signature.

Improved

  • In TCF Adapter the granularity of the timestamp in the TCstring has been reduced to comply with the latest changes in the TCF policy.

In this section: