Review Scroll Tracking Guide

Learn how to configure and use scroll tracking to provide objective evidence for your site sign-offs and QA processes.

Why use it

Liability protection. The most common post-launch dispute is “we never saw that” — a typo, a broken element, missing footer content. The review log gives you a specific answer: the footer was on your screen for 12 seconds on 3 September at 14:02, at 94% page coverage, on desktop.

QA thoroughness. Long landing pages invite accidental skimming, including by your own team. A page only reaches verified once it passes the coverage threshold, so a section nobody scrolled to is visibly still outstanding rather than quietly assumed done.

Structured sign-off. Clients get a tangible completion metric — a live “Reviewed 72% of this page” readout in the widget — which encourages a top-to-bottom pass instead of jumping around and declaring the site done.

Turning it on

Scroll tracking is off by default, per project. On the Feedback project → ⚙ settingsReview scroll tracking:

SettingMeaning
Track how much of each page is reviewedMaster switch. Off by default.
Mark reviewed at … % of the page seenCoverage threshold for verified. Default 90, allowed range 50–100.

Changing a setting can take up to 5 minutes to reach pages that are already open due to loader caching.

The Client Review URL

Asking a client to “open the little tab first” is the step they forget. To solve this, use a Client Review URL — your address with #wscfb-review on the end.

Following that link enables the session directly. The client then just browses the site normally and every page counts; there is nothing to open and nothing to remember. The launcher picks up a coloured ring so it's visible that review mode is on, but the panel deliberately stays shut.

No login required

The link carries no login and no identifier — it's a flag, not a token. The fragment is stripped from the address bar on arrival, so a reload doesn't re-announce it.

Privacy and Scope

  • Opt-in per project: Off by default. No tracking surface is exposed unless you explicitly enable it.
  • Consent Gate: Only after the widget is opened or a Client Review URL is followed. Public visitors are never measured.
  • Stored per session: Page, phase, device, coverage, dwell, document height, user agent, IP, timestamp. No cookies or cross-site identifiers.