# Stay Heatmap

Visualizes how long users stay on each block in the page. **Long stay = high user interest** — useful for identifying which areas attract attention.

***

## What this heatmap can tell you

* Which blocks attract user attention
* Which blocks get skipped
* Whether important content gets the attention it deserves

> **Prerequisite**: Stay Heatmap requires [block setup](/en/insight/smart-heatmap/block-element-settings.md#block-settings) on the target page.

***

## Two display modes

Switch display modes using the dropdown menu in the upper left of the heatmap. **The default is Attention.** We recommend starting with Attention to grasp overall focus distribution intuitively, then switching to Block Stay to dig into block-level data.

| Mode                    | Characteristics                                                     | When to use                                               |
| ----------------------- | ------------------------------------------------------------------- | --------------------------------------------------------- |
| **Attention** (default) | Pixel-level attention distribution as a thermograph (color shading) | When you want to know exactly where the gaze concentrates |
| **Block Stay**          | Average stay time (in seconds) per block                            | When you want a rough sense of which sections are popular |

***

## Attention mode (color display)

Relatively evaluates user stay time and visualizes it via color shading.

| Color       | Meaning                          |
| ----------- | -------------------------------- |
| Red         | Areas where users stayed longest |
| Blue        | Areas with low user attention    |
| Transparent | Stay time near zero              |

### Three rules of attention coloring

1. **The middle of the screen turns reddest** — gaze concentrates here
2. **Where users stop scrolling, overlap turns red** — many users stopping in the same place deepens the color
3. **Long-stopped positions turn red** — the longer a position is viewed, the redder it becomes

***

## Block Stay mode (numerical display)

Displays the average stay time (in **seconds**) per block (section).

* Each block shows its stay time prominently
* The right-side panel lists all blocks with their impression rates

### Block detail view

Click any block on the heatmap to see a popup with detailed data:

* Display rate
* Average stay time
* Exit count
* Conversion count

### Right-side data table

The right-side panel shows the full list of blocks on the page.

| Metric            | Description                                                             |
| ----------------- | ----------------------------------------------------------------------- |
| Block name        | Click to scroll the heatmap to the corresponding location               |
| Display rate      | % of PVs where this block was displayed                                 |
| Average stay time | Average stay time of users who saw this block. Longer = higher interest |

> **About sort order**: The block list is sorted by **page position (block top edge from top)** by default. Click any column header to re-sort by that metric.

***

## Metrics used

| Metric                      | Definition                                                                                               | Formula                                    |
| --------------------------- | -------------------------------------------------------------------------------------------------------- | ------------------------------------------ |
| **Block Average Stay Time** | Average time the block was visible in the viewport (seconds). Indicates how long users viewed the block. | Sum of in-viewport time ÷ impression count |
| **Impression Rate**         | % of PVs that scrolled to display this block                                                             | PVs reaching block top ÷ total PVs         |

> For detailed formulas, see [Metrics Reference](/en/insight/smart-heatmap/metric-reference.md).

***

## Analysis tips

### Long stay ≠ always positive

There are 2 possible reasons for long stay:

* **Positive**: Users are interested and reading carefully
* **Negative**: Content is unclear and takes time to understand

The key is to **combine with Exit Heatmap** to disambiguate.

| Pattern        | Stay time | Exit rate | Interpretation                                 |
| -------------- | --------- | --------- | ---------------------------------------------- |
| High interest  | Long      | Low       | Users are satisfied and move to the next block |
| Hesitation     | Long      | High      | Users read but it didn't meet expectations     |
| Skim           | Short     | Low       | Not interested, moving on with anticipation    |
| Immediate exit | Short     | High      | Lost interest at first sight, exited           |

### Checkpoints

* Are key pieces of content (value props, CTAs) getting enough attention?
* Are attended pieces buried below the fold?
* If the page is overall pale-colored, content might lack appeal
* Areas with sharp color jumps (red→green→red) indicate fluctuating reading intent

***

## Related pages

* [Exit Heatmap](/en/insight/smart-heatmap/exit-heatmap.md) — Analyze with exit rate together
* [Smart Summary](/en/insight/smart-heatmap/smart-summary.md) — AI auto-analysis
* [Metrics Reference](/en/insight/smart-heatmap/metric-reference.md)


---

# 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://helps.ptengine.com/en/insight/smart-heatmap/stay-heatmap.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.