2. Provide a Valid Consent String

Based on the user's location, ATS Envelope API may require a standardized consent signal. Make sure you provide a valid consent string so you can successfully retrieve an Identity Envelope. If a user is located in a country that is outside of the EU/EEA and is not the U.S., ATS Envelope API will successfully return an envelope without the need for a consent string.

  • About GDPR: The General Data Protection Regulation (GDPR) is a "regulation in EU law on data protection and privacy in the European Union and the European Economic Area". If a user is located in an EU (or EEA, in some cases) country, consent is required.
  • About CCPA: The California Consumer Privacy Act (CCPA) is "a state statute intended to enhance privacy rights and consumer protection for residents of California, United States".

For Users in the EU/EEA (GDPR)

When calling the Envelope API for users in the EU/EEA, you will need to supply a valid TCF consent string with LiveRamp listed as a vendor (ID 97) and a positive signal for TCF purposes 1 to 10, special purpose 1 and feature 1 and 2 in order to obtain an identity envelope.

If a user revokes their consent, we suggest that you remove the identity envelope from configured storage.

See an example of a valid valid TCFv2 Consent string below:

CPSzMzJPTeGtxADABCENB_CoAP_AAEJAAAAADGwBAAGABPADCAY0BjYAgADAAngBhAMaAAA.YAAAAAAAA4AA

Validate your TCFv2 Consent string here.

For Users in the U.S. (CCPA)

When calling the Envelope API for users in the US, a Privacy String is currently not required. ATS will take an approach of "soft" enforcement to the CCPA Privacy String. If a user in the U.S. declines consent, in which case a negative string will be given, ATS API will respect the settings.

However, as adoption increases and clarity emerges on the federal level, we expect that a consent signal will be required as they do in the European Union.

If a user revokes their consent, we suggest that you remove the Identity Envelope from configured storage.

An example of a valid US Privacy Consent is as follows: 1YNN

See more examples here.

For Users in Other Countries

When calling the Envelope API for users in all other countries (outside of the EU/EEA and not the U.S.), ATS Envelope API will successfully return an envelope without the need for a consent signal.