What is Cookie Banner?

The banner is the visible tip of a consent system. Behind it sit a consent management platform that stores choices, script-blocking logic that enforces them, and a record store that proves them. A banner that exists only as UI — displaying while every tracker fires underneath — fails at the one job that matters.

What a compliant banner looks like depends on jurisdiction. For EU/UK visitors it must offer a genuine first-layer choice: accept and reject with equal prominence (several EU regulators have fined sites where rejecting took more clicks than accepting), purpose-level granularity at most one layer deep, no pre-ticked boxes, and no tracking until a choice is made. For California visitors the banner is less about opt-in and more about disclosure plus a working 'Do Not Sell or Share My Personal Information' pathway and honoring GPC signals automatically.

Design choices carry legal weight. Making 'Accept' a bright button and 'Reject' grey text, hiding refusal behind 'Settings,' or nagging repeatedly after refusal are dark patterns — and consent obtained through dark patterns is invalid by definition under the CPRA and by regulatory guidance in the EU. The banner must also link to the cookie policy and name purposes accurately, which requires knowing what the site actually sets.

Operationally, banners need maintenance: purposes and vendor lists drift out of date as tags change, translations must match the visitor's language, and the banner version shown must be recorded with each consent so you can later prove what the visitor agreed to.