Welcome to the wonderful world of conversion optimization powered by Omniconvert.
In order to start your journey and achieve the highest potential of your website, you must take the smallest step first: installing the tracking code that will apply all the changes you make in the platform, onto your website.
These instructions are for non-Shopify websites. If your website is on Shopify, please follow this article.
Installing the code directly into your website
To install the tracking code, you need to LOG IN the application and click on the Install button in the header area:
Or lower, on the Click here link:
Another way to reach the tracking code page is by clicking on the website’s name > Tracking code settings.
After doing so, you will be prompted with a new window from where you must simply copy the custom code generated especially for your website.
After you copy the code, you must go on the server where your website is hosted, search for the file that contains the header part of your website, and paste the code immediately after the <head> tag or at least before any other javascript (js) files.
The code must be installed and available in the header of all the pages of the website where you want to run an experiment, include in segmentation or track goals on.
If you want to install the tracking code using Google Tag Manager check out this article.
Asynchronous Code
Because our platform is Javascript based, for seamless user experience when conducting A/B tests (without any flickering effect), we recommend the synchronous implementation (the default one). But if you plan to use other features than A/B testing, you can load the asynchronous code.
If you are using a Tag Manager system, always use the asynchronous version.
For example, if you use Google Tag Manager (GTM), and try to implement the Omniconvert tracking code via a Custom Tag, you must know that these tags will be fired asynchronously. As a consequence, there will be a flickering effect when running A/B test experiments.
If you use GTM and want to conduct A/B tests and offer a very good user experience, try implementing the Omniconvert tracking code independently, directly into your website, not placing it through a Tag Manager System.
There are multiple undesirable consequences that may appear when the code is integrated asynchronously. You can read more about this in this article.
Asynchronous & Anti-Flicker Code
If you are planning to use the Asynchronous code due specific reasons, but want to avoid displaying a flicker effect to your visitors, there is an option to address this.
The Anti-flicker feature for the async code will make it so the page is not shown until the changes from your experiments load completely.
The visitors will only see a white page until the tracking code finishes loading, that’s when the real page will be displayed, containing the experiment changes.
You will also have 2 settings here:
Minified code
By default, this checkmark is selected, that means the code you will see will be in minified version.
By deselecting this checkmark, you will see the code un-minified, for those of you who would like to change or adapt the code as per your needs.
Anti-flicker timeout
The anti-flicker mechanism will hide the contents of the page until the Explore code is loaded and experiments are applied. This timeout represents the number of miliseconds to wait for this to happen.
The default is 1 second (1000 ms).
Please be aware that setting a timeout that is too low might cause flicker, this number might need to be adapted according to your website.
