> For the complete documentation index, see [llms.txt](https://support.growlytics.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.growlytics.in/best-practices/data-management/understanding-data-discrepancies.md).

# Understanding Data Discrepancies

It's not uncommon that Growlytics sessions and other numbers may differ from other vendors like Google Analytics, Mixpanel, etc. This article will help you understand how Growlytics tracks users and sessions.

### Highlights

1. **Time Zone:** Data ingested by Growlytics are timestamped in UTC but in the report, you see the data specified in the time zone of your account (mentioned while setting up the account).
2. **Web bots & Scrapers:** Growlytics' intelligent source identification mechanism makes sure bots and scrapers are ignored for session tracking. Bots like "Googlebot" or any other data scrapers are ignored. This can be the reason you are seeing the discrepancies in a number of sessions.

### Google Analytics Discrepancies

Though Google Analytics and Growlytics track sessions similarly, the following table outlines factors that cause a discrepancy in your session numbers.

<table><thead><tr><th width="219.33333333333331">Scenario</th><th>Growlytics</th><th>Google Analytics</th></tr></thead><tbody><tr><td>Time hits midnight</td><td>Session continues</td><td>The current session ends at 11:59 PM and the new session starts at 12:00 AM.</td></tr><tr><td>Campaign source changes</td><td>Session continues</td><td>New session begins even if it is within the 30-minute threshold.</td></tr><tr><td>Session Event Limit</td><td>No limit</td><td>After the first 10 events, tracking is limited to 1 event per second.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://support.growlytics.in/best-practices/data-management/understanding-data-discrepancies.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.