One banner per site, answered before your agent looks
Roughly seventeen consent platforms are recognised by their own selectors and APIs, and a heuristic covers the rest. Reject is the default; accept is an explicit choice. These pages document the recognisers one CMP at a time.
The rules every recogniser follows
The CMP’s own path
A deny button or the vendor SDK, never a hidden overlay or a hand-written cookie. The site stores the decision as it would for a visitor.
Done means gone
The banner element must leave the page for the action to count. A click that changed nothing is reported, not assumed.
Fail safe on drift
Vendors rename things. A selector that no longer matches makes the recogniser silent; the heuristic runs next, and if that finds nothing the banner stays and observe says so.
Three values, one default
reject by default, accept only when you say so, off when the banner is yours to handle.
See what observe returns on your site
Five browser hours, no card. The banner is handled inside the first call.
-
Borlabs Cookie banners in browser automation
How the consent autopilot recognises the Borlabs Cookie box that most German WordPress sites run, refuses through its own link, and what it does not do.
-
Cookiebot banners in browser automation
How the consent autopilot recognises the Cookiebot dialog, declines through the decline button or submitCustomConsent, and confirms the dialog is gone.
-
OneTrust banners in browser automation
How the consent autopilot recognises the OneTrust banner and preference centre, rejects through the reject-all handler or OneTrust.RejectAll, and verifies it.
-
Usercentrics banners in browser automation
How the consent autopilot recognises a Usercentrics CMP inside its shadow root, rejects non-essential cookies by default, and what it records.
-
consentmanager banners in browser automation
How the consent autopilot recognises the consentmanager box used across German Mittelstand sites, declines through its own button, and hands the page on.