Tracking setup
Table of contents
In short
Increase the security of your login by activating multi-factor authentication to protect your account even better against unauthorized access.
Difference Varify Snippet Integration and Tracking Setup
Snippet integration
With the Snippet integration is the integration of the Varify snippet into the website.
The snippet integration is mandatory for:
- Loading the editor
- Creating experiments
- Playing out the experiments
- DataLayer Push of the Varify events
Tracking setup
The tracking setup is a stand-alone setup, independent of the Varify snippet.
The tracking setup ensures that the Varify events are sent from the DataLayer to your analytics solution (e.g. Google Analytics, Matomo, etc.).
Step 1: Define tracking setup
Analytics Connection
The A
The AB-Testing Setup
Advanced Setup
Go to your settings via the dashboard under "Your Settings". Under Security you can now use an authenticator app such as Microsoft Authenticator, Google Authenticator (available for free in the Google Play Store and Apple Store) or 1Password to generate an authentication code. Simply scan the QR code with your app.
User Group Identification
With the setting User Group Identification you determine how the assignment of experiment participants is saved in the browser. This is crucial if you want to determine whether users are assigned to a new experiment variant for each session or whether they should be recognized across sessions in order to always see the same variant of the experiment.
- Session Storage,: New assignment in each session
- Local Storage: Cross-session assignment (recommended)
Data Save Mode (beta)
Without the Data Saving Mode the Varify event is triggered every time the experiment is played (i.e. when Page and Audience Targeting true return). If the Data Saving Mode is activated, the Varify event is only triggered once per visitor and session. The advantage: fewer requests are generated, which can lead to cost savings when using BigQuery, for example.
Wait for GA4 consent update (beta)
If the Varify event is triggered in the DataLayer before the Consent update, it is possible that no or only little A/B test data is recorded in GA4.
In this case, it can be helpful to select the Wait for GA4 Consent Update to be activated. If this mode is activated, the Varify event is held back until the consent update has been initialized in the DataLayer.
This ensures that experiment data is only transmitted to GA4 if consent has been given.
The playout of the experiment remains unaffected by this, as it is independent of the setting. Wait for GA4 Consent Update takes place.
After scanning, the app generates a code. Enter this and confirm with "Verify & Enable".
Ready!
After setup, you will be asked for the authentication code the next time you log in.