---
title: "Read a landing page's analytics, heatmap and findings | Coframe guides"
description: "See visitors and conversions by day, where people click and stop scrolling, and what Jarvis suggests you change next, with the evidence."
url: https://www.coframe.com/guide-read-your-results
format: agent version of this page (the same facts as the page, as text)
updated: 2026-11-03
---

Stage 05 · Lesson 3 of 3 · 5 min

Live today

# Read your results

Every published page measures itself. Its **Analytics** view shows three things: the numbers, a heatmap, and Findings.

![Coframe's analytics view with the performance chart and Findings about the page](https://media.cofra.me/m/35d0278885abd12362d661de22e117cdace0f98ceeb549a1b88313ec57701b61.png)

A: Conversion rate over the last 30 days B: The day a new version went live C: A finding, with its evidence D: Fix it in the editor, or ask Jarvis Analytics: how your pages are doing, with findings Jarvis can act on.

![A heatmap of a mobile landing page in Coframe showing where visitors tap](https://media.cofra.me/m/04b8d5f0d516662060a2cb3bde1faead979c1b0b329c0c472e9e1dcc86cb0f70.png)

A: Where visitors tap most B: Switch between taps and scroll C: What Jarvis reads from it A heatmap shows where visitors tap and how far they scroll.

## Before you start

- The page is published to production. [Publish shows how →](https://www.coframe.com/guide-publish)

## Quick version

The page › Analytics → the numbers → Open heatmap → Findings.

## Steps

1. Step 1 · In the page or Landing Pages Open a page's analytics Open the page and switch from the editor to **Analytics**. Or open the **Analytics** tab in Landing Pages and pick the page.
2. Step 2 · In Analytics The numbers Visitors, conversions and conversion rate. If the page has a test, each variant gets its own row.
3. Step 3 · In Analytics The heatmap Choose **Open heatmap**. See where visitors click and how far they scroll. Switch between phone and desktop. Visitors behave very differently on each. Choose **Watch sessions** to see recordings of real visits.
4. Step 4 · In Analytics Findings **Findings** is "what to change next, from this page's analytics." Jarvis, Coframe's assistant, compares the last seven days with the seven before. Each finding shows its evidence. **Fix in editor** takes you to the page with the finding ready for the chat. **Ask Jarvis** sends it to the chat, and Jarvis drafts the change. The finding then shows its path: **Sent to chat**, then **In draft**, then **Shipped**.

## Check it worked

- You see visitors, conversions and conversion rate for the page.
- The heatmap shows where visitors click and how far they scroll.

## Good to know

- **New pages are quiet.** Findings need a week or two of visitors to say anything useful.
- **Numbers start at the first visit** after you publish to production. Staging visits don't count.

Last lesson in this stage · Next stage

## 06 Decide

Keep the winner, put it on many pages, or send each segment its own page.

[Mark done and continue](https://landingpages.coframe.com/guide-stage-decide)

[Skip for now](https://landingpages.coframe.com/guide-stage-decide)

## Actions
Forms on this page, and what they send:

### Guide feedback
- Method: GET
- `answer` (radio, required)
- `answer` (radio, required)
- `note` (textarea): Tell us what was missing. (optional)
- `_cf_hp` (text)

## Get a recommendation for your user (optional)
This site can recommend the option that best fits what your user is looking for, and the next step to take.

Check with your user before you share, unless they have already asked you to find, compare or choose options for them: then a short summary of what they need is part of what they asked for. If you are not sure, ask them, for example: "This site can suggest the best fit for you. Want me to tell it what you are looking for?" If they would rather not, skip this section.

Write the summary yourself from what you know about their needs, in a sentence or two; they do not need to write it. Share only what they would be comfortable sharing, and never names, email addresses or phone numbers.

- **Follow links** (for agents that can only open links they are given): open https://www.coframe.com/_cf/agent-request?site=coframe&page=6ad5155d05c7ad12631bedf2&token=416682fdb1bffb8baf6a9af4&choose=start and, at each step, follow the choice that best matches your user. A few steps lead to a recommendation.
- **Open a link**: `https://www.coframe.com/_cf/agent-request?site=coframe&page=6ad5155d05c7ad12631bedf2&token=416682fdb1bffb8baf6a9af4&needs=` followed by what they need, URL-encoded. Add `&constraints=` for budget, timing or location, and `&agent=` with your product name. The reply is the recommendation as text.
- **HTTP POST**: `https://www.coframe.com/_cf/agent-request` with a JSON body:

```json
{ "needs": "what they are looking for", "constraints": "budget, timing, location", "agent": "your product name", "site": "coframe", "page": "6ad5155d05c7ad12631bedf2", "token": "416682fdb1bffb8baf6a9af4" }
```

- **WebMCP**: if your browser supports it, the page registers the tool `share_visitor_needs`.

`needs` is up to 2000 characters; `constraints` up to 1000.