👉 Traffic allocation at visitor level

When creating a test or a personalization campaign, you need to define the percentage of visitors assigned to the variation(s) (in case of a test) or scenario(s) (in case of a personalization) and to the original version of your website.

🚩 Heads up
If you change the traffic allocation while your campaign is live, only the new visitors will be affected by this change. Visitors who have already been affected to a variation (before this change) will keep on seeing the same variation.

This table shows the different categories of users representing your entire website traffic. For each category, information on what the users will see is displayed:

🚦 Type of traffic

🍪Visitor’s cookie campaign information (ABTasty cookie)


👻Untracked visitors

campaignId = xxxxxx

value = -1

Visitors who see the original version of your website but whose actions won’t be taken into account.

🎯Tracked visitors (% of unique visitors of your campaign)

campaignId = xxxxxx

value/variationId = 0 or variationID of the variation

The original version of your website or a new variation/scenario of your website

🏛Traffic allocated to original

campaignId = xxxxxx

value = 0

Visitors within the test sample who see the original version of your website.

🆕Traffic allocated to variations

campaignId = xxxxxx

variationId = variationID of the variation

Visitors within the test sample who see a new version of your website (or one of the new versions if there are several variations/scenarios).

🚩 Heads up
If you want to change the traffic allocation of the test to assign 100% to the variation you think is the highest-performing after analyzing your report, you need to create a personalization campaign from the current test. Otherwise, people who have a cookie from another variation or from the original version will continue to see the original version of your website. 

💡 Use case

For example, let’s say you’ve implemented a ‘risky’ test and want to limit risk-taking. In this case, you can limit the number of visitors tracked and so that 40% of visitors aren’t tracked. That way, you reduce the test sample and limit the visibility of your new version(s). This means that these 40% of untracked visitors will see the original version of your website but won’t receive a cookie in their browser related to the test. Their actions on the website won’t be tracked unless you decide to increase the percentage of tracked visitors.
The percentage of visitors that you track depends on the volumetry of your website. For example, if your website has over 10M unique visitors per month, you can choose to track only 20% of the entire traffic (and limit the test sample to 20%). However, if you have around 200k unique visitors per month and decide to track 20% of the traffic, you won’t reach reliability quickly enough to determine whether or not you can increase the percentage of tracked visitors. For more information, refer to Campaign report.

Need additional information?

Submit your request at product.feedback@abtasty.com

Always happy to help! 


Was this article helpful?