Ability to split traffic evenly no matter how many experiences you have

[#1]

Description - The feature request is to be able to split traffic evenly no matter how many experiences/variations you have. For example if you have 4 Target splits traffic 25/25/25/25. But if you have 6 Target doesn’t allow for decimal places and is effectively giving the control (or Experience A) 20% traffic and then splitting the rest evenly 16%. But really it should be 16.67% for all six (with technically one at 16.65%), but a difference of 0.02% is negligible unless we're talking about hundreds of millions of visitors, whereas a difference of 4% is much larger (20% control traffic - 16% other variations). So a rounding to 2 decimal points with a tweak to round to 100 for one experience is acceptable and done by other testing tools.

Why is this feature important to you - Because if we want to split traffic evenly, which is standard practice, we should be able to, regardless of the amount of experiences/variations.

How would you like the feature to work - Detailed above.

Current Behaviour - Detailed above.

[#2]

Allowing of two decimal places would be ideal.

[#3]

Thank you so much for your idea! You are correct that Target does not currently allow traffic splits that are not whole percentages. While Target continues to work as is, if it is important for your business that traffic allocation is exact between experiences, I would recommend choosing a number experiences that allows 100% to be split evenly (i.e 2 can be split 50/50 or 5 can be split 20/20/20/20/20).  

We appreciate your feedback and look forward to hearing more of your ideas for Adobe Target!

[#4]

Absolutely but what if you have a usecase where the number of variations is not even? Why was the idea declined? Thanks!

[#5]

@schristensenadobe, So in this case you are saying to use only 2 or 4 or 5 experiences, So that we can split evenly. In most cases, we won't go more than 4. But especially if we have 3 experiences and want to split evenly, adding the decimals would be really helpful. Hope you consider this. Thank you!

[#6]

@schristensenadobe The point of this idea here is to precisely solve for the uneven situations. Where the split % doesn't require a decimal point is already taken care of today in Target, so no issues there. We would want to extend that to situations where you DO need to split traffic to the decimal point level, as per my example. Thanks again!

[#7]

No reply on this @kevincobourn. Thanks.