Why Convert Experiences Data is Different from Google Analytics?

Understand GA vs Convert Data

Convert Experiences and Google Analytics (GA) have different tracking methods and technology. This is the reason why you see the difference between the GA and Convert Experiences data of your website. To make it easy to find out what the differences are and helping you explain them we have this document.

1. You’re Comparing “Visit Starts” in GA with Visitors Data in Convert Experiences

The “visit starts” data in GA is actually the total number of visits on the website. So if a person visits your website and closes it (GA loses the previous session here), only to visit it again after some time, GA will start a new session for the same visitor. As a result, the “visit starts” option that shows you the number of visits on a website will count this session again in its data and reflect two visits.

On the other hand, the visitors count shown in your Convert Experiences tool is the unique visitor count that became a part of the test. The default cookie life of a Convert Experiences cookie is one year, so this visitor is counted only once by our tool as long as the Convert Experiences cookie lasts in his browser.

If you want to see a fair data comparison, you should visit the “Overview” page in your GA to check the data listed under unique visitors. And this data should be compared with your visitors data in Convert Experiences. Still, the exact data match wouldn’t be possible here as well, as GA and Convert Experiences have different tracking methods. Usually, there’s a discrepancy of 5-10% in this data.

2. GA Reports Take 24-48 Hours to Update, Convert Experiences Reports Are Real Time

So if you have paused any test, make sure that you at least wait for up to 48 hours before you compare the data.

3. You’re Comparing the Date Selector Data in GA with the Date Selector Data in Convert Experiences

When you use date selector in GA, it shows you unique visitors only in that particular date range (even when they may have visited the site before the selected date). But date selector in Convert Experiences doesn’t segregate unique visitors for the selected date range on GMT.

For example, if a visitor visits a page (under test in Convert Experiences and is also being tracked in GA) on 10th May, he will be tracked as a unique visitor for 10th May in Convert Experiments and GA. If now the same visitor comes to the website on 11th May, for Convert Experiments he will not be a unique visitor and won’t be counted in our records for 11th May. On the other hand, for GA, if the date selected is 11th May, he will be again shown as a unique visitor.

So if the date selected in Convert Experiences and GA is 10th May, you will see one unique visitor in both of them, but if the date selected is 11th May in Convert Experiences and GA, you will see zero unique visitors in Convert Experiences whereas GA will show you one unique visitor for the same date. Now if you select a date range of 10th -11th May, you will see one unique visitor in both Convert Experiences and GA.

4. You’re Comparing Results in Different Time Zones

Apart from being conscious about selecting the same date range, different time zones can also reflect a huge difference in the data that you see in your GA and Convert Experiences account. While your GA might be having the time zone that was chosen by you earlier, in Convert Experiences we have GMT as the time zone used for storing report data.

5. You Have Multiple Tests Active at the Same Time

When you have multiple tests active on the same webpage simultaneously, make sure that you choose different slots or dimensions in GA for each of your tests. If you are pushing the data for multiple tests in the same slot, your Convert Experiences and GA data will not match.

Have more questions? Submit a request

Comments