A partition set allows your organization to divide end-users who visit a property into one or more distinct partitions (groupings) who can receive different messaging scenarios. By utilizing a partition set, you can A/B test different scenarios on property visitors and/or manage a controlled rollout of your messaging experience. In this article, we will cover how partition sets are divided (bucket start/end) and use cases for partition sets.

• ​Partition setup​

• ​Use Case - A/B testing​

• ​Use Case - Controlled rollouts​​

Partition setup

The message scenario that is shown to your end-user is determined by the Sourcepoint messaging library running on the property the end-user visits. Your organization can determine what percentage of end-users are shown each message.

In the example below two messages have been created with different themes. Your organization should set each partition to a message and a scenario. The PARTITION % is the percentage of end-users who are shown a particular message.

Use Case - A/B testing

Partition sets can be used to A/B test messaging experiences where a percentage of users are shown one message experience and another percentage of users are shown a different experience. This requires that your organization sets as many scenarios as you have partitions.

For example, your organization wishes to test two different first layer message designs and find the design more successful in converting end-users to accept tracking.

Use Case - Controlled Rollouts

Partition sets can also be used to control the percentage of users being exposed to a new messaging experience. For example, if you would only like 25% of your users to experience a messaging scenario, you can create a partition set with a single partition to only show the message to a small group of users.​