Document analytics explained in one sentence: they tell you what happened after you shared a file, from who opened it to how long they spent on each page. The catch, and the thing that trips up almost everyone reading these numbers for the first time, is that not every "view" means the same thing. There is a world of difference between a raw visit, meaning someone loaded the link, and a verified viewer, meaning a named person confirmed their identity through email and a one-time code before opening. Confuse the two and you will draw the wrong conclusions from your own data. This guide explains what document analytics really show, how to tell a visit from a verified view, and why the distinction changes how you act on the numbers.
Whether you are a founder tracking an investor deck, a salesperson watching a proposal, or an accountant sending client accounts, the promise of analytics is the same: no more wondering whether the file landed. But raw curiosity ("did they open it?") is easy to answer badly. The useful question is "did the right person actually engage, and how do I know it was them?" That is where the visit-versus-verified split earns its keep.
What a raw visit actually tells you
A raw visit is the lowest bar an analytics system can record: a link was loaded. Something, somewhere, requested the document. That is genuinely useful as a signal of delivery and timing. If you sent a deck on Monday and the link was opened within the hour, you know it arrived and that someone was interested enough to click. Visit-level data typically captures when the open happened, roughly where from, and sometimes how many times the link was loaded.
But a visit does not tell you who. A link can be opened by the person you sent it to, by a colleague they forwarded it to, by an email security scanner that automatically follows links, or by a preview bot that renders the page to generate a thumbnail. All of those register as activity. If your tool reports "3 views" and you assume that means three humans read your document, you may be badly wrong: it could be one person, one scanner, and one link-preview crawler. Treating raw visits as proof of human engagement is the single most common analytics mistake, and it leads founders to either panic ("nobody's looking") or celebrate ("everyone's reading it") on the strength of numbers that do not mean what they think.
This is also why the plumbing matters. Tools that quietly load third-party trackers can inflate or distort visit counts, and some leak viewer data to advertising networks in the process. 99 Data Rooms uses no third-party viewer trackers, so a visit is a visit in your room and nowhere else. If you are choosing between tools on the strength of their tracking, our roundup of the best tools to track who opened your PDF walks through what to look for.
What a verified view adds
A verified view raises the bar from "a link was loaded" to "a named person confirmed who they are and then opened the document". In 99 Data Rooms that means the viewer entered their email and a one-time code sent to that address before the file rendered. The difference is identity. A verified view attaches a real, confirmed person to the activity, which means the page-by-page data that follows, time on each slide, order of viewing, whether they reached the financials, is anchored to someone you can name rather than to an anonymous request.
This is the number that should drive decisions. If a verified investor opened your deck, spent four minutes on the traction slide, and came back twice, that is a signal worth acting on. If you only have a raw visit, you have delivery confirmation and nothing more. The verification step also filters out most of the noise: scanners and preview bots do not have your one-time code and cannot pass the gate, so they never become verified views. That is why the verified number is almost always smaller than the visit number, and why a smaller-but-verified figure is worth more than a larger-but-anonymous one.
The mechanism behind verification is the access gate, which requires a verified email plus a one-time code before anyone sees the content, with NDA acceptance available on the Business tier. Gating is what makes the verified layer possible in the first place; without a gate, every view is a raw visit. We explain how it works on our gating and access-control page, and the practical upshot is that verification is not a separate analytics product, it is a consequence of controlling access properly.
How to read the two numbers together
The right way to use document analytics is to hold both numbers at once and understand what each is for. Use raw visits to answer questions of timing and delivery: did the link arrive, when was it first opened, is there a burst of activity after you followed up? Use verified views to answer questions of engagement and intent: did the specific person you care about actually read it, which sections held their attention, and did they return?
A worked example. You send a pitch deck to five investors through individual gated links. Over a week you see eleven raw visits but only four verified views. Read naively, eleven views sounds like strong interest. Read correctly, it means four of your five investors confirmed their identity and engaged, one has not opened it at all, and the gap between eleven and four is mostly re-opens, forwards and automated scans. Now you know exactly who to chase and who is genuinely engaged. That is a far more useful picture than a single inflated view count. We take this specific scenario further in our guide on how to tell if an investor actually read your deck, which shows how to turn verified page-by-page data into a follow-up decision, and if you are still setting up the send itself, our guide on the best way to share a pitch deck with investors covers the full workflow.
The general rule: verified views are your quality metric, raw visits are your reach metric. Never let a big reach number stand in for real engagement, and never dismiss a document as ignored just because the verified count is small; a small verified count of the right people is often exactly what you wanted.
Two related points are worth keeping in view. First, if you also watermark on the Business tier, a leaked page can be traced to a verified viewer by name, which is why analytics and document watermarking reinforce each other rather than compete. Second, analytics only stay meaningful for as long as your link stays live; a link left open forever keeps accruing anonymous visits long after the deal is done, which is why we cover how long a share link should stay live as its own decision.
How 99 Data Rooms handles visits and verified views
99 Data Rooms is built so the two layers are clearly separated rather than blurred into one misleading total. When you share a document as a tracked, revocable link, the page-by-page analytics show both a raw visit and, where the viewer passed the gate, a verified view tied to a confirmed email. You can see time spent per page, the order pages were viewed in, and whether a viewer returned, all attributed to a named person once they have verified. Because the platform runs no third-party viewer trackers and is UK-hosted in London, the data you see is your data, not something shared with an ad network.
The wider journey makes the numbers actionable. A document can be drafted from vetted clauses, gated so only verified emails plus a one-time code get in, shared as a link you can revoke in one click, and tracked at the page level, with dynamic watermarking available on the Business tier if you want every copy stamped with the viewer's identity too. Analytics are not a bolt-on dashboard here; they are the natural readout of a controlled sharing process, which is what makes the visit-versus-verified distinction meaningful rather than cosmetic.
See your own analytics for free
The best way to understand visits versus verified is to watch your own document being read. In 99 Data Rooms you can draft, gate, share a tracked link and see page-by-page analytics with a clear split between raw visits and verified viewers, all in one place. The free tier is a real tier, not a trial: three rooms, twenty-five active links, forever, no card required. Start for free, share a document, and see exactly who engaged and how. The platform is in beta and improving fast, but the analytics already tell you what most tools cannot: not just that a file was opened, but who really read it.
Sources
What is the difference between a visit and a verified view?
A visit means the link was loaded by someone or something, which could be your recipient, a forwarded colleague, or an automated scanner. A verified view means a named person confirmed their identity with an email and a one-time code before opening the document. Verified views tell you who engaged; visits only tell you the link was accessed.
Why is my visit count higher than my verified count?
Because visits include re-opens, forwards, email security scanners and link-preview bots, while verified views only count people who passed the identity gate. A gap between the two is normal and healthy; it means the verification step is filtering out the noise. The smaller verified number is usually the one worth acting on.
Do document analytics tell me exactly who read my file?
Only if the viewer verified. A raw visit is anonymous by nature. Once someone passes an email-plus-code gate, the page-by-page activity is attributed to that confirmed identity. This is why gating and analytics work together, as covered on our gating page and analytics page.
Can automated scanners inflate my numbers?
Yes. Email security tools and preview crawlers routinely follow links, which shows up as visits. They cannot pass a one-time-code gate, so they do not become verified views. This is the main reason to trust verified figures over raw visit counts.
Does 99 Data Rooms share my viewer data with advertisers?
No. 99 Data Rooms uses no third-party viewer trackers and is UK-hosted in London with data resident in the UK. Your analytics are yours.