Understand a proposal’s analytics
Analytics shows who read your proposal, when and for how long, section by section. This chapter helps you read these facts without over-interpreting them.
Guide chapters11 of 15
On this page7 sections
Open Analytics and find a reading
- Open the proposal, then the Analytics stage. From the dashboard, See the analytics takes you straight there.
- Start with the header: the proposal’s heat, its reading streak, then the indicators.
- Look at Access. Click a person or a visit to open their record: sessions, time, shares, sections read, then the detail of each session (First opening or Re-read) and, where relevant, the Quote options selected.
- In Reading by section, click a section to see who read it and for how long.
- Browse the Activation calendar and the Signals. Check the facts before deciding on a next step.
The screen refreshes when you come back to the tab. It explains the observed behavior: it does not send a follow-up and does not close the deal.


Read the indicators
The indicators, readers, sections and calendar relate to the latest published version: after a republication, they start again from zero.
| Measure | Meaning |
|---|---|
| Openings | Number of times the proposal was read. One reader can produce several openings. |
| Readers | Identified people who read it: invitees and the signer. Visits without an invitation are shown next to it; with no identified reader, the tile is called Anonymous visits. |
| Reading time | Time actively spent on the proposal. |
| Open rate, with invitations | Share of invitees who opened it. An invitation opened several times does not represent several invitees. |
| Time per opening, without invitations | Average reading time per opening. This tile replaces the open rate when the proposal has no invitees; a note may specify public link. |
Access is Sorted by engagement: the most engaged readers appear first. Columns: Person, Activity, Sessions, Time, Shares (people this reader invited), Last visit. An invitee is named by their address, with the Invited mention; Cuevr does not reconstruct a name from an address.
Without an invitation, each visit counts separately: a reader who reloads the page or comes back later appears as a new visit. Anonymous visits are grouped on a single row, which you can expand; their heat is read visit by visit, in the detail.
The detail of older readings is not kept indefinitely: after a while, the screen keeps only the total, “Readings before {date}”, above the figures.

Analyze the sections
Reading by section lists each part read under its title; the cover appears under its title, or as Cover if it has none. For each: the time spent, the number of visits and a bar showing its share of the reading time. A section’s window adds the average time per visit and the Readers of this section.
Cuevr measures the time spent on each section, one section at a time. A heavily viewed section is not necessarily an objection: it may also contain useful or complex information.
If the card is empty, wait for a more complete reading.


Read the calendar
Navigate month by month in the Activation calendar, from publication until today. The subtitle states whether the history starts from sharing or from the last month.
A day’s color reflects the readers’ engagement that day: Inactive, Lukewarm, Warm or Red-hot. A day can also show milestones: sent, signed, marked lost and “The client declined”. The prospect’s decline and the outcome declared by the seller remain two separate events.
Hover over a day to see its milestones and the readers active that day, with their time. A return to reading after a break gets a reactivation marker.
Hovering over a dated signal highlights its day in the calendar, if that day belongs to the month displayed.
While activity remains sparse, the calendar is collapsed: Show the activity calendar opens it, and Cuevr remembers your choice.

Read the signals
The Signals card has no seen or unseen state and no Remind me later command. Decisions appear before activity signals. Facts are dated; the reason shown may be shortened, while its full version is kept in the deal.
The panel flags: an acceptance, a decline by the prospect, a deal marked lost, the opening of the acceptance form, a period without reading, the most viewed section, a proposal read again, several readers and the first opening.
Understand heat and reading streaks
Heat shows the level of engagement: Cold, Lukewarm, Warm or Red-hot. It takes into account reading time, reshares, the opening of the signature form and changes to the quote options, and it decreases over time. It is neither a signature probability nor a qualification score.
Each reader has their own heat, in the Activity column. The header badge gives the proposal’s heat; it shows Dormant when nothing is happening any more, and gives way to the signature or loss date once the outcome is known.
A flame appears when the proposal is read several days in a row; a moon shows the number of days without contact since the last reading.

Understand empty states and measurement limits
| Situation | Explanation and action |
|---|---|
| Proposal not published yet | “Nobody has seen your proposal yet”: publish and share with Share. |
| Published, no reader | “Nobody has opened it yet”. Check the link, the recipients and the access mode. |
| Proposal unpublished | The link is no longer accessible to readers; the history remains. A session already under way may still be counted. |
| Loading error | The statistics are unavailable, not lost. They appear as soon as the server responds. |
| Acceptance without a reading session | A decision may come from another device or from a previous version: the acceptance signal appears, even if the signer is not among the access list. |
Cuevr does not send you an email for every reading, signature or decline; you can forward these events to an external tool through a webhook.
Readings are tracked for authorized access. Your own readings as a member are not counted. Two tabs opened at the same time by the same reader count twice.
No export of the statistics is offered for now.

A question this chapter doesn’t answer?
Write to the team: a person will reply by email.