Mobile A/B test stuck on B experience | Community
Skip to main content
T
tmrog
August 4, 2020
Solved

Mobile A/B test stuck on B experience

  • August 4, 2020
  • 2 replies
  • 1271 views

I have created my first Mobile A/B test for an iOS app.  I have two experiences configured 50/50 but I always get the data for the B experience.  I have tried running on multiple simulators to see if I ever get the A experience, but I do not. 

 

1. How do I test this?

2. What is used to uniquely identify the device?

3. Should an app restart reset which experience I should see or multiple calls to the Target SDK?

 

Ted

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 raghavc

You can use the Preview link available for each test.

 

Alternatively, you can craete a segment for query parameter like test=a and test=b and create segment for these and choose these segments for the experiences . You can then pass this query parameter to your url and test in any device

2 replies

raghavc
raghavcAccepted solution
Level 4
August 5, 2020

You can use the Preview link available for each test.

 

Alternatively, you can craete a segment for query parameter like test=a and test=b and create segment for these and choose these segments for the experiences . You can then pass this query parameter to your url and test in any device

    T
    tmrogAuthor
    August 24, 2020

    With enough testing I was able to see different experiences returned.

    Terms & ConditionsAccessibility statement

    Loading footer...