Targeting your A/B Test

Targeting tests to specific Users

The segmentation options for an A/B test are identical to those used for a messaging campaign.  Reference the targeting user guide for full details.

Keeping your test "sticky"

You may also choose to make an A/B test 'sticky.' This option appears adjacent to the targets you have selected and is a button with a magnet on it. If this magnet button is checked, like so:

it indicates that a user should remain in the test after being assigned, even if they have fallen outside of the specified target group.

For example, consider a test that is targeting users in the US. A user launches the app in the US and is placed into the test. Then, they fly to Europe and open the app again. If the magnet is selected, the user would stay in the test. If the magnet is unselected, they will then be removed from the test.

The magnet defaults to 'on' as most tests require users to remain in the group they are assigned to. You might want to turn it off for use cases that only happen once such user onboarding, as you would not want the same user to see the onboarding flow more than once.


Creating an A/B test directly from a message or interface:

Note that if you click to add a message to a new A/B test directly from the message setup page, the targets defined on the message will be copied over to the test as well. If the message campaign and the A/B test have exactly the same targets, then ONLY users within the A/B test will be served that message. If the targets do not match identically, then it’s important to keep in mind that users outside of the test could also receive the message, if they meet only the target criteria for the message, but not the test.


Was this article helpful?
Have more questions? Submit a request