> For the complete documentation index, see [llms.txt](https://docs.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intelligems.io/analytics/overview.md).

# Analytics Overview

Intelligems features a sophisticated analytics engine that can measure a wide variety of metrics on your Shopify store with zero setup. Data is available in near real-time — there will generally be a \~30-60s lag between activity on your site and metrics updating in the Intelligems dashboard.

## Types of Analytics

Our analytics engine spans three different offerings:

* [**Experiment Analytics**](/analytics/overview/experiment-analytics.md) - Measures the outcome of a specific test or experiment and see which variations drove the best results.
* **Experience Analytics** - Monitors the performance of a given experience, whether its a content change or offer
* [**Sitewide Analytics**](/analytics/overview/sitewide-analytics.md) **-** Provides a profit-first view of your store's overall performance with deep dives to uncover underlying performance drivers and identify new opportunities

Profit metrics need your COGS loaded first. See [How to Add Profit to Intelligems Analytics](/analytics/overview/how-to-add-profit-to-intelligems-analytics.md). For how orders get tied to test groups in the first place, see [How Orders and Sessions are Attributed](/analytics/overview/how-orders-and-sessions-are-attributed-to-experiments.md) and [Order and Revenue Accounting](/analytics/overview/order-and-revenue-accounting.md). Common questions are answered in the [Analytics FAQs](/analytics/analytics-faqs.md).

## Sources

Intelligems uses data from a variety of sources to arrive at a clear picture of performance, including:

* Shopify client-side web pixels
* Shopify server-to-server webhooks
* Intelligems’ own client-side tracking


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.intelligems.io/analytics/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
