Basic Requirements
Before getting started with your ATS configuration, check what's required for ATS to successfully return an envelope based on GDPR, CCPA, and other privacy laws. You will need to do the following:
Check for consent signal: For users in the UK/EU, ATS expects a TCF v2.2 compatible consent string to be present before the ATS JavaScript library can be loaded. For users in the U.S., ATS.js will check for a GPP National String or a CCPA Privacy String as a fallback. If consent is rejected, ATS.js will automatically remove the RampID envelope from the configured storage in the browser. This also means you must implement an opt-out methodology that meets local law
Create an ATS placement: Every ATS configuration requires a placement ID, which you can obtain in Console once you have submitted the domains and countries where you want to run ATS. Your placement ID is used to determine the loading rules and to make sure your property is following all LiveRamp's requirements for running ATS.
Implement an opt-out methodology: LiveRamp requires that all of its partners must establish and implement an opt-out methodology that meets local laws and regulations. The opt-out method should allow users to decide if their data can be used for targeted advertising purposes.