Expand my Community achievements bar.

Ask our product team on how to best grow your experimentation and personalization strategies with Target during our AMA on May 6th!

Mark Solution

This conversation has been locked due to inactivity. Please create a new post.

SOLVED

Mobile A/B test stuck on B experience

Avatar

Level 1

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

1 Accepted Solution

Avatar

Correct answer by
Level 5

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

View solution in original post

2 Replies

Avatar

Correct answer by
Level 5

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

Avatar

Level 1

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