To help you save time in reading and understanding your test results, you can sign up for the Smart Report You aren't seeing the same numbers when you compare data for one of your test reports and the data in GA? The points below will certainly help you understand why!
1) Comparison between the 2 different metrics
Often, users look at sessions in GA which in AB Tasty we display visitors.
It is vital to compare the same thing in the two tools, and therefore to select the “user” metric in GA.
2) Filters in GA that are not applied to AB Tasty data
There are usually filters excluding internal IP addresses or known robots in GA. When these filters are not applied to AB Tasty data, the data is of course different.
To see the filters applied in GA, go to Admin > filter.
Filters can be applied at the view level and at the account level.
You can also exclude robots known to Google by ticking a box; this can also explain differences in data (Admin > View > View settings):
3) Error in implementing one of the two tags
It is possible that one of the two tags may be poorly implemented, and that the information is sent twice (or not sent).
To check, go to a page on which the test is active and open your Network (F12) and reload the test page. By filtering on the hit name, you will see if the tool sends a single hit of each type (page view or event):
4) One of the two tags is much slower than the other.
In certain cases, it is possible that a tag is much slower to load than the other (depending on its position on the page, on its size, etc.)
This way, if a user skips over the page quickly, one of the two tags may load but not the other.
In order to verify a tag’s loading time, use the Network:
5) Single vision in AB Tasty vs. multiple vision in GA
In AB Tasty, clicks and pages are shown in unique views. Therefore, you must compare them with “unique events” and “unique page views” in Google Analytics.