More in Tracking & analytics

How read tracking works

Updated 17 November 2026

Every public link you create in Quixli is tracked, on every plan, and there is nothing to switch on. When someone opens the link, Quixli records a visit: when it started, how long the document was on their screen, how much of that time they were active, and roughly where they were and on what device. This article explains how a visit is counted, how the two time figures are measured, which visits are kept out of your numbers, and how long the data is kept.

Visits are recorded on public links, and on the link each person gets when you share a quix by email. People you share a document with by email, or through a domain, your team or a folder, open it in the Quixli editor under their own account, and the editor records no visit.

When a visit starts

A visit starts when the reader gets to the document. If the link has a PIN, an email gate, a view limit or an expiry date, all of them have to pass first. Someone who opens the link and gives up at the PIN screen is not counted as a reader.

While the document is open, the reader's browser sends a short signal every 15 seconds. The time figures are built from those signals. A tab in the background sends nothing, and closing the page sends one last signal.

If no signal arrives for five minutes, the visit is closed at the last signal. Closing it is a guess that the reader has gone, and it can be undone: if the same reader comes back within 30 minutes, Quixli continues the same visit instead of starting a new one. The time they were away is never added.

What counts as the same visit

Quixli continues a visit only when all of these match: the same link, the same browser, and the same kind of reader. So:

  • Reloading the page continues the visit. Pressing refresh four times is still one visit.
  • Opening the link again from the same email within half an hour continues the visit too.
  • A second link to the same document is a different visit, even for the same person. If you send separate links to separate people, each person's visits stay on their own link.
  • A second device is a different visit, and usually a different reader in the count; see "Unique people" below.
  • Signing in to Quixli changes the kind of reader, so the next load starts a new visit. A client who was anonymous and is now signed in is counted under their account from then on.

If you delete the link or it expires while someone has the document open, their next signal is refused and the visit stops gaining time. They see a banner, "Access to this document has ended", and what is already on screen stays.

What a visit records

  • Which link was opened, and who it was sent to if you shared a quix by email
  • The address typed into the email gate, if the link has one
  • The account, if the reader was signed in to Quixli
  • Device type (desktop, mobile or tablet), browser and operating system
  • Country and an approximate city, looked up from the IP address on our own servers, with no outside service. Country is right far more often than city; a city is often the nearest large town of the reader's internet provider, which is why the dashboard marks cities as approximate.
  • Time on screen and reading time (below)
  • If the document has headings, how long each section stayed on screen; see section attention

Time on screen and reading time

You see two figures for every visit, and they answer different questions.

On screen is how long the document stayed open and visible. Each signal adds the time since the one before. If a gap is longer than 45 seconds, because the laptop went to sleep or the connection dropped, that gap adds nothing. A gap that long means the reader was not there, or the signals were not getting through, and Quixli does not guess which.

Reading time is the part of that time when the reader was active: the tab was in front, the window had focus, and they had scrolled, typed or moved the pointer in the last two minutes. A document left open in a window beside the one they are working in builds up time on screen and almost no reading time. Reading time can never be higher than time on screen: the browser can only lower its own figure, never raise it past what the server measured.

When the two figures are far apart, the reader probably opened the document and then did something else. When they are close, they were working through it.

Build a visit below to see what each figure would come to.

What would Quixli count for this visit?

Build a visit out of a few parts, in order. Pick a part to change what happens in it and for how long.

The visit, in order
What happens in part 1
For how long

On screen

8m 45s

Reading time

4m 45s

Reading time is 54% of the time on screen: someone worked through it, with stretches away or hands off.

A timer running from open to close would have said 11m 0s.

1. Scrolling and reading2m 0s

On screen
1m 45sReading
1m 45s

Tab in front, window focused, input all the time, so what is credited counts on both figures. 15s of it fell inside a gap longer than 45 seconds and counts for nothing.

2. Switched to another tab2m 0s

On screen
0sReading
0s

A hidden tab sends no signal. The gap was longer than 45 seconds, so it adds nothing.

3. Scrolling and reading1m 0s

On screen
1m 0sReading
1m 0s

Tab in front, window focused, input all the time, so what is credited counts on both figures.

4. On a call, page up, no input6m 0s

On screen
6m 0sReading
2m 0s

Signals keep coming, so it counts on screen. Reading time stops 2 minutes after the last scroll, keypress or pointer move.

Bars show how much of each part was credited. Worked out with the rules in our help centre: a signal every 15 seconds, no credit for a gap longer than 45 seconds, reading time only with input in the last 2 minutes.

What is left out

Four kinds of visit never reach your counters, alerts or daily digest:

  • Bots and link previews. When a link is pasted into Slack, WhatsApp, Telegram, LinkedIn and similar apps, the app fetches it to draw a preview. Those fetches, search engine crawlers, headless browsers and command-line tools are recognised by their browser signature and set aside.
  • You. Opening your own link to check it does not count, as long as you are signed in.
  • Your team. Views by active members of the workspace that owns the document are shown separately, in a card called "Reads from inside your workspace", and kept out of views, unique people and reading time.
  • Anyone who did not get past the link's checks, as above.

Note

The view limit on a link works differently: it counts every successful open, including your own and, sometimes, an email security scanner. If you set "Max views" to 1 and then test the link yourself, the reader will find it already used.

Unique people is an estimate

The dashboard shows unique people as "≈ 12" because it cannot be exact. A reader is counted by their Quixli account if they were signed in, by the address they typed into the email gate if there was one, and by their browser otherwise. So the count can be off in both directions:

  • One person on a second device, in a private window or with cookies blocked can be counted twice.
  • Two people sharing one browser count as one.
  • Someone who only saw a shared screen, a screenshot or an exported PDF is not counted at all.

The address you sent a quix link to by email is not used to count people. Links get forwarded, and everyone who opens a forwarded link would otherwise be counted as the person you sent it to.

What the reader is told

There is no consent banner on a shared document. At the end of the document, and on the PIN screen if the link has a PIN, the reader sees a small link, "How your visit is recorded". It opens the part of Quixli's privacy policy written for people who received a document.

How long the data is kept

  • IP addresses are shortened after 30 days. For IPv4 the last part is dropped; for IPv6 only the first four groups are kept. The country stays.
  • Raw tracking events are deleted after 12 months.
  • You can delete everything recorded for one document at any time: open its analytics, click the … menu and choose Delete all tracking data, then Delete permanently. That removes every visit, event and captured email address across all of its links, and it cannot be undone. Alerts and digests that were already sent cannot be recalled.

This is also how to act on a reader who asks for their data to be deleted. It removes every reader's data for that document, not only theirs.

What tracking cannot tell you

It cannot tell you that someone took in a sentence, agreed with it or forwarded it. Reading time says the document was in front of an active person; it does not say what they thought. A long reading time on a proposal is a reason to follow up, and the analytics dashboard and view alerts are where to watch for it.

Questions

Does tracking work if the reader blocks cookies? Yes. The visit and its times are still recorded. Without the cookie, each page load looks like a new browser, so that reader may be counted more than once in unique people.

Is a PDF a reader downloads tracked? No. Tracking covers the document in the browser. Once someone has a PDF, Quixli knows nothing about what happens to it; see reader downloads.

Why does a visit show 0s of reading time? The document was open but nobody was active on it: it sat in a background tab, or the reader opened it and walked away. It still counts as a view.

Can I turn tracking off for a link? No. Every share link is tracked. You can delete a document's tracking data at any time, as above.

Related

  • See which sections held attention

    Section attention shows how long each heading of your document stayed on a reader’s screen, which they passed over and which they came back to.

  • See who opened your document

    Who opened a link: a signed-in account, the email gate or a quix sent by email. Why documents shared by email show no visits, and the Free and Pro limits.

  • Use the analytics dashboard

    Find your way around Analytics: the overview tiles, a single document’s readers and audience, the PDF report, and who in a team can see what.

  • View alerts and the daily digest

    Get an email a minute or two after someone opens what you sent, or one summary each morning. When alerts fire, what they say, and how to turn them off.