> For the complete documentation index, see [llms.txt](https://docs.navless.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navless.ai/analytics/view-analytics-for-a-guide.md).
# View Analytics for a Guide
### What this is for
Every Guide you publish gets its own analytics dashboard. If you want to know whether a Guide is actually working — how engaged visitors are, what they're asking, which content they're opening, and where they're coming from — this is the screen to open. It's one page that pulls together engagement, content, traffic, and first-party intent data.
### Before you start
* You need at least one published Guide that has received visitor traffic. A brand-new Guide with no sessions yet will show an empty dashboard.
### Step-by-step
* Open the Guide you want to analyze.
* Click **Analytics** on the Guide.
* You can also go directly to the **Guide Analytics** menu on the sidebar
* You'll land on the per-Guide dashboard.
* Use the **date filter** to set the time range. Options are Last 7 days, Last 30 days (default), Last 90 days, This month, Last month, and All time.
* Apply traffic-source filters as needed: **Referrer**, **UTM Source**, **UTM Medium**, and **UTM Campaign**. Each opens a multi-select popover with the values from your selected date range.
* Read the **hero stats** at the top: Averageg engaged time (with median), Total sessions, and Emails captured.
* Click any of the five **KPI cards** — Sessions, Visitors, Prompts, Skills, or Content — to change what the chart and table below show. The selected card highlights, and both the chart and the table swap to match.
* Scroll to the **traffic source panel** at the bottom for a breakdown by Referrer, UTM Source, UTM Medium, and UTM Campaign. This stays visible regardless of the active KPI.
* To see a single visitor's full journey, click a row in the **Visitors** table. You'll go to their visitor profile with every session, prompt, and content open they've had.
* To export the data behind the active KPI, click the **CSV export** button. You'll get a file named `guide-analytics-[metric]-YYYY-MM-DD.csv`.
### Tips & gotchas
📝 **Note:** The Emails captured tile only shows up once at least one email has been captured for this Guide in the selected date range. If you don't see it, that means no captures yet — not a missing feature.
📝 **Note:** Filters combine with "AND" across categories, and with "OR" within a category. Selecting "linkedin" and "twitter" under UTM Source shows visitors from either. Adding "newsletter" under UTM Campaign narrows it to visitors from linkedin-or-twitter *and* newsletter.
⚠️ **Important:** The five KPIs use different table shapes — Sessions shows only the chart with no table, Prompts shows a stream of cards with the actual messages visitors typed, and the others show sortable tables. If you switch metrics and the bottom of the page looks different, that's why.
### Common questions
#### How fresh is the data?
The dashboard computes live from your Guide's session and event data. There's no overnight job, so filter changes and date-range changes reflect current data immediately. Pages cache for around 30 seconds so repeated clicks stay snappy.
#### Can I export the data?
Yes. Click the CSV export button to download the active metric. To export a different metric, switch KPI cards first and export again.
#### What do the Prompts show?
The actual messages visitors typed into the Guide, newest first, with timestamps and visitor IDs. This is the raw text — not summaries — so you can read what visitors asked in their own words.
#### Does this include traffic from embedded Guides?
Yes. The dashboard counts both visits to the hosted Guide URL and visits to Guides embedded on your own pages. To split them, filter by Referrer.
#### Is there a way to compare Guides side by side?
Yes. The per-Guide dashboard is the drill-down view. There's also an account-wide overview that ranks all your Guides together — open it from the main Guides analytics area.
---
# 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://docs.navless.ai/analytics/view-analytics-for-a-guide.md?ask=
```
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.