> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/maker-pages/publish-and-measure/using-metrics-and-insights.md).

# Using metrics and insights

* LOG IN

## Video Learnings

Follow the steps outlined in the video above to learn how to view Maker's engagement metrics in Stories Manager, the Insights Tab and Overlay Analytics.

### Key Features covered:

Insights panel in Stories Manager

Insights tab

Overlay analytics

After signing-in to your account on Maker, you'll automatically be directed to your Stories Manager, which hosts the insights panel on the right:

See overall account metrics or click on a story to get a summary of its specific performance.

For a deeper dive into our built-in insights, switch to the Insights tab to see every metric collected by Maker, including views, click-through rate, share count and more.

Select engagement or inbound here

Select All Stories, or one of the collections listed below

Choose a date range here

Move through images to see the insights features.

Customize the data shown by any of the following options:

* Date range - use the calendar dropdown to select a custom range or one of our preset ranges
* View - 'Engagement' or 'Inbound'
* Content - The insights tab is set to All Stories by default, but you can select specific collections from the left panel

There are two ways to access overlay analytics in Maker:

* Select a story from your Stories Manager and click the Overlay Analytics button, or
* Go directly to the embed on your site and click 'Show Insights'.

Use the overlay metrics to see the total number of views, average attention, total CTR and click-through breakdowns per device (Desktop, Tablet and Mobile).

To see element specific CTR metrics, simply hover over a CTA or other link to see the metrics breakdown:

Detailed CTR Metrics

Get a detailed table for both total click and Quick View CTR by hovering on these metrics and clicking on the show details prompt. The table provides detailed information on each link clicked along with its CTR further broken down by devices. For Quick View, see additional details on both primary and secondary CTAs.

You can also see where visitors are dropping off with our interactive scroll bar on the left:

For any video or image metrics, simply hover over the blue tile on the page to see the details:

<figure><img src="/files/loCPcwl93z6QYbeRr20Q" alt="Using metrics and insights"><figcaption></figcaption></figure>

<figure><img src="/files/UZzxhnQzNhu7ikD8S2MG" alt="Using metrics and insights"><figcaption></figcaption></figure>

<figure><img src="/files/gs9MRQqhdHgViO8AEqa6" alt="Using metrics and insights"><figcaption></figcaption></figure>

<figure><img src="/files/7UXHYJdP64FRNXnyweRx" alt="Using metrics and insights"><figcaption></figcaption></figure>


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.maker.co/maker-pages/publish-and-measure/using-metrics-and-insights.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.