Cookie Consent: What Your Site Must Show
When a cookie banner is required, what valid consent looks like, and how to set one up without wrecking user experience or analytics.
Cookie consent dialogs exist because tracking technologies store or access data on visitors’ devices. Getting consent wrong annoys users AND creates legal exposure — getting it right is mostly common sense.
When You Need Consent
Strictly necessary cookies (login sessions, cart, security) do not need consent. Analytics, advertising, embedded media, and personalization cookies generally do, unless you rely on an accepted legal basis your counsel has confirmed.
What Valid Consent Looks Like
Freely given, specific, informed, and unambiguous. Rejecting must be as easy as accepting — no pre-ticked boxes, no dark patterns hiding the decline button. Records of consent should be kept.
Balancing UX and Compliance
Layer the dialog: a clear summary with accept, reject, and customize options; details behind the customize panel. Run analytics in privacy-friendly modes where possible to reduce the weight of consent-gated scripts.
Frequently Asked Questions
Do I need consent for Google Analytics?
In most interpretations of EU rules, yes — or use a consent-mode configuration that respects refusals.
Can I block all content until consent?
Technically yes, but it wrecks experience — minimize consent-gated scripts instead.
Does a banner replace a privacy policy?
No — you need both; the banner handles real-time choice, the policy handles transparency.
Open your own site in a private window: can a visitor decline non-essential cookies in one click? If not, fix the dialog.