Adobe Target A/B Test: Same Content Displayed for Experience A and Experience B | Community
Skip to main content
S
Sairam Thatikonda
New Member
August 20, 2026
Question

Adobe Target A/B Test: Same Content Displayed for Experience A and Experience B

  • August 20, 2026
  • 2 replies
  • 30 views

I created an A/B Test activity in Adobe Target and completed the required configurations and integrations. The activity is active and configured with Experience A and Experience B.

However, while testing the activity, both experiences are displaying the same content on the page, even though I modified the content for each experience separately using the Visual Experience Composer (VEC) and saved the changes.

Expected: Experience A and Experience B should display their respective modified content.

Actual: Both experiences display the same content.

Could anyone help me understand what configuration or implementation might be causing this behavior and how I can troubleshoot it?

2 replies

DineshK
DineshK
Level 3
August 20, 2026

Hi ​@Sairam Thatikonda ,
 

Browser cache/cookie. If you're just reloading the same tab, Target remembers which experience you got and keeps showing you that one — that's normal, not a bug. Use incognito or clear cookies between tests.

Not using QA links. If you're hitting the page raw instead of using the activity's per-experience QA/preview links, you're relying on random bucketing and could land on the same one repeatedly. Grab the QA links from the activity — one per experience — and use those instead.

Traffic split. Quick check — make sure it's not set to 100/0 by accident.

SDK check. Are you on at.js or Web SDK (alloy.js)? Tells us where to look next, and Assurance (Griffon) will show you exactly which experience Target is actually serving versus what's rendering on the page.

SSampsa
SSampsa
Level 4
August 21, 2026

As Dinesh said, I recommend using the Adobe Experience Platform Debugger if you’re running Web SDK a based Target integration. You’re able to run the Assurance session and see the exact details. If you’re running an older at.js based implementation, you can get the trace debug code and see the required information. Instructions here: How to Troubleshoot with Target Traces | Adobe Target

The debugger is compatible with Chrome and other browsers that support the same extensions, see here: Install Experience Platform Debugger | Adobe Experience Platform

The advantage of these solutions vs. just checking the response from Target is that you also see the audience matching data. If you simply want to figure out what version you are actually seeing, you can look at the response from Target and the data shows you which version you are seeing.

Terms & ConditionsAccessibility statement

Loading footer...