Expand my Community achievements bar.

Adobe Target Question - How to identify which experience the customer qualified for A/B Test?

Avatar

Level 2


Hi everyone!

We have setup A/B test via Adobe Target for Mobile Audiences. The test is live and while troubleshooting, I would like to understand where I could see which experience we are getting qualified for in developer tools or Adobe experience platform debugger? 
Can you please help?

Thanks

 

 

4 Replies

Avatar

Level 4

Hi @Prachi_091 

You could find them under 'Activities', then click the desired activity from the list.

 

For example, you could select A/B Test and Experience Targeting from the Type drop-down list and Live from the Status drop-down list to display only A/B tests and Experience Targeting activities that are in an active state.

 

If you have setup lower environment report suite like dev / qa, you could find the results in those reports.

 

BR, Hari

Thank you for your input @harikrishnadevanabowina.

This should give you a clearer idea of what I'm looking for:

We have set up an A/B test in Adobe Target specifically for mobile audiences, and the test is currently live. During troubleshooting in the browser console. I want to know how to determine which experience a user is qualified for using either the browser's developer tools or the Adobe Experience Platform Debugger.

Previously, I used to verify these details in the "Network Tools" tab under the "delivery" filter, which showed which test was triggered.

 

 

 

Avatar

Community Advisor

Hi @Prachi_091 , You can check by using activity QA URL on Mobile device or test the process on browser stack or any mobile browser emulators using network tab.

 

 

Avatar

Level 5

Hey @Prachi_091 

 

If your website is integrated with Adobe Launch using Web SDK, you can then identify the visitor's qualification for an experience similar to how we check our analytics server calls. This will occur alongside the web server call under decisioning > propositions.

 

Let me know if this helps. 

Thanks!