> 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/sitewide-analytics/audience-dive.md).

# Audience Dive

#### Page **Overview**

The Audience Dive page brings audience-level visibility to Sitewide Analytics. It helps merchants identify which visitor segments drive the most profit across devices, countries, and channels.

* Audience Comparison Snapshot: Shows key metrics for each audience: Visitors, Conversion Rate, Profit per Visitor (or Orders and Profit when toggled to Absolute)
* Audience Details Over Time: Time-series visuals showing Visitors, Orders, Net Revenue, or Gross Profit by audience

#### Audience Types

Audience Dive includes six pre-built views:

1. **Device:** Mobile vs Desktop.
2. **New vs Returning:** Based on visitor’s first session since Intelligems tracking began.
3. **Channel:** Paid Social, Organic Search, Direct, Email, etc.
4. **Source Site:** Referring URLs or domains (e.g., Meta, Google, Pinterest).
5. **Country:** Top 10 traffic sources by country.
6. **Landing Page:** Top 10 entry URLs, recalculated dynamically based on filters.

#### Metric Details:

* **% Change:** calculates change in metric for an audience between current period and prior period
* **Total Change Contribution:** calculates the contribution of the change in the given audience's impact on the total metric
* **Impact from Visitor Mix Shift**, a unique Intelligems calculation showing the effect of traffic mix changes on conversion and profit, even if audience performance itself is stable.


---

# 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/sitewide-analytics/audience-dive.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.