Adobe target - AB test on landing page with cookie consent | Community
Skip to main content
D
davidec55525142
Level 2
June 6, 2023
Solved

Adobe target - AB test on landing page with cookie consent

  • June 6, 2023
  • 1 reply
  • 2127 views

Hello,

 

we have implemented a cookie consent banner (OneTrust in our case) but we are trying to figure out a way to get it to interact with Target without affecting the customer experience.

The issue would happen when a test deployed on the landing page for a visitor who has never been on the website before. This would be the sequence of events creating the issue:

1. new visitor lands on a page where an AB test is deployed

2. the visitor sees the standard version of the page (experience A) and the cookie consent banner appears

3. the visitor accepts adobe target cookies (aka the tag can now load on page)

4. experience B might now load on the page

 

As you can see the same visitor could see 2 different versions of the page before and after cookies are accepted.

 

Has anyone found a solution for this potential issue?

 

Thanks,

 

Davide

 

    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 PratheepArunRaj

    Dear @davidec55525142 ,

    With consent in place, we have to deal with these and below are the options provided by Adobe.

    1. The Target tag is pre-approved via Adobe Experience Platform (or the data subject previously approved Target): The Target tag is not held for consent and functions as expected.

    2. The Target tag is NOT pre-approved and bodyHidingEnabled is FALSE: The Target tag fires only after consent is collected from the customer. Before consent is collected, default content only is available. After consent is received, Target is called and personalized content is available to the data subject (visitor). Because only default content is available before consent, it is important to use an appropriate strategy, such as a splash page that covers any portion of the page or content that might be personalized. This process ensures that the experience remains consistent for the data subject (visitor).

    3. The Target tag is NOT pre-approved and bodyHidingEnabled is TRUE: The Target tag fires only after consent is collected from the customer. Before consent is collected, default content only is available. However, because bodyHidingEnabled is set to true, bodyHiddenStyle dictates what content on the page is hidden until the Target tag is fired (or the data subject declines opt-in, in which case default content is displayed). By default, bodyHiddenStyle is set to body { opacity:0;}, which hides the HTML body tag. Adobe’s recommended page configuration is below so that the entire body of the page, other than the consent manager dialog, is hidden by putting the content of the page in one container and the consent manager dialogue in a separate container. 

    So, the answer is simple, you either use SPLASH kinda page or HIDE the content till the consent is approved. We don't have any other feasible options than the rest.

    Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics

    1 reply

    PratheepArunRaj
    Community Advisor and Adobe Champion
    PratheepArunRajCommunity Advisor and Adobe ChampionAccepted solution
    Community Advisor and Adobe Champion
    June 6, 2023

    Dear @davidec55525142 ,

    With consent in place, we have to deal with these and below are the options provided by Adobe.

    1. The Target tag is pre-approved via Adobe Experience Platform (or the data subject previously approved Target): The Target tag is not held for consent and functions as expected.

    2. The Target tag is NOT pre-approved and bodyHidingEnabled is FALSE: The Target tag fires only after consent is collected from the customer. Before consent is collected, default content only is available. After consent is received, Target is called and personalized content is available to the data subject (visitor). Because only default content is available before consent, it is important to use an appropriate strategy, such as a splash page that covers any portion of the page or content that might be personalized. This process ensures that the experience remains consistent for the data subject (visitor).

    3. The Target tag is NOT pre-approved and bodyHidingEnabled is TRUE: The Target tag fires only after consent is collected from the customer. Before consent is collected, default content only is available. However, because bodyHidingEnabled is set to true, bodyHiddenStyle dictates what content on the page is hidden until the Target tag is fired (or the data subject declines opt-in, in which case default content is displayed). By default, bodyHiddenStyle is set to body { opacity:0;}, which hides the HTML body tag. Adobe’s recommended page configuration is below so that the entire body of the page, other than the consent manager dialog, is hidden by putting the content of the page in one container and the consent manager dialogue in a separate container. 

    So, the answer is simple, you either use SPLASH kinda page or HIDE the content till the consent is approved. We don't have any other feasible options than the rest.

    Thank You, Pratheep Arun Raj B (Arun) | NextRow Digital | Terryn Winter Analytics

    Thank You, Pratheep Arun Raj B (Arun) | Xerago | Terryn Winter Analytics
      Terms & ConditionsAccessibility statement

      Loading footer...