Share it, then see how it landed.
A private link is only half the job. Stacktree tells you how the page was received: reactions and private notes from viewers, an activity feed and an optional daily digest, and engagement analytics that show the time on page, the scroll depth, and where readers actually lingered. Aggregate and private, never a recording.
Aggregate and private. No recording.
- 🔥Reacted on Q3 board update2m
- Note: “the pricing slide nails it”1h
- Opened by 3 people3h
Can you see how someone read a shared page?
Yes. When your agent publishes an HTML page to Stacktree, the link does more than serve the file. Viewers can react and leave a private note on the page. You get an activity feed and an optional daily email of who opened, reacted, and commented. From Solo you see the numbers behind that: opens, how many people, and when it was last read. And on Studio, an engagement view shows the typical time on page, the scroll depth, the share of readers who reached the end, and an attention heatmap of where they lingered. All of it is aggregate and non-PII: no session replay, no keystrokes, no identity.
The gap this closes
Most hosts hand you a link and stop. You send a report, a proposal, a dashboard, or a build, and then you are guessing. Did they open it? Did they read past the first screen? Did the pricing section land or get skipped? For a client deliverable, that guess is the whole game.
Stacktree closes the loop in three layers, from the lightest signal to the most detailed, and keeps every one of them on the right side of privacy.
1. Reactions and notes
Turn on the reaction bar for a site and viewers can react with an emoji or leave a short private note, right on the page, with no account. It is the low-friction signal that formal comments miss: a client will tap a heart on a deck they would never write a paragraph about. If several people are viewing at once, reactions animate in live, so a shared review feels shared. Reactions are opt-in per site, so a polished deliverable stays clean until you want them.
When a page needs a real review cycle rather than a pulse, the client feedback loop is the heavier sibling: element-anchored comments your agent reads over MCP, fixes at the same URL, and marks resolved.
2. How it is read
This is the DocSend question applied to agent-built HTML: not just whether the page was opened, but how it was consumed. On Studio, the engagement view shows:
- Typical time on page. The median engaged time, counting only when the tab is visible and focused, so a page left open in a background tab does not inflate the number.
- Scroll depth and read-to-end rate. How far readers get, and what share reach the bottom.
- An attention heatmap. Dwell time by page depth, so you can see the section that held attention and the one that got skipped.
It is aggregate and non-PII by design. No recording, no keystroke capture, no identity attached. It extends the "opened by ~N people" count that Solo carries, rather than turning a private link into a tracking product.
Aggregate and private. No recording.
3. Notifications that bring you back
Signal is only useful if you see it. The dashboard has an activity feed and a notification bell that show what happened to your pages while you were away, newest first: opened, reacted to, commented on. An optional daily email digest summarises the reactions, notes, and opens once a day. The digest is off by default, and every one carries a one-click unsubscribe. On Free you are told a page was opened; the counts arrive with Solo.
- 🔥Reacted on Q3 board update2m
- Note: “the pricing slide nails it”1h
- Opened by 3 people3h
Why not session replay
Session replay records the viewer. On a private client deliverable that is both a privacy liability and a bad fit for a host that leads with private-by-default links. Stacktree deliberately stops at aggregate: enough to tell the owner how the deliverable landed, without ever surveilling the reader. You get the answer to "did they read it, and what held their attention" without the recording.
How this compares
| Criterion | A plain static host | Stacktree |
|---|---|---|
| Get a private link | Yes | Yes |
| Know it was opened | Rarely | Yes, on every plan |
| How many people opened it | No | Yes, from Solo |
| Reactions + private notes | No | Yes, opt-in per site |
| Time on page + scroll depth | No | Yes, from Studio |
| Attention heatmap | No | Yes, from Studio |
| Activity feed + daily digest | No | Yes, on every plan |
| Records the viewer | n/a | No, aggregate and non-PII |
Frequent questions
Can I see how someone read a shared HTML page? +
Is this session replay or recording? +
What do reactions and notes look like for a viewer? +
How do I find out when a page gets opened or reacted to? +
Which plans include this? +
Is any of this on by default? +
Related guides
- Analytics without recording anyone The design behind the engagement view, and why aggregate.
- Pricing Reactions on every plan, viewer numbers from Solo, engagement from Studio.
- Host AI-generated reports The deliverable this loop was built for.
- Share Claude artifacts Publish an artifact, then see how it lands.
Send the link. Then find out how it landed.
Reactions and notifications are on every plan. Viewer numbers start on Solo at $19 a month.
Sign up free →