Every validation site is measured by three sources that do not depend on each other. A scenario is OK only when all of them agree with the expected behaviour.
| Source | What it records |
|---|---|
| Consent Monitor | Loads the page like a first-time visitor and records scripts, requests, cookies and consent signals (scenarios S1–S3). |
| Website Evidence Collector | Open-source tool of the European Data Protection Supervisor. Records cookies, requests and storage, also with a stored choice. |
| Manual protocol | A person follows a written protocol in Chrome, Firefox and Safari with the developer tools and Google Tag Assistant. |
Scenarios
| # | Scenario |
|---|---|
| S1 | First visit, no choice |
| S2 | Reject all |
| S3 | Accept all |
| S4 | Analytics only |
| S5 | Accept, then withdraw |
| S6 | Returning visitor |
| S7 | Expired choice, reset of consents |
| S8 | Logged-in user |
| S9 | Page served from cache |
| S10 | Second language |
| S11 | Other browsers (Safari, Firefox, Chrome on Android) |
What counts as tracking
A request to an analytics or marketing service that carries identifiers, or a cookie of such a service, before the visitor allows its category. Cookieless Google pings in Advanced Consent Mode (gcs=G100) are allowed when they create no cookies, as Google designed them.
Limits
- The results describe this site with this setup, not every WordPress site.
- Measurements are technical findings, not legal advice.
- After every new plugin release the sites are updated and measured again; older results stay in the history.