Message loaded
Often triggered by an image proxy. It cannot tell you whether the attachment was read.

See exactly who opened your document, how long they spent on each page, and whether they came back for another look, not just whether the email got read.
RoundOS keeps page attention, repeat visits and recipient identity together, so a document is not reduced to one anonymous view count.

Email read receipts tell you a message loaded. A generic view counter tells you a link got clicked. Neither tells you what held attention, where it stopped, or whether the person came back a week later.
Often triggered by an image proxy. It cannot tell you whether the attachment was read.
One timestamp, detached from the pages that changed the conversation.
Identity when known, page dwell, returns, completion and forwarding stay in one record.

The point is not more metrics. It is enough context to understand what the person on the other end did.
Recipient-specific links and email verification keep sessions tied to a person. Unknown sessions stay honestly anonymous.
See when it started, how long it lasted and whether the same reader returned days later.
See which page held attention, which was skipped and where reading stopped.
A new recipient becomes a separate forwarded session instead of being folded into the original reader.
Aggregate analytics hide the useful part. RoundOS lets you read each session in context.
The unit economics slide became the center of attention. Follow up on the model.
The deck was read end to end at scanning speed. Do not pretend that is the same signal.
RoundOS Data Room and Operator share the same deal context. Operator can turn a page-level signal into a ranked next move and a drafted follow-up, with the evidence attached.
Maya returned to page 7 after six quiet days.
The last email is still unanswered.
Drafted from the page that changed the conversation.
No. The same analytics work for proposals, board packs, diligence materials and the other documents you share through a RoundOS room.
Yes. The recipient opens the same tracked room or document link. There is no extra analytics gate; when identity matters, you can use a recipient-specific link or require email verification.
RoundOS records the new reader as a separate forwarded session rather than silently crediting that activity to the original recipient.
No. Analytics begin automatically when a document is opened through a tracked RoundOS link.
The tracking itself is familiar. The difference is what happens next: the same signal can feed the Operator and become a prepared follow-up instead of remaining a report.