After the banner: reject and accept

The weekly ranking measures pages before any interaction. This separate test goes one step further: after the same passive window, it presses the consent banner's reject (or accept) button once, in a fresh browser each time, and records what the page contacts in the following seconds.

How this test works, and what it does not say

• Each site is loaded in a fresh browser, exactly as in the weekly measurement. After the passive window, the tool looks for the banner's button: first by the documented ids of common consent tools (OneTrust, Cookiebot, Didomi, Sourcepoint, Quantcast, Usercentrics, Google Funding Choices and others), then by the button's exact text (“Reject all”, “Alle ablehnen”, “Rechazar todo”…) inside a block that talks about cookies, consent or privacy. It presses that one button and nothing else, then records the next window.
• “After” counts tracking services in our list contacted in the window after the click. “New” counts those that were not contacted before it. A service contacted after rejecting is a measured fact, not proof of unlawful processing: some requests may be needed to record the refusal itself, or may carry no personal data.
• “Not found” means our detector found a banner but no one-click reject button on its first layer. The option may exist behind a “settings” or “manage” button. When the banner shows a button offering a subscription or an ad-free paid option instead (“pay or accept”), we note its text; we never press it. We do not open settings menus.
• “No banner detected” means our detector did not recognise one. Banners depend on the visitor's country: from outside the EU and UK many sites show none.
• Both choices are measured in separate fresh browsers. A link that would leave the page is never followed, nothing is typed, and no account is used.
• This test is separate from the weekly ranking and never changes it. Raw reports: data/consent/<origin>/<date>/; table: consent.csv.