Engagement analytics
Know who read what, page by page, and follow up at the right moment
Every visit tells you who came, which pages held their attention, where they stopped and what they downloaded. Live, in your inbox, or in your own tools.
The problem
"Did they read it?" should not be a guess
You sent the deck on Monday. Was it opened? Did they get past the financials? Are they reading it right now? An attachment answers none of that. A link answers all of it.
What you learn
From the first open to the last page
Reading time per page
See how long each page held the reader, where interest peaked and on which page they left. Completion, at a glance.
Live viewers
Watch a visit as it happens: who is in the document right now and on which page.
Who they are
Email and name when you require them, whether the address was verified, whether the NDA was signed, the device and the browser, and, if you turn it on, the country and city.
Every visit, in order
A timeline of each visit: pages in order, time on each, downloads. Compare visits of the same person across versions.
Contacts, rolled up
Every viewer across your workspace, with their last visit and everything they opened. Export to CSV and bring it to your CRM.
Notified where you work
Email on first open, on download, on NDA signature; a daily or weekly digest; webhooks to your own tools.
How it works
Nothing to set up on your side
Share a link
Analytics start with the first visit. Require an email at the gate if you want names, not just visits.
Read the signals
Open the document's analytics: visits, pages, time, downloads, live viewers. Filter by link or by date.
Act
Follow up when a page was read three times, export the contacts, or let a webhook post the visit in your own tool.
Seen by the recipient
Told at the gate, not hidden in a policy
Before the first page, your recipient reads one line: the sender receives their reading activity. No hidden pixel, no fingerprint, a stated rule, in their language.
Where your analytics are computed
Visits are recorded and analysed on dedicated servers in France, operated by a French company, outside the scope of the US CLOUD Act. Viewer IP addresses are hashed; no external analytics processor is involved.
Learn moreWho uses engagement analytics most
Fundraising
Know which investor read the financials twice and call them first.
Fundraising use caseSales
Follow the buying committee: who opened, who read to the end, who stopped at pricing.
Sales use caseHR and consulting
See whether the client read the deliverable before the steering meeting.
HR and consulting use case
See who reads your next document
Join the waitlist and we will invite you when early access opens for your profession.
Questions about analytics
Do recipients know their reading is tracked?
Yes. The gate states in one line that the sender receives their reading activity, and links to the privacy policy.
Can I see who forwarded my link?
Every visit is recorded, including visits from people you did not send the link to. Require an email or a one-time code to know who each of them is.
Where does the location come from?
From the visitor's address, resolved at the time of the visit only if your instance turns it on. The address itself is stored hashed.
Can I export the data?
Yes: visits and contacts export to CSV, and webhooks push each visit to your own tools as it happens.