Use the Split Segmentation extension to randomly assign your visitors into segments. This can be used for A/B testing or sampling.
See the full list of available extensions.
In this article:
The Split Segmentation extension randomly assign your visitors into segments by setting a cookie value based on a distribution. The cookie values can then be used in load rules or other extension conditions to create personalized experiences. You can also pass the segment names to a vendor tag to measure campaign effectiveness or A/B test results.
Each segment is defined by a name and a distribution. The total sum of the groups must equal 100%.
Before you begin, familiarize yourself with how extensions work.
Once the extension is added, the following configuration options are available:
utag_maincookie. The Split Segmentation cookie values not in the
utag_maincookie have an expiry of 2099. Cookie values placed in the
utag_mainshare its expiry. So, for
utag.jsversions 4.27 and later, that expiry is 1 year. For versions before 4.27, the expiry is 2099.
This example creates three groups to segment the users. To differentiate the groups, a variable called
_group is created to contain a value that is unique to each group. Different analytics tags are run depending on the group.
_groupfor the variable name, and "Split segmentation cookie" for the Description.
In this scenario, we want to run a different analytics tag for each group. For Group A we want to run Google Analytics, for Group B we want to run SiteCatalyst, and for Group C we want to run IBM Digital Analytics. To do this, we must create a load rule for each of the three situations.
The first load rule states if either the domain or
page_name value contains "tealium" and the cookie value
_group equals (ignoring case) "Group A", then this load rule applies.
The other two load rules follow almost identical logic, except for the value that
_group contains, which is "Group B" and "Group C", respectively.
To use these load rules, apply them to the appropriate Tags. In this example, we have the Group A load rule apply to Google Analytics, the Group B Load Rule apply to SiteCatalyst, and the Group C load rule apply to IBM Digital Analytics.
When visitors in Group A come to the page, Google Analytics runs. When visitors in Group B come, SiteCatalyst runs. When visitors in Group C come, IBM Digital Analytics runs.