Active Consent - Lotame Pixels

OVERVIEW

Lotame’s Active Consent allows clients to communicate whether user consent was obtained by passing an active consent flag directly into a Lotame pixel. This article will review how active consent can be passed into Lotame pixels.

---

Important:

• IAB’s TCF 2.3 framework is the required methodology for signaling consent in GDPR Countries*. Contact your account representative if you cannot meet this requirement. 

• Lotame is NOT a CMP
  • Lotame is not a system of record for consent and does not obtain consent from users or store consent for use as evidence whether a client obtained lawful consent from a user. 
  • Lotame Active Consent is a tool to instruct Lotame on when to collect and process data or not. 

• In countries where consent IS REQUIRED under the applicable law to collect and process personal data, the partner is required to obtain end-user consent. The party calling Lotame’s pixel can communicate that consent was obtained by including lac=y when initiating the call [or communicate that consent was not obtained by setting lac=n]. 

  • Note - The IAB Transparency and Consent Framework (TCF) can be used in the GDPR Countries 
• In countries where consent IS NOT REQUIRED under the applicable law to collect and process the personal data being provided to Lotame, the party calling Lotame’s pixel is required to indicate that consent is not required by including lac=y.

Passing Active Consent Signals Into Lotame Pixel 

Overview

A Lotame pixel is a non-JS HTTP call that can be made directly to Lotame. Lotame supports various pixel versions, including:

1. Web-Based Data Collection Pixel 
2. Mobile App / CTV Data Collection Pixel 
3. Web-Based Cookie Syncing Pixel 
4. Audience Extraction API Pixel 

Consent can be signaled to Lotame using the parameter lac=y|n

• lac=y - signals you have the proper consent to call Lotame
• lac=n - signals that you do not have proper consent 
• Note - if the lac parameter is missing or lac=n, then the request will be rejected by Lotame. 

Important - If you are configured to use TCF in the EEU/EEA, the UK, and Switzerland ("GDPR Countries"), you must pass the TC string for users in GDPR Countries. Details are found in our Transparency and Consent Framework (TCF) 2.3 document.

Passing Consent Examples

Web-Based Data Collection Pixel

<img src="https://bcp.crwdcntrl.net/5/c=CLIENT_ID/lac=y/int=sports" width="1" height="1"/>

Mobile App Data Collection Pixel

<img src="https://bcp.crwdcntrl.net/5/c=CLIENT_ID/ua=[idfa|aaid]/uid=[MAID_IFA_VALUE]/lac=y/int=sports" width="1" height="1"/>

Web-Based ID Syncing Pixel

<img src="https://sync.crwdcntrl.net/qmap?c=CLIENT_ID&tp=NAMESPACE&tpid=PARTNER_USER_ID&lac=y" width="1" height="1"/>

Audience Extraction API

<script type="text/javascript" src="https://ad.crwdcntrl.net/5/c=CLIENT_ID/pe=y/var=ccauds/lac=y"></script>