Start free
new

What changed, linked to traffic

See what you changed on your site — notes, deploys, changelog entries and campaign sends — next to that day’s visitors on the trend chart.

In every plan, including Free. See your traffic.

📘 Step-by-step guide, with screenshots and diagrams →

Start free, no cardOpen the demo

What changed, linked to traffic: example screenshot with made-up demo dataWhat changed, linked to traffic: example screenshot with made-up demo data
ExampleScreenshot with made-up demo data, not a real customer’s numbers.

What it is

A What changed list under the Trend card gathers your existing chart notes, new deploy and changelog markers, and campaign send dates, each shown with that day’s visitors and the change from the day before. The same items appear as coloured flags on the chart. The Chart notes form is still there: add a note, a deploy or a changelog entry by hand, or create a hook URL so CI can POST a short label when you ship.

Why it matters

A spike or a drop is easier to explain when the deploy or the post that may have caused it is sitting on the same chart.

How it works

  1. On the Trend card, open Chart notes and add a note, or pick Deploy or Changelog and type a short label (for example v1.4 or “Pricing rewrite”).
  2. Or click Create a deploy hook and add a POST from CI to that URL. The body can be {"kind":"deploy","text":"v1.4"} or {"kind":"changelog","text":"…"}. The token is shown once. Nothing about a person belongs in the label.
  3. The What changed list shows each marker next to that day’s visitors. Campaigns you already added keep their ✉ markers and are included in the list.

Privacy: what is and isn’t collected

Collected

  • The date and the short label you (or your CI hook) send
  • The visitor total already on the chart for that day

Never collected

  • Source code, commit messages, or anything about a person
  • Payloads beyond an 80-character label
  • Cookies, localStorage or anything else stored on the visitor’s device
  • IP addresses or user agents (used in memory, then discarded)
  • Anything that links a visitor across days (the visitor ID resets daily)

How quietstats works, and the legal caveats →

Rows and limits

  • Up to 200 markers per site (the same cap as chart notes)
  • The hook accepts 20 posts per site per day
  • 1 row per marker; no bulk writes
  • Core script.js is unchanged (845 B)

“Rows” are database rows written, which is what our hosting is billed on. Reads are not rows written. Methodology →

Questions

Does this replace chart notes?

No. Chart notes, the add form and delete buttons stay. What changed is a timeline of those notes plus deploys, changelog entries and campaign sends, with traffic beside them.

Will you fetch my changelog or my git repo?

No. A changelog marker is one you add, or one your hook posts. We never pull a feed or a repository.

Is the hook public?

The URL contains a secret token. Only the hash is stored. Revoke it at any time. Posts that look like personal data are refused.

Related features

All features → · Sitemap →

Set it up

Nothing to set up: it works with the standard one-line script.

HTML
<script data-host="https://quietstats.co.uk" data-dnt="true" src="https://quietstats.co.uk/js/script.js" id="YOUR_SITE_ID" async defer></script>

Try it on your own site

Free during launch: one site and 5,000 pageviews a month, no card needed. After launch, paid plans start at £5 a month.

Start freeSee pricing