Visitors change the variants within an experiment
If you notice that a different version of the same experiment is displayed during a page visit - or when you visit the page again - this is usually because no entry has been set in the LocalStorage. The reason for this is usually that the Varify Activation Tracking Script has not been integrated correctly.
Alternatively, the Consent Management Platform (CMP) you are using may also be responsible: Some CMPs empty the browser's session or local storage as soon as consent is granted or they block the local storage from being set.
The Tracking Activation Script was not integrated correctly
Check whether the setting "Start Tracking on Activation Event" is active and whether the "Tracking Activation Tag" is correctly triggered and delivered in your Google Tag Manager. How to set up the "Tracking Activation Tag".
Possible causes & solutions:
- Tracking Activation Script was not triggered
→ Check whether the Tracking Activation Script is configured correctly.
→ It must be in the GTM be triggered in such a way that it immediately after initialization of your analytics tool. - Deactivate setting (not recommended)
→ As a result, the tracking events fire directly with the variant playout.
→ Attention: This can lead to "Not Set" sessions. in the analytics data.
Step-by-Step Tutorial
Start Tracking on Activation Event
Your Consent Management Platform (CMP) blocks or deletes the Varify Local Storage
If this is the case, you only need to create and categorize Varify.io® or app.varify.io as a provider in the CMP tool. Here is an example of Cookiebot:
