# \[Troubleshooting] Reasons for differences in data between Google Analytics and AB Tasty

To help you save time in reading and understanding your test results, you can sign up for the Smart Report. The following points will help you understand why you may not always see the same data in test reports and Google Analytics.

## Comparison between different metrics <a href="#h_01ggvyxp7s40p2j4tc8c45ne3z" id="h_01ggvyxp7s40p2j4tc8c45ne3z"></a>

Users often compare data from Google Analytics and AB Tasty, but it’s essential to know that we display some metrics differently from Google Analytics. To create useful comparisons, you should ensure you are displaying comparable metrics from both platforms. The best way to do this is to ensure Google Analytics is displaying the **user** metric.

## Filters in GA that are not applied to AB Tasty data <a href="#h_01ggvyxv364m3g9t1dg1krg732" id="h_01ggvyxv364m3g9t1dg1krg732"></a>

Google Analytics uses filters that automatically discount visitor data from internal IP addresses or known robots. Unless these same filters are applied to AB Tasty’s data, results will not be comparable.

To see the filters applied by Google Analytics, go to **Admin** > **filter**.

{% hint style="success" %}
**Heads up⚡**

Filters can be applied at the view level and the account level.

You can also tick a box to exclude robots known to Google. This can also minimize differences in data. Go to **Admin** > **View** > **View settings**.
{% endhint %}

<figure><img src="/files/0unRy63tF330RSZLwLfo" alt=""><figcaption></figcaption></figure>

## Error in implementing one of the two tags <a href="#h_01ggvyy07vhmkmkvpjj3b4s5k1" id="h_01ggvyy07vhmkmkvpjj3b4s5k1"></a>

One of the two tags may have been poorly implemented, causing information to be sent twice – or not sent at all.

To check this, open a page where the test is active. Next, open **Network** (**F12**) and reload the test page. Filter by hit name to see if the tool sends a single hit of each type (page view and event).

<br>

<figure><img src="/files/a1cFWP1aabNgSj5FoZ1H" alt=""><figcaption></figcaption></figure>

## One of the two tags is much slower than the other. <a href="#h_01ggvyy81tys7bnm7p9gsqmy4x" id="h_01ggvyy81tys7bnm7p9gsqmy4x"></a>

In certain cases, one tag may be much slower to load than the other, due to its position on the page, its size, or other factors. If this happens, and a user skips over the page quickly, one of the two tags may load.

To verify a tag’s loading time, use open **Network** (**F12**) and console the **Time** column:

<figure><img src="/files/e4otIFONNBTffRKGZ0x0" alt=""><figcaption></figcaption></figure>

## Single vision in AB Tasty vs. multiple vision in GA <a href="#h_01ggvyyeezpzhgc0mnejm3ykbk" id="h_01ggvyyeezpzhgc0mnejm3ykbk"></a>

In AB Tasty, clicks and pages are shown as unique views. These should only be compared with “unique events” and “unique page views” in Google Analytics.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.abtasty.com/help-center/troubleshooting/troubleshooting-reasons-for-differences-in-data-between-google-analytics-and-ab-tasty.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.