Privacy and measurement
A blocked script, an empty dashboard, and reduced data collection are different observations. Use a test that explains what happened.
Begin with a specific question: does a known browser request occur, does an optional analytics script load, or does a page continue to function without that script? Keep the question separate from broader claims about every system that may receive data.
For a publisher, good testing includes the visitor experience when measurement is unavailable. Navigation and core content should be evaluated independently from the presence of an analytics integration.
Record the browser, filter configuration, consent choice, page, and actions taken. Compare the same sequence with one deliberate change at a time. Cached resources, earlier page state, or different choices can otherwise make the comparison misleading.
When using a browser’s network tools, begin recording before the relevant action and inspect the request in context. The analytics testing fieldnote includes an official reference and a full test protocol.
A missing request is evidence about that request under the tested conditions. It does not establish that the publisher has no server-side logs or that every other measurement path has stopped. A blank visual element is weaker evidence still.
If an application function breaks, identify the dependency rather than assuming analytics must be essential. For a site you control, consider whether optional measurement has been coupled to necessary features and whether that coupling can be removed.
Request logs can contain sensitive URLs or identifiers. Retain only what your investigation needs, and remove private values before sharing a report. Describe the reproducible steps and relevant rule instead of publishing a complete browsing history.
Read domain list scope to understand hostname-level limits, or use the list-selection guide when choosing a starting configuration.
No. Check the relevant requests and behavior. Visual removal alone does not establish which data was transmitted.
A filter is a technical control, not a legal determination. Legal obligations depend on the actual processing, context, and applicable requirements.
From Ad Block List Lab
Build a repeatable analytics-blocking test that checks both connection behavior and useful page functions, with careful evidence collection, meaningful negative cases, and clearly bounded conclusions about results.
6 min readStart with what you want to control. Then choose a list, a compatible tool, and a way to check that the result works for you.
Explore this topicA hostname is only part of a web request. Understand what domain-level filtering can see before expecting page-level precision.
Explore this topic