Docs

Documentation

Everything the 1270-byte script can do, what each setting changes, and how to read your numbers back out. Written against the code that ships, not against a roadmap.

Verified against the shipping code, September 2026

Start here

If you have five minutes and a website, the whole product is one script tag. Install the script walks through it, shows you how to prove it is working, and covers the three situations that are not quite one tag: single-page apps, tag managers, and a content security policy that blocks third-party scripts.

Everything after that is optional. You get pageviews, referrers, countries, devices and realtime visitors without configuring anything at all.

All pages

Start here

Measuring things

Privacy controls

Reference

What this documentation will not tell you

How it is built. You will find the guarantee — no cookies, no localStorage identity, no IP address stored anywhere, a one-way daily-rotating visitor hash that cannot be reversed or joined across days or across sites — stated plainly and repeatedly, along with everything you need to verify it in your own browser's developer tools.

You will not find the storage design, the shape of the counting, or the construction of the hash. That is not coyness about a weakness; it is that a competitor reading these pages should learn how to use the product and be reassured about privacy, and learn nothing that helps them build it. Where a claim needs proof, we point you at something you can observe rather than at something you have to take on trust.

Known gaps, stated up front

Three things a reader will look for and not find, so nobody wastes an afternoon:

  • There is no self-hosted build, and no plan for one. If running the server yourself is a requirement, we are the wrong product — see the Plausible comparison, which says so plainly.
  • The Stats API is a Business-tier capability. That is the incumbent's gating, reproduced deliberately, and it is the single most criticised thing about their pricing. The reference says so on its first screen rather than after you have written the integration.
  • The script does not honour Do Not Track or Global Privacy Control, and does not pretend to. What it has instead is a real opt-out you can wire to a real control — see visitor opt-out.

Something missing?

These pages are written from the shipping source and dated. If something here does not match what you are seeing, that is a bug in the documentation and worth telling us about — the privacy policy carries the contact address.