Protect Analytics: UK Cookie Consent for Marketers and Agencies

Marketer testing balanced cookie consent choices

Non-essential cookies need prior, freely given consent before they load, under the Privacy and Electronic Communications Regulations as interpreted by the ICO. Strictly necessary cookies are exempt from consent but still need documenting. If you haven’t already, run a cookie audit this week and get a mechanism in place that blocks non-essential tags until someone actively opts in.


TL;DR:

  • Most cookies require user consent unless they are strictly necessary for essential functions like login sessions or shopping carts.
  • Exemptions such as transmission, temporary preferences, or emergency cookies do not require consent, but personal data processing still needs lawful GDPR grounds.
  • Valid consent must be freely given, specific, informed, and involve a positive user action, with cookie walls or pre-ticked boxes considered invalid.
  • Implementing compliant consent involves auditing all cookies, blocking non-essential tags until approval, and offering granular choices with clear settings options.
  • Many organizations fail compliance by relying on default settings or incomplete banners, risking enforcement and data unreliability, so a comprehensive, reviewed approach is critical.

Table of Contents

A cookie is a small file a website stores on a visitor’s device, but the same consent rules also cover local storage, tracking pixels, and device fingerprinting techniques that read or write information without dropping a traditional cookie file. If your site touches a browser in any of these ways, PECR treats it the same way.

Most sites run a mix of the following:

  • Session cookies — temporary, deleted when the browser closes, often used to remember a shopping basket.
  • Persistent cookies — stored for a set period, used for login memory or returning-visitor recognition.
  • Analytics cookies — track behaviour across pages, commonly Google Analytics or similar tools.
  • Advertising cookies — build profiles for targeted ads, frequently set by third-party ad networks.
  • Preference cookies — remember settings like language or currency.

Strictly necessary cookies, such as those managing a login session or a basket, generally sit outside consent requirements because the site cannot function as requested without them. Analytics, advertising, and most preference cookies almost always require consent, because the service works perfectly well without them, even if it works less conveniently.

Regulation 6 of PECR is the operative rule: you cannot store information on, or access information from, a user’s device unless the user has consented, subject to narrow exemptions. Understanding those exemptions matters more than most cookie policies suggest, because getting them wrong in either direction causes problems: over-blocking annoys users, under-blocking invites enforcement.

The exemptions worth knowing:

  1. Transmission exception — cookies necessary purely to carry a communication over a network.
  2. Strictly necessary for a requested service — the cookie is essential to deliver something the user explicitly asked for, not something that merely improves the experience.
  3. Appearance or temporary preferences — short-lived settings like screen resolution or font size, provided they don’t persist beyond the session in most cases.
  4. Emergency assistance — a narrow carve-out for cookies supporting emergency service requests.

None of these exemptions hand you a free pass on UK GDPR. Even where PECR doesn’t demand consent, if the cookie processes personal data, you still need a lawful basis under the Data Protection Act 2018. PECR governs the storage and access step; UK GDPR governs what happens to any personal data collected afterwards. Analytics data that gets pooled with other identifiers to build a profile, for instance, needs its own UK GDPR basis on top of PECR consent for the cookie itself.

The ICO’s test has four parts: consent must be freely given, specific, informed, and involve a clear positive action. Miss any one of those and the consent isn’t valid, whatever your banner says. The European Data Protection Board has been explicit that cookie walls, where a user must accept tracking to access the site at all, do not produce valid consent, and the ICO takes the same line.

Practically, that rules out a few tactics that were common a few years ago:

  • No pre-ticked boxes for analytics or advertising categories.
  • No bundling cookie acceptance into general terms and conditions.
  • No “accept all or leave” walls that block content until consent is given.
  • No burying the reject option behind extra clicks the accept option doesn’t have.

Granularity is non-negotiable too. A single “accept cookies” toggle doesn’t meet the specificity requirement once you’re running analytics, advertising, and personalisation cookies together. Each category needs its own choice, and where you’re using third-party vendors, name them.

Pro Tip: Test your own banner as if you were a mystery shopper. If accepting takes one click and rejecting takes three, that’s a strong signal your consent flow won’t survive scrutiny.

Getting from “we know the rules” to “our site actually complies” takes a sequence, not a single fix.

  1. Audit every cookie live on your site. Map each one to its purpose, retention period, and the third party (if any) that sets it. Most sites are surprised by what’s firing before anyone’s clicked anything.
  2. Design a layered experience. A short banner states the headline choice, a settings page gives granular toggles per category, and a full cookie or privacy notice covers the detail. The GOV.UK design system offers a genuinely useful reference pattern for how this layering should look and read.
  3. Block first, ask second. Non-essential tags should not fire until the user opts in. This usually means a consent management platform (CMP) with an API that gates your tag manager, plus data layer signals so consent status travels with every subsequent tracking call.
  4. Confirm withdrawal actually works. Test that clicking “withdraw consent” genuinely stops future tracking, not just future banners.
  5. Update the paperwork. Vendor contracts need to reflect who’s responsible for what, consent records need logging with timestamps, and retention windows need a documented justification rather than a CMP default.

Pro Tip: Don’t test your consent blocking in an ad blocker’s absence. Load the site in an incognito window with no extensions, then check your network tab for any tag firing before the first click.

Choosing a CMP and avoiding common banner mistakes

A consent management platform earns its cost if it does four things properly: blocks non-essential tags until there’s a valid opt-in, offers real per-category toggles rather than a fake “customise” button that leads nowhere, keeps an audit log of who consented to what and when, and makes withdrawal as easy as giving consent in the first place.

Banner language matters more than most teams assume. The ICO expects plain-language purposes, not “we use cookies to enhance your experience,” and it expects a genuine opt-in action rather than a pre-selected default. A link to full settings should sit next to the accept and reject options, not several menus deep.

The pitfalls that keep coming up:

  • Assuming the CMP’s default expiry (often 90 days) is fine without checking whether it’s actually justified for your use case.
  • Leaning on browser-level signals like Global Privacy Control as a substitute for your own consent mechanism, rather than a supplement to it.
  • Listing “third parties” generically instead of naming the actual advertising or analytics vendors receiving data.

The ICO’s own guidance suggests treating six months as a reasonable point to seek fresh consent in many cases, rather than letting a CMP’s factory setting decide for you.

A practical checklist for marketing websites

For a typical marketing stack running Google Analytics, a tag manager, and one or two ad pixels, the sequence is always the same six steps: audit, classify, banner, block, record, review.

  • Audit what’s actually firing on the site today.
  • Classify each cookie as strictly necessary, exempt, or consent-required.
  • Build a banner with genuine accept/reject parity and a settings link.
  • Block every consent-required tag until opt-in.
  • Record consent decisions with a timestamp and version reference.
  • Review retention periods and vendor lists at least twice a year.

Clear cookie notices don’t just reduce enforcement risk. They also tell visitors you take their data seriously, which tends to translate into more trust further down the customer journey.

Most cookie consent guidance treats this as a legal box-ticking exercise: get a banner, get a policy, move on. That’s backwards. The organisations that get into trouble with the ICO aren’t usually the ones with no banner. They’re the ones with a banner that looks compliant but blocks nothing, or that quietly re-fires advertising tags after a user has rejected them.

Why most cookie compliance advice misses the point — overview diagram

The conventional advice also underplays how consent interacts with personalisation. Marketing teams often see consent as a compliance layer bolted onto a separate marketing strategy, when in reality the two are the same decision. Every category you ask permission for is a category your testing and measurement strategy depends on. Get the consent architecture wrong and your analytics data becomes unreliable long before a regulator ever notices.

If there’s one priority above all others, it’s this: fix the blocking before you fix the wording. A beautifully worded banner sitting on top of tags that fire regardless is worse than no banner at all, because it creates a false paper trail of “compliant” consent that a regulator can pull apart in minutes.

— Calum

Michaelbell is the alternative to building this in-house piecemeal: instead of a marketing team learning PECR case law while also running campaigns, our team handles the cookie audit, CMP configuration, and privacy copy as part of a joined-up communications strategy, not a bolt-on compliance task.

Michaelbell

We treat consent architecture as part of the same job as your customer journey and campaign planning, because the two are genuinely inseparable. DIY consent setups tend to fix the banner and forget the vendor contracts, the retention justification, and the ongoing review that keeps everything defensible six months later. An agency-led approach gives you integration testing, governance that doesn’t lapse when the person who set it up moves on, and a marketing-aligned consent strategy that protects your analytics rather than breaking it.

If your cookie setup needs an honest audit or your consent flow needs rebuilding properly, get in touch through our services page and we’ll get straight back to you.

Sources