# Comparison Heatmap

A feature for comparing heatmaps under different conditions side by side. Useful for verifying redesign effects, comparing user behavior across segments, and viewing multiple heatmap types simultaneously.

***

## What this feature can tell you

* Differences before and after page redesign / A/B test
* User behavior differences by segment (traffic source, device, region, etc.)
* Multiple perspectives (stay, exit, click, etc.) on the same page

***

## 2 comparison modes

| Mode                               | Description                                                                            |
| ---------------------------------- | -------------------------------------------------------------------------------------- |
| **Compare different conditions**   | Compare the same heatmap type across different periods, segments, or page versions     |
| **Compare different perspectives** | Show multiple heatmap types (stay, exit, click, etc.) for the same page and conditions |

***

## Compare different conditions

This mode compares **the same page on the same device, varying only the conditions**. The core purpose is to see "**how different groups of people behave on the same page**."

It answers questions like: "How does someone from Google Search read this LP differently from someone from an Instagram ad?" or "Did the click rate just below the fold change between the old version and the redesigned version?"

You can place multiple heatmap cards side by side. Click each card to adjust:

* Date range
* Segment conditions (traffic source / visitor type / region / etc.)
* Saved heatmap version (pre / post redesign)
* Experience version (different A/B test variants)

The right-side data table shows the numbers and ratios for each card side by side.

> **⚠️ Device cannot vary between cards.**
>
> This mode is built on a **single page + single device** baseline. The base image (page layout) of the heatmap differs between PC and mobile, so placing them side by side wouldn't allow position-by-position comparison. To compare device-level behavior, use the device toggle in the toolbar to view each device's heatmap separately.

### Use cases

* **Pre vs post redesign**: Use Page Save to retain the previous version, then place it next to the current version to verify improvement
* **By traffic channel**: Compare behavior between Google Search, ads, direct traffic, etc.
* **New vs returning visitors**: Spot interest-point differences between visitor segments
* **A/B test variants**: See how behavior around the CTA differs across experience versions

***

## Compare different perspectives

Set a **shared baseline condition**, then select multiple heatmap types.

Shared conditions to set:

* Page URL
* Analysis period (e.g. 4/1–4/30)
* Device type (PC, mobile, etc.)

Example: Show "Stay Heatmap" and "Conversion Heatmap" simultaneously for "PC users in April."

### Use cases

* Spot blocks where stay is high but CV contribution is low
* Get a holistic view of stay / exit / click for the same data

***

## Entry points

Comparison Heatmap is **accessible from any heatmap type**. Additionally, the Comparison Heatmap screen itself has a new entry point.

See [Migration from Classic — Comparison Heatmap entry points](/en/insight/smart-heatmap/migration-from-classic.md).

***

## Related pages

* [Toolbar](/en/insight/smart-heatmap/toolbar.md)
* [Stay Heatmap](/en/insight/smart-heatmap/stay-heatmap.md)
* [Exit Heatmap](/en/insight/smart-heatmap/exit-heatmap.md)
* [Migration from Classic Heatmap](/en/insight/smart-heatmap/migration-from-classic.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/comparison.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.