The ATS Mobile SDK allows you to handle envelopes without having to spend time coding. The SDK includes the ability to retrieve, refresh, and cache envelopes while ensuring that user consent is respected.
You must have an approved ATS placement to which you can link the SDK configuration. If you don't have an ATS placement yet or want to create a new one, see Submit Domains/Bundle IDs for Privacy and Data Ethics Review.
Subscribe to the ATS Mobile SDK product from the Marketplace.
Obtain Config ID for ATS Mobile SDK Before initializing the SDK, you must first obtain the Config ID in Console.
A Config ID will be automatically generated and displayed in the "SDK Configurations" area.
To install LRAtsSDK in a Swift application
Please see our documentation.
The SDK will automatically perform a geolocation check to ensure consent is properly set for GDPR and CCPA. Learn what this means for your application below:
To successfully initialize and use the SDK, user consent needs to be present per IAB standards (ie: in NSUserDefaults). The SDK will fail to initialize if there is no consent given for TCF purposes 1 to 10 and if LiveRamp is not listed as a vendor (ID 97). If you are running the SDK outside of the GDPR and CCPA legislations, you can set the default consent state with the following method: LRAts.shared.hasConsentForNoLegislation. Dynamic TCF and CCPA consent monitoring and handling is applied. This ensures if consent is revoked, SDK will reset (clear cached data) and all SDK-related APIs will stop working. The SDK will automatically re-initialise and APIs will work again if consent is given during lifecycle of the application.