Operating experiments and personalizations on the server-side involves particular challenges that are not present when running purely client-side campaigns. This article presents those obstacles and provides solutions and workarounds for them.
Bots and inflated traffic numbers
There are basically two options to remove the bots from your Kameleoon results:
Filter the bots on your side. It is not always easy to recognize a valid HTTP request from an automated one. However, if you're able to identify the bots (maybe you use some monitoring platforms where a specific User-Agent or IP is provided, for instance), just exclude them from the experiments you're running (it mostly means to not call the
triggerExperiment()method on those requests).
Perform most of the tracking calls on the client-side. As explained, there are much less bots on the client-side, so your results will be much closer to your "real" traffic. For this, you need to create a Hybrid server-side experiment, and activate the checkbox "Do not track experiment activations on the server-side". As a result, the
triggerExperiment()method will only perform experiment variation allocation, without sending a tracking call in the background to our data collection servers. The experiment activation should then be tracked on the client-side (using the Back-end / Front-end Bridge), which will eliminate most of the bots.