> ## Documentation Index
> Fetch the complete documentation index at: https://beta.docs.replo.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Insights

> See how your store and pages are performing, with dashboards you can slice yourself or ask Replo to build.

Insights turns your store's analytics into dashboards: traffic, engagement, and sales, laid out so you can see what is working. It opens to your headline metrics, comes with report templates to start from, lets you re-slice any report by date and segment, and can build a brand-new report for you when you describe what you want to see in Agent chat.

You can reach Insights from the **+** in the tab bar or the <kbd>Cmd</kbd>+<kbd>K</kbd> menu.

## Your home screen

Insights opens to a single, scannable read on your store, with a date range at the top that drives the whole view:

* **Headline metrics**: revenue, conversion rate, sessions, and average order value, each compared against the previous period.
* **Daily performance**: a revenue trend across the date range you have selected.
* **Your reports**: the reports you have created, grouped by who can see them (team, private, or shared with you), with a toggle between **Cards** and **Table** layouts.

## Report templates

You do not start from a blank page. Until you create your first report, **Your reports** shows a **Create a new report** card next to 2 ready-made templates; click **Use template** to turn one into a report of your own:

* **Overview**: sessions, pageviews, purchases, and revenue, plus a sessions trend, where your sessions come from (by referrer and UTM source), and your top landing pages.
* **Sessions**: every visit as a row, with where it started, how long it lasted, and what it was worth, alongside average duration and bounce rate.

Click any report to open it. If you delete a template-based report and want it back later, ask Replo in chat to rebuild it.

## Reading a dashboard

A dashboard pulls together a few kinds of tiles:

* **Headline metrics** for the period you are viewing, each compared against the previous period so you can see the direction of travel at a glance.
* **Trend charts** for traffic, revenue, and orders, with the current period plotted against the one before it.
* **Breakdowns** that rank your top pages, referrers, and traffic sources.

## Slice it yourself

Every dashboard has a control bar at the top so you can change what you are looking at without asking Replo:

* **Date range** with a comparison period, so "this week vs last week" or a custom window are a click away.
* **Filters** to narrow the data down to a segment.
* **Breakdown** to group the results by a dimension.
* **Reset** to return to the report's defaults.

## Create a custom report

You are not limited to the templates. Click **Create report** to choose a starting point: describe what you want, answer guided questions, or use an existing report as a reference. Insights hands your request to Agent chat with the prompt ready to send. Replo assembles a dashboard and saves it as a new report you can reopen and re-slice like any other. From inside a report, **Ask or edit report** continues in Agent chat with that report's context.

```text theme={null}
Show which landing pages are driving revenue this week, broken down by traffic source.
```

```text theme={null}
Show sessions, revenue, and conversion rate for the last 30 days, broken down by week.
```

```text theme={null}
Which UTM campaigns drove the most purchases last month?
```

Reports you create are saved under **Your reports**, so you can come back to them anytime. Pair Insights with [Tasks](/apps/tasks) to have a report run and summarized on a schedule.

## Where the data comes from

The foundation is your store's own Replo analytics: the page views, add-to-carts, checkouts, and purchases tracked automatically on every site you publish with Replo, with nothing to install. That's the on-page funnel, and it's what the headline metrics and starter reports run on.

Connecting your other tools in [Integrations](/apps/integrations) widens what a report can know, because each one answers a question Replo's own tracking can't:

* **GA4** knows your traffic across your whole domain, not just Replo pages.
* **Triple Whale and Northbeam** know which ad actually gets credit for a purchase.
* **Klaviyo** knows which emails went out and to whom.
* **Microsoft Clarity, PostHog, and Amplitude** know what visitors did on the page before they left.
* **Google Search Console** knows what people searched before they landed.

Some of these can feed report panels directly (Triple Whale metrics, for example); for the rest, ask Replo to pull their data in chat and build the report for you.

The reason to bother: these systems don't talk to each other. Your attribution tool doesn't know what the email campaign said, and your analytics tool doesn't know which page variant the ad pointed at. Replo reads all of them in one place, so it can connect what each one knows into a recommendation none of them could make alone: which campaigns to repeat, where a funnel leaks, which traffic source deserves more spend. [Act on Your Analytics](/analytics) shows this loop end to end, with prompts.

Revenue and conversion figures come from tracked purchases, so give a new site a little time to collect real orders before you lean on those numbers.

## Related

<CardGroup cols={2}>
  <Card title="Integrations" icon="plug" href="/apps/integrations">
    Connect the analytics tools that feed your dashboards.
  </Card>

  <Card title="Tasks" icon="clock" href="/apps/tasks">
    Get a report summarized on a schedule.
  </Card>
</CardGroup>
