Title: How does randomisation work?
Last modified: August 30, 2016

---

# How does randomisation work?

 *  [kiaseven](https://wordpress.org/support/users/kiaseven/)
 * (@kiaseven)
 * [10 years, 8 months ago](https://wordpress.org/support/topic/how-does-randomisation-work/)
 * Hi Scott,
 * Are you able to share how the randomization between the two groups works? The
   reason I ask is because I’ve added a test to this page: [http://www.atlasandboots.com/privacy/](http://www.atlasandboots.com/privacy/)(
   scroll down to the bottom of the sidebar where it says ‘Split Test’). I keep 
   getting the ‘Japanese’ version despite trying it on several different browsers
   including Tor and on mobile. I have checked [http://www.atlasandboots.com/privacy?group_override=1](http://www.atlasandboots.com/privacy?group_override=1)
   and do get the China version but this doesn’t seem to be being served up naturally.
 * Thanks,
 * Kia
 * [https://wordpress.org/plugins/ab-see/](https://wordpress.org/plugins/ab-see/)

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Author [Scott Grant](https://wordpress.org/support/users/sgrant/)
 * (@sgrant)
 * [10 years, 8 months ago](https://wordpress.org/support/topic/how-does-randomisation-work/#post-6576583)
 * For sure! The code is completely open-source, so you’re welcome to have a peek
   at the code to double check.
 * [https://github.com/scotchfield/ab-see/blob/master/ab-see.php](https://github.com/scotchfield/ab-see/blob/master/ab-see.php)
 * Users are put into groups based on two things: their logged-in state (user id)
   or their IP address. If the user is logged in, A/B See will use their user id
   and the test id (so they’re not always in the same group) to put them in one 
   of two buckets. If the user isn’t logged in, A/B See will use the IP address 
   and the test id instead.
 * What this means is that regardless of browser, a logged-out user on a particular
   IP address will always be in the same bucket, and a logged-in user will always
   be in the same bucket.
 * I’d recommend watching it for a few days and seeing if it’s putting people in
   the right bucket. If not, please let me know! (I’ll leave this topic unresolved
   to be safe).
 * And a quick anecdote: I tried to be cute when demoing A/B testing for my team,
   and all five of us were put in the same group. Unlikely, but possible! 🙂 (The
   sixth person finally got added to the second group. Still made me nervous!)
 * Keep me posted! Thanks!
 *  Thread Starter [kiaseven](https://wordpress.org/support/users/kiaseven/)
 * (@kiaseven)
 * [10 years, 8 months ago](https://wordpress.org/support/topic/how-does-randomisation-work/#post-6576623)
 * Thanks, Scott. I’ll keep an eye on it and let you know either way.
 * I tried with a few proxies and managed to get the China version showing up once
   or twice so I suspect it **is** working; I just happened to get Japan quite a
   few more times.
 * Great plugin. I will definitely drop you a review once everything is in order.
 *  Plugin Author [Scott Grant](https://wordpress.org/support/users/sgrant/)
 * (@sgrant)
 * [10 years, 8 months ago](https://wordpress.org/support/topic/how-does-randomisation-work/#post-6576630)
 * Awesome, and thanks! Feel free to come by and mark this as resolved when you’re
   satisfied that it’s working, and if it seems like something’s wrong, just let
   me know.
 * Have a great day!
 *  Thread Starter [kiaseven](https://wordpress.org/support/users/kiaseven/)
 * (@kiaseven)
 * [10 years, 8 months ago](https://wordpress.org/support/topic/how-does-randomisation-work/#post-6576788)
 * Hi Scott,
 * I think the randomisation is working but I’d like to query some stats please.
 * I have set up an A/B test on my sidebar (for the ’10 great travel books’ promo
   on the sidebar [here](http://www.atlasandboots.com/travel-blog/)). In the back-
   end, A/B See gives me the following stats.
 * **Group 1 conversions: 2% (46/2304)
    Group 2 conversions: 1.63% (37/2268)
 * These clicks are unexpectedly high so I checked in Google Analytics and since
   the test went live, there have been 16 clicks on the destination page, not 46
   + 37 as suggested by the A/B See stats.
 * Do you have any idea why there is a discrepancy? Any help would be much appreciated.
 * Thank you,
 * Kia
 *  Plugin Author [Scott Grant](https://wordpress.org/support/users/sgrant/)
 * (@sgrant)
 * [10 years, 7 months ago](https://wordpress.org/support/topic/how-does-randomisation-work/#post-6576823)
 * Hi Kia,
    Sorry, I’m not sure why you’re seeing different numbers. I’ll try to
   take a closer look, but I haven’t run across this in practice. It’s possible 
   that the site numbers would be higher because browsers are blocking analytics
   or requests are timing out. Those numbers seem a lot higher though, so this probably
   isn’t the reason. If you find more information, can you let me know? I’ll keep
   poking around on this end. Thanks!

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘How does randomisation work?’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/ab-see.svg)
 * [A/B See](https://wordpress.org/plugins/ab-see/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/ab-see/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/ab-see/)
 * [Active Topics](https://wordpress.org/support/plugin/ab-see/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/ab-see/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/ab-see/reviews/)

## Tags

 * [A/B test](https://wordpress.org/support/topic-tag/ab-test/)
 * [A/B Testing](https://wordpress.org/support/topic-tag/ab-testing/)
 * [split test](https://wordpress.org/support/topic-tag/split-test/)
 * [Split Testing](https://wordpress.org/support/topic-tag/split-testing/)
 * [testing](https://wordpress.org/support/topic-tag/testing/)

 * 5 replies
 * 2 participants
 * Last reply from: [Scott Grant](https://wordpress.org/support/users/sgrant/)
 * Last activity: [10 years, 7 months ago](https://wordpress.org/support/topic/how-does-randomisation-work/#post-6576823)
 * Status: not resolved