Practical guide · Search topic: Do Not Track and Global Privacy Control analytics
Do Not Track and Global Privacy Control in website analytics
Do Not Track and Global Privacy Control are browser signals that can communicate a visitor’s preference. Whether a specific analytics script responds is a product and configuration question; check the exact snippet and implementation.
What the query can—and cannot—measure
In quietstats’ default snippet, the `data-dnt="true"` setting is intended to stop collection when DNT or GPC is enabled. A different tag, custom loader or tag manager may behave differently. A privacy notice should describe the actual setup, not just the tool’s general feature list.
A practical way to do it
Test in a controlled browser profile with the signal enabled, verify no analytics event is sent, and repeat after site changes. Keep testing separate from customer data and do not infer that every tag on the page honours the same signal.
A useful checklist
- Inspect the script configuration and tag manager rules.
- Test DNT and GPC in an isolated browser session.
- Verify the request is absent, not merely hidden in a report.
Limits to keep in mind
A signal is not a substitute for understanding other scripts or legal requirements on the site.
Questions
Does every analytics product honour GPC?
No; verify the specific product and configuration.
Does DNT stop every tracker on my page?
Only if each relevant script is configured to honour it.
Sources and further reading
Related pages
Zero cookies, privacy built in · quietstats cookie-free analytics Install guide & docs · quietstats Compliance: PECR, UK GDPR, sub-processors & retention · quietstats
Put your traffic in context
Explore the product, its measurement method and pricing before choosing a tool.