Skip to main content


Why should I implement ATS.js on all pages?

We recommend having ATS running on every page to make sure envelopes don’t expire and opt-out signals can immediately be passed to ATS. ATS.js script handles envelope refreshes and it does so every 30 minutes. For example, when a user with an envelope returns to a page, the script refreshes the lifetime of the envelope, so it doesn't expire and can still be used. Additionally, implementing ATS.js on all pages ensures that the user's journey, from the landing page to a child content page, remains compliant and relevant for both the publisher and the brand.

What is the size of the ATS library?

The size of the ATS library is about 50 KB on network and about 145 KB decoded.

What is the size of an identity envelope with a RampID when it is stored in the first-party cookie?

An identity envelope with a RampID is about 139 bytes. Our encoded envelope (cookie name: _lr_env) is about 265 bytes and the envelope specifically created for prebid (cookie name: idl_env) is about 140 bytes. The envelope may exceed 265 and 140 bytes if the ride-along ID is enabled and other IDs, such as UID 2.0 or EUID are provided in the envelope.

The size of ATS envelopes may vary depending on your implementation. Contact your LiveRamp representative for more information.

Is the loading time faster when loading ATS via Launchpad?

There is no difference in size when loading ATS via LaunchPad but there are other benefits of using LaunchPad such as;

  • Easy implementation: There is only one tag to implement for all of your LiveRamp publisher products.

  • Easy maintenance: All configurations, product updates, and additions can be managed from Console.

  • Smaller footprint: ATS will only be loaded when appropriate conditions are met.

  • Compliance: ATS won't be loaded outside of geo-restrictions.

  • Security: ATS won't be loaded outside of the allowed domains.

Do the libraries need to register event listeners that have the potential to degrade page performance?

The libraries do not require any registration of user interaction. The ATS script loads in the background and will only be fed with identifiers whenever they become available through any form of authentication.

How do I make sure I use all of my authentication methods?

To make the most of ATS, it is crucial that all authentication methods are identified by ATS. This can be done by auditing your site to identify all areas where users provide their identifiers (ex: Newsletters, email click-throughs, social logins, on-site registrations, etc.). You can then configure your ATS tags accordingly to capture identifiers from these different authentication methods.

Once you've implemented ATS, trigger each authentication event to ensure that identifiers are being picked up and envelopes are being created. We recommend using the Logging Debugger function in the Settings of your Console configuration to troubleshoot your tag. To learn more, see Install ATS and Test Your Implementation.