Do Your Own Views Show Up in Your Document Analytics?

It is the first thing anyone does after setting up a tracked link: open it themselves to check it works. The second thing is to wonder whether they have just corrupted their own data.

The short answer is no, and the long answer is more interesting than the short one — because the way a product handles its owner’s own traffic tells you quite a lot about whether its other numbers can be trusted.

What is separated, and what “separated” means

A read by you, or by an active member of the workspace that owns the share, is marked as internal. Marked reads are excluded from every client-facing counter, from the view alerts and from the daily digest. They are not thrown away — they are shown to you separately, as reads inside your workspace, with a count of reads and a count of people and nothing else.

The vocabulary is kept deliberately apart. The internal figures say reads and people inside your workspace; the client figures say views and visitors. Two numbers on one screen that mean different things should not share a noun, because someone scanning quickly will read whichever word they saw first.

Why exclusion alone was not enough

Excluding your own reads is the obviously correct behaviour — the product exists to answer “did the client read it”, and a colleague is not a client. But excluded and hidden are different things, and hiding produced a specific, real confusion.

A document that three people on your team had opened, and no client ever had, appeared under “not opened”. That is entirely true and it reads as “the link is broken”. You end up re-sending a working link, or worse, quietly assuming your tracking is not working.

Showing the internal count beside the client count answers that in one glance: the link works, we have proved it ourselves, the client has not been. Separate is a better answer than either counted or hidden.

What the internal figures deliberately do not include

No names, no addresses, no device, no location, no reading time. A count of reads and a count of people, and that is the whole of it.

The reasoning is worth stating because it is a boundary rather than an omission. All the identity machinery in this product governs one thing: readers of your documents, and how much a label about them is worth believing. Colleagues are not readers in that sense. Building a second identity surface aimed at your own staff would turn an analytics product into a monitoring one, and it is a line worth not crossing by accident.

The three ways your own traffic still gets counted

The separation depends on recognising you, so it fails in exactly the cases where you are not recognisable:

1. You opened the link signed out. A private window, a different browser, a machine you are not signed in on — nothing connects that visit to you, and it lands in your client numbers as an anonymous reader.

2. You opened it on a personal phone. Same reason. This is the most common one, because checking a link on your phone is exactly what people do before sending it.

3. Someone outside your workspace is on your side. A subcontractor, an accountant, a designer who is not a member of the workspace. To the data they are a reader like any other, and no rule can know otherwise.

So the practical habit: to check a document looks right, open it from your own dashboard rather than through the share link. If you must test the link itself, do it while signed in, in your normal browser. It costs nothing and it keeps the first entry in your reader list from being you.

Why this is worth caring about beyond tidiness

Three reasons, in ascending order of consequence.

• Your alerts stay meaningful. If your own opens triggered alerts, the notification would stop meaning anything within a week, and you would turn it off.

• Your reader counts stay small and true. A reader count that includes your team is not a reader count, and it inflates in the one direction you would most like it to inflate — which is precisely why a product should be suspected of allowing it.

• It is a test you can run on any tool. Send yourself a link, open it a few times, and see what appears. If your own opens land in the client-facing totals, every number that tool shows you is measuring your team as well as your prospect, and you have no way to separate them after the fact.

What you must not conclude

• Not “every view in my dashboard is my client”. It is every view that was neither a recognised machine nor a recognised colleague. Two filters, both imperfect at the edges.

• Not “the internal count tells me who on my team looked”. It does not carry names, on purpose, and it never will.

• Not “zero client views means the link failed”. Check the internal count first — if your side can open it, the link is fine and the silence is real.

The other contaminant in the same numbers is automated traffic, covered in was that a real reader or a link preview. What is separated, filtered and shown is set out on the features page.