Cookie consent examples, and the banner that has to work behind them
Every consent banner looks like the last one, and almost none of them do the same thing. This site is for the person who owns the website and has been handed the banner: what a banner has to offer, what has to stop firing until somebody answers it, and what you need to be able to produce when a visitor says they refused. Start with the free cookie audit worksheet, which counts what your site actually sets and how much of it is already running before anyone has been asked.
For the person who has to answer for the banner
Agencies and in-house web leads run this on the sites they are responsible for: one audit per property, one record per decision, and an export that goes to the client or the lawyer without a screenshot in sight.
Ask properly, hold the tags, keep the answer
- The banner offers categories a visitor can actually act on. A single accept button is not a question, it is an announcement. Here the strictly necessary set is named and separated from the rest, nothing is pre-ticked, and refusing is the same number of clicks as accepting.
- Nothing fires until the answer comes back. The failure mode is not a badly worded banner, it is analytics and ad tags calling out on page load while the bar is still sliding up. Tags stay held until the visitor has chosen, which is the one part of this an outsider can check without your help.
- Every decision is a row, and a withdrawal is a new row. The question a complaint asks is never what your settings say today, it is what was true on the date somebody says they refused. A record that holds the banner version, the categories chosen and the timestamp can answer that; a cookie in the visitor's own browser cannot.
Cookievo Pro
The worksheet tells you what is firing today. Pro is what lets you answer the harder question six months from now: what was this person shown, what did they choose, and when did they change it. Cookievo Pro is $10 a month for the whole company, billed monthly.
