A/B Test: How can traffic enter both experiences? | Community
Skip to main content
bkmills
bkmills
Level 2
February 9, 2022
Solved

A/B Test: How can traffic enter both experiences?

  • February 9, 2022
  • 1 reply
  • 1371 views

Hello all,

 

I have an A/B activity where I'm seeing traffic enter both experiences. What initially brought my attention to this was interaction with the chat widget (~10%) in the control variant -- Live Chat Button Opened. See Venn diagram and data below. This is unexpected because the widget is being suppressed in the control. In fact, there is no code that would deliver the widget here.

 

Is this type of traffic crossover common? Is it possible a visitor entered experience B clicked a button, then later enter experience A, but the initial engagement was captured in the subsequent visit?

 

Thanks in advance for your help!

 

-Brion

    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 bkmills

    Hi @ryanr7 - There are multiple Pages with unique URLs where this test is delivered, but no redirect has been added to those pages.

     

    I spoke with customer care yesterday and they shared the following, which seems to explain a possible cause. In our case I think it's either point 1 or point 3.

     

    Why is the same visitor sometimes counted in multiple experiences in Analytics?
    The following list explains reasons why the same visitor could be counted in multiple experiences in Analytics:

    • The Target profile expired but the Analytics cookie is still there. In this situation, Target reevaluates the user but Analytics considers the visitor to be the same person.
    • If the visitor is using the mbox3rdPartyId, when the anonymous visitor is merged with the 3rd-party ID profile, Target could put the visitor into a different experience to match up with the 3rd-party ID. For more information, see Real-Time Profile Syncing for mbox3rdPartyID.
    • Analytics might be tracking different devices as the same visitor in a different way than Target tracks those devices: the 3rd-party ID setup in Target is different than in Analytics.

    https://experienceleague.adobe.com/docs/target/using/integrate/a4t/a4t-faq/a4t-faq-viewing-reports.html?lang=en

     

    1 reply

    R
    Adobe Employee
    ryanr7Adobe Employee
    Adobe Employee
    February 11, 2022

    Hi @bkmills,

    Is this test executed with a redirect? Depending on the setup, redirect offer test can sometimes have cross-over traffic showing up in the reports with A4T reporting.

    bkmills
    bkmillsAuthorAccepted solution
    Level 2
    February 11, 2022

    Hi @ryanr7 - There are multiple Pages with unique URLs where this test is delivered, but no redirect has been added to those pages.

     

    I spoke with customer care yesterday and they shared the following, which seems to explain a possible cause. In our case I think it's either point 1 or point 3.

     

    Why is the same visitor sometimes counted in multiple experiences in Analytics?
    The following list explains reasons why the same visitor could be counted in multiple experiences in Analytics:

    • The Target profile expired but the Analytics cookie is still there. In this situation, Target reevaluates the user but Analytics considers the visitor to be the same person.
    • If the visitor is using the mbox3rdPartyId, when the anonymous visitor is merged with the 3rd-party ID profile, Target could put the visitor into a different experience to match up with the 3rd-party ID. For more information, see Real-Time Profile Syncing for mbox3rdPartyID.
    • Analytics might be tracking different devices as the same visitor in a different way than Target tracks those devices: the 3rd-party ID setup in Target is different than in Analytics.

    https://experienceleague.adobe.com/docs/target/using/integrate/a4t/a4t-faq/a4t-faq-viewing-reports.html?lang=en

     

      Terms & ConditionsAccessibility statement

      Loading footer...