How to fire Third party extension ( Facebook, Twitter ) based on cookie consent ( either using JavaScript / OneTrust) GDPR law | Community
Skip to main content
Gokul_Agiwal
Community Advisor
Gokul_AgiwalCommunity Advisor
Community Advisor
July 29, 2020
Solved

How to fire Third party extension ( Facebook, Twitter ) based on cookie consent ( either using JavaScript / OneTrust) GDPR law

  • July 29, 2020
  • 1 reply
  • 4250 views

Hello All, 

 

As per the GDPR laws have mandated that organisations can no longer rely on passive consent for cookies

 

The ECID itself have an ability to wait for opt-in before firing. For that purpose the Opt-in service is a JavaScript library bundled with Experience Cloud ID (ECID) and exists in Visitor JS in the global  adobe object as the adobe.optIn object. 

 

But wondering how we can wait for other Third party extension including (Facebook, Twitter, LinkedIn) not to fire on page load but fire only when consent provided. 

 

I'm looking either using OneTrust (Consent management platform / Plain JS ) solution.

 

Thanks in advance.

@andrey_osadchuk  @analytics_union @thebenrobb @pratheeparunraj 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by kevalytics

Hi @gokul_agiwal , 

Consent Management Platforms (CMPs) like OneTrust or TrustArc store the visitors' opt-in preferences in dedicated cookies. As part of their services, they usually perform a cookie audit and provide an audit spreadsheet. Then, they then ask the website owners to categorize all cookies into different buckets. The terminology differs from vendor to vendor but most of the time, you see at least 3 cookie categories: 

  1. Essential Cookies
  2. Statistics/Analytics Cookies
  3. Marketing Cookies

Depending on the visitors' preferences, the CMP cookies have different values. I recommend asking the CMP vendor to provide you their documentation. Most CMP vendors already have pre-written implementation guides for GTM & Launch.

Even if they don't have one for Launch yet, the logic is always the same and you can simply Adobe-tize any tag manager implementation guide they have. For instance, Variables in GTM translate to Data Elements in Launch, Tags in GTM translate to Rules in Launch. 

What you can do in Launch: 

  1. Set up data elements that read the CMP cookies
  2. Use the data elements as conditions in your rules
    1. Type "Regular" - Fire the rule only if the cookies have the necessary values
    2. Type "Exception" - Prevent the rule from firing if the cookies don't have the necessary values 

 

1 reply

kevalytics
kevalyticsAccepted solution
Level 2
July 30, 2020

Hi @gokul_agiwal , 

Consent Management Platforms (CMPs) like OneTrust or TrustArc store the visitors' opt-in preferences in dedicated cookies. As part of their services, they usually perform a cookie audit and provide an audit spreadsheet. Then, they then ask the website owners to categorize all cookies into different buckets. The terminology differs from vendor to vendor but most of the time, you see at least 3 cookie categories: 

  1. Essential Cookies
  2. Statistics/Analytics Cookies
  3. Marketing Cookies

Depending on the visitors' preferences, the CMP cookies have different values. I recommend asking the CMP vendor to provide you their documentation. Most CMP vendors already have pre-written implementation guides for GTM & Launch.

Even if they don't have one for Launch yet, the logic is always the same and you can simply Adobe-tize any tag manager implementation guide they have. For instance, Variables in GTM translate to Data Elements in Launch, Tags in GTM translate to Rules in Launch. 

What you can do in Launch: 

  1. Set up data elements that read the CMP cookies
  2. Use the data elements as conditions in your rules
    1. Type "Regular" - Fire the rule only if the cookies have the necessary values
    2. Type "Exception" - Prevent the rule from firing if the cookies don't have the necessary values 

 

    J
    jamesb37349107
    New Member
    September 22, 2020

    Hi @kevalytics @gokul_agiwal 

    We've having an issue in that using the OneTrust autoblock feature it's preventing Launch script running, therefore what cookies are required to run to enable Launch which are GDPR compliant as if its the AMCV cookies these track the user, so aren't compliant.

     

    We require all cookies to be block and on acceptance the relevant cookies fire enabling first page tracking of Adobe Analytics

     

    Thanks

    James

    C
    clairea39507456
    Level 2
    January 27, 2022

    Hi jamesb37349107,

    We are having a similar issue, although not using Launch, whereby OneTrust is blocking first page tracking upon acceptance of cookies. Did you get round your issue? If so, do you have any insights to share?

    Cheers,

    Claire

    Terms & ConditionsAccessibility statement

    Loading footer...