Each project is assigned a unique Convertize Pixel. It is a small line of code that you add to the header of your website, and it usually looks something like this:
The Pixel is what allows you to make changes to your website in the Convertize SmartEditor™. It is also how you track conversions for different scenarios during an A/B test. Without having the Pixel in place, none of the changes you make to your website will be visible.
Our developers are constantly working on ways to optimize the Convertize pixel. As a result, it is exceptionally fast and remarkably versatile. We encourage our users to test their page loading speed after installing Convertize and, if possible, to share their results.
Since Convertize is both an A/B testing tool and a website optimization platform, the same Pixel can be used to edit your content, run A/B tests and add new features to your webpages. Once the Pixel is installed, you can create Smart Notifications and add Geolocation or Dynamic Text to your website.
Our developers found 7 key areas to optimize the Convertize pixel, reducing its size and making it more powerful. That means that you can run substantial A/B tests without affecting your page loading speed or causing page flicker.
What is Page Flicker?
A/B Testing Page Flicker occurs when a large and inefficient Pixel is too slow to modify the webpage before the original content appears. As a result, a visitor sees the original page for a split-second, before the new version appears. The effect is also known as FOOC (Flash of Original Content).
You can read all about the optimizations that make Convertize lighter and faster in our article on A/B testing site speed.
If you are running A/B tests on multiple sites, you have to create a new Project for each website. Remember, each Pixel is unique to a Project, so be sure to install the correct Pixel on the correct website.
If you have one site with multiple domains, you can often use the same Pixel. For example, a website with separate domains for French and English-language content (that, otherwise, look and function the same) could use a single Pixel to test both domains.
It is important that you define the pages included in your experiments carefully, using URL targeting to make sure the right changes are made to the right pages.
For example, if you are using the same Pixel on your French www.example.fr and English www.example.com websites, but you only want to change the catalog page on your English-language domain, you should target: www.example.com/catalog
Simply targeting all URL’s that contain ‘/catalog’ would apply your changes on every webpage including that string on each domain that uses the same Pixel.
Your project is assigned a unique Pixel as soon as you create it, and you find it at Step 1 (“Create”), before you have even started editing a page. Bear in mind that the changes you make in the SmartEditor™ won’t be visible until the Pixel is in place.
If need help, read this article on how to install the Pixel.
You can access your Pixel at any time, by visiting your project page. Simply click on “Settings” in the top right corner.
Once you have opened your project settings, the Pixel will be displayed in the tab “Tracking Pixel”.
There are three ways to add the Convertize Pixel to your website: