About the Android ATS Mobile SDK

LiveRamp Android ATS Mobile SDK provides all the tools you need to handle envelopes from Android devices more optimally without spending time on tedious codes. The SDK contains built-in functionalities to retrieve, refresh, and cache envelopes while ensuring that user consent is being respected. On Android platform, SDK is implemented as LRAtsManager.aar, which makes it compatible with applications written in Java and Kotlin programming languages.

From Version 2.0 and above, the SDK comes with a functionality to enable ATS On-Device. ATS On-Device allows you to match identifiers directly on users' devices, enabling you to handle identifiers from users who have opted out of AppTrackingTransparency (ATT) or any similar framework.

🚧
Compatibility

The ATS Mobile SDK supports Kotlin v1.6.0 and above.

The ATS Mobile SDK is available for Android API 21 (Lollipop) and above.

📘
Documentation for Version 1.0
You can find the documentation for Android ATS Mobile SDK Version 1.0 in our Identity Documentation site. If you are already running the ATS Mobile SDK, you can check which SDK version you are running by calling getSdkVersion.

🚧
ATS On-Device is Available in Closed Beta
ATS On-Device is currently available in closed beta; their functionality will not work out-of-the-box during this phase.
If you want to be part of the closed beta release, contact your LiveRamp representative to get ATS On-device enabled.

Before You Begin

You must have the following already set up in Console:

An ATS Placement tied to the bundle IDs of the apps you want to run ATS in
An SDK Config ID as illustrated below:

An Integration Key as illustrated below to enable the handling of ATT-opt-out users (or similar framework for Android) through ATS On-Device:

📘
If your ATS placement is still pending for an approval, you can still continue with the initialization. SDK configurations linked to unapproved placements will return test envelopes which you can utilize for testing purposes until the placement is approved.

See our Console documentation on Implementing ATS Mobile SDK to learn how to complete the prerequisites.

Additionally, your application must be able to handle user consent (typically by a CMP) as per IAB standards. The SDK will automatically perform a geolocation check to ensure consent is properly set for GDPR and CCPA.