# Maker Analytics

***

### What  can you do in Insights

* See **top-level performance trends** (Pageviews, Unique Visitors, Avg. Time on Page, CTR, clicks)
* Review performance across all Stories in an **organization-level dashboard**
* Drill into a specific Story/page to see **page-level metrics**
* Use a **heatmap overlay** to visualize engagement on the page
* Get **element-level metrics** (including **eCTR**) to understand what users engage with
* Understand **scroll depth** (how far users make it down the page)

***

## Organization-level Insights

Use the Dashboard to view overall performance for a selected organization and quickly spot which Stories are driving results.

<figure><img src="/files/2Cld7tlxqdpd0rf2QtjG" alt=""><figcaption></figcaption></figure>

#### Organization switcher

Use the organization dropdown at the top to switch between organizations/workspaces.

#### Date range + Apply

Select a date range, then click **Apply** to refresh all metrics and charts.

#### Top-level metrics

At the top you’ll see trend charts for:

* **Pageviews**
* **Unique Visitors**
* **Avg. Time on Page**
* **CTR**
* **Clicks**

#### Stories table

The table shows the list of Stories/Projects in the selected organization, including metrics like Pageviews, Unique Users, CTR, Clicks, and Avg Duration.

***

## Story/Project-level Insights

Click into any Story/Project to view page-level trends plus a visual overlay of engagement on the page itself.

<figure><img src="/files/7404aijFhqb5JT60zsLG" alt=""><figcaption></figcaption></figure>

#### Page-level metrics&#x20;

At the top you’ll see a snapshot of key page metrics (with trend lines) for the selected date range.

#### Date range

Use the date picker to adjust the reporting window.

#### Device toggle (Desktop / Mobile)

Switch the device view to see device-specific metrics and overlays. When you change device:

* The **top-level metrics update**
* The **heatmap/overlay updates**\
  So you’re always viewing performance for that device.

#### Outbound Click Insights

Depending upon where the user has clicked on the page, this is aggregated data on the URL level.&#x20;

#### Heatmap toggle

Turn on the heatmap to visualize engagement directly on the page.

#### Scroll depth

The scroll indicator shows how far users scroll, based on the **number of unique users** reaching each depth.

#### Section Views

We consider the section view if even one element inside the section is visible, essentially the maximum of all elements within a section.

#### Element-level insights

When the heatmap is on, click/hover an element to open an **Element Insight** panel showing:

* **eCTR**
* **Clicks**&#x20;
* **Element Views**\
  …and supporting context metrics (like page-level totals) for comparison.

***

### Understanding eCTR

**eCTR (Element Click-Through Rate)** helps answer: *“When users actually see this element/section, how often do they click it?”*

In practice:

* **Element Views / Section Views** represent how many times something was *viewed* (often estimated using pageviews and scroll depth).
* **eCTR** is clicks / element or section views.

***

## Best-practice workflow

1. **Pick a date range** and click **Apply**
2. On the Dashboard, identify Stories with unusually high/low **CTR**, **Clicks**, or **Avg. Time on Page**
3. Open a Story and **switch device views** (Desktop vs Mobile)
4. **Enable heatmap** and scan for:
   * High-engagement elements (working well)
   * Low-engagement CTAs (may need repositioning/copy changes)
5. Use **scroll depth** to confirm whether users are reaching key sections (and move important CTAs higher if needed)
6. Compare **eCTR** across key elements to decide what to iterate next

***

## Troubleshooting / FAQ

#### “Why don’t I see data?”

Common causes:

* The Story/page didn’t receive traffic in the selected date range
* The date range is too narrow
* You’re viewing the wrong organization
* You’re viewing the wrong device (desktop vs mobile can differ significantly)

#### “Why don’t the top metrics match the table totals?”

The table may only load a subset of Stories initially. Scroll to load more rows—totals may change as more Stories are loaded.

***

## Glossary

**1) Pageviews**\
Number of times a page is loaded (or reloaded) in a browser.

**2) Clicks**\
Number of times a user clicks an **outbound link** (for example: a button, linked image, or linked text).

**3) CTR (%)**\
Percentage of pageviews that resulted in an outbound click.\
**Formula:** `(Clicks ÷ Pageviews) × 100`

**4) Avg. Time on Page**\
Average time visitors spend on the page.

**5) Scroll Depth**\
A measure of how far users scroll down the page (typically expressed as a %).

**6) Section Views**\
Estimated number of times a section was viewed.\
**Formula:** `Pageviews × Scroll Depth (%)`

**7) Section Clicks**\
Total clicks on all clickable elements within a section.

**8) eCTR (%)**\
Engagement rate for a specific element or section, based on how often it was actually *viewed*.\
**Formula:** `Clicks on element/section ÷ (Pageviews × Scroll Depth (%)) × 100`

**9) Element Clicks**\
Total clicks on a specific element (button, linked text, or linked image).


---

# Agent Instructions: 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.maker.co/features/maker-analytics.md?ask=<question>
```

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.
