User Consent Guide

Passing Consent Signals Into Lotame

For clients that utilize Lotame's Consent Management Product, consent signals can be passed directly into Lightning Tag. Use this feature to inform Lotame of each user's consent preference and how they are handled within the DMP.

// Callback that runs when setConsent() completes
function setConsentCb(returnData) {};

// Set these as true or false as per the signals from your User Consent process
var customerConsents = {
  analytics: true,
  crossdevice: true,
  datasharing: true,
  targeting: true
window.lotame_<lotameClientId>.cmd.push(function() {
  window.lotame_<lotameClientId>.setConsent(setConsentCb, <lotameConsentClientId>, customerConsents);

Important Note: If this is your first time using Lotame's consent signals, please be sure to set your Consent Policy by Region by sending the relevant info to support@lotame.com. The relevant info can be found under the "Consent Policy Region Implementation" section from the following article: https://my.lotame.com/t/60h3nwl/overview-of-gdpr-with-lotames-consent-api

Callback Data

The following table describes the possible responses that could be contained in the returnData object provided to your callbacks:

Return State Return Object Format Description
  "profileId": "LOTAME_PROFILE_ID",
  "consent": [{
    "lastupdate": UTC_SECONDS,
    "types": [{
      "name": "analytics",
      "consent": true
    }, {
      "name": "targeting",
      "consent": true
    }, {
      "name": "datasharing",
      "consent": true
    }, {
      "name": "crossdevice",
      "consent": true


The Lotame DMP recorded the consent signals as indicated and will enforce them going forward. The Lotame Consent API will only store and return here signals that you’ve explicitly provided via a set call (i.e. the types array could be empty).
Browser opted out of Lotame cookies
{"error": 200}


The Lotame DMP is unable to store or enforce consent.
Could not write cookie
{"error": 201}


The Lotame DMP is unable to store or enforce consent.
Consent Collection not enabled
{"error": 202}


The client id is not configured to store or enforce consent.
Upvote Follow
  • 2 wk agoLast active
  • 234Views
  • 1 Following
Log In