> For the complete documentation index, see [llms.txt](https://nimora.gitbook.io/nimora-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nimora.gitbook.io/nimora-docs/nimora-ai-media-and-seo-docs/features/analytics.md).

# Analytics

## Analytics

Nimora Tracker helps teams see what visitors actually do on the storefront.

### Core signals

Analytics workflows can include:

* Live visitors
* Session replays
* Heatmaps
* Click and scroll depth signals
* Funnel views
* Campaign and UTM tracking
* Bot-filtered activity

### Session replays

Replays help surface friction such as rage clicks, variant confusion, mobile checkout issues, cart exits, and weak CTAs.

### Heatmaps

Heatmaps show where shoppers click, move, and scroll. They are useful for product pages, landing pages, collection pages, carts, and checkout-adjacent flows.

### Live visitors

Live visitor tracking is useful during launches, promotions, and other high-traffic windows.

### Funnels and campaigns

A good campaign workflow looks like this:

1. Use consistent UTM parameters.
2. Track sessions and landing paths.
3. Review behavior for each campaign.
4. Compare buyer quality by source.
5. Improve the page or creative.
6. Re-measure after the next cycle.

### Signal quality

Bot traffic can distort analysis. Nimora references bot and country blocking in higher-tier plans to keep signals more reliable.


---

# 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:

```
GET https://nimora.gitbook.io/nimora-docs/nimora-ai-media-and-seo-docs/features/analytics.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.