> For the complete documentation index, see [llms.txt](https://help.pagefly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pagefly.io/page-structure-and-elements/analytics/page-analytics/page-insights-in-editor.md).

# Page Insights in Editor

See how your page performs without leaving the PageFly Editor. The Page Insights drawer shows live analytics and section engagement right in your editing workspace.

**Availability:** Paid plans with PageFly Analytics enabled.

***

## How to open

1. Open any page in the **PageFly Editor**
2. Click the **Page Insights** icon in the left sidebar

***

## What you see

### Analytics Overview

A compact summary of your page's key metrics:

* Sessions and visitors
* Bounce rate and engagement rate
* Add-to-cart rate and conversion rate
* Revenue and orders

Data updates automatically based on your most recent analytics.

### Section Engagement

A list of all sections on your page with engagement data:

* **Section name** and position
* **Impressions** — how many visitors viewed each section
* **Click rate** — what percentage of viewers clicked something
* **Engagement indicators** — quick visual cues showing which sections perform well or poorly

This helps you identify underperforming sections while you're actively editing — no need to switch to the full Analytics dashboard.

***

## When to use it

| Situation                       | How Page Insights helps                                               |
| ------------------------------- | --------------------------------------------------------------------- |
| **Redesigning a section**       | Check current engagement before and after changes                     |
| **Deciding what to edit first** | See which sections have the lowest engagement                         |
| **After publishing changes**    | Monitor if your edits improved metrics (check back after 24-48 hours) |
| **Building a new page**         | Compare section patterns from your best-performing pages              |

***

## Requirements

* PageFly Analytics must be **enabled** (see [Enable PageFly Analytics](/page-structure-and-elements/analytics/page-analytics/enable-pagefly-analytics.md))
* The page must be **published** (draft pages have no visitor data)
* You need a **paid plan** (Free plan users see an upgrade prompt)

If analytics isn't enabled yet, the drawer shows an **Enable Analytics** button — click it to activate tracking without leaving the editor.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.pagefly.io/page-structure-and-elements/analytics/page-analytics/page-insights-in-editor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.