Cookie Consent Management

Cookie Consent Management

A regulator's sweep finds six tracking cookies firing before anyone agreed to anything, and a banner with no way to refuse. Correct the inventory, rebuild the banner, and re-crawl the site to see what a supervisory authority would now find.

What Is Cookie Consent Management?

Cookie banners are the most visible privacy control on the internet and among the most commonly misconfigured. This exercise puts a learner in the operations seat at a digital publisher after a supervisory authority sweep reports that six non-essential cookies were set before any consent was given, and that the banner offers no way to refuse. The work is concrete. A crawl lists twelve cookies with the moment each was written, and two of them wear a strictly necessary label they have not earned, which is the single most common cookie compliance error there is. Three uncategorised cookies have to be filed correctly, because the banner switches whole categories on and off based on those labels. The banner itself has three defects: implied consent wording, a single Accept all button with refusal buried behind a preferences panel, and optional categories switched on by default. The learner rebuilds it, publishes the change with a documented reason, and re-crawls the live site. One tag survives: a video player embedded directly in the article template, which the browser fetches before the consent script can hold anything, and which needs a different fix entirely.

What You'll Learn in Cookie Consent Management

Cookie Consent Management — Training Steps

  1. Introduction

    Today you will work through cookie consent: which cookies a website may set before anyone agrees to anything, how the four categories differ, and what turns a consent banner from a legal notice into a legal problem. The rules here come from two places at once. The ePrivacy Directive governs storing or reading anything on someone's device, and the GDPR governs what counts as valid consent.

  2. The Regulator's Enquiry

    Alice opens her inbox to find a message from Helena Ruzicka, the Data Protection Officer. A supervisory authority sweep has flagged the Brackwell Media website. The letter is specific about what the automated check found.

  3. Opening the Consent Platform

    Helena's email links straight to the consent management platform, where the fresh scan is waiting.

  4. Signing In

    The consent platform holds the cookie inventory, the banner configuration and the consent log for every Brackwell Media property.

  5. Reading the Scan

    The scan lists twelve cookies set by the Brackwell Media homepage, with the moment each one is written and who writes it. Alice starts with the two columns the regulator's crawler was reading.

  6. The Strictly Necessary Myth

    Three cookies are correctly marked strictly necessary: the sign-in session, the CSRF token, and the cookie that stores the consent choice itself. Two more are marked strictly necessary and should not be. This is the most common cookie compliance error there is.

  7. Which One Is Necessary

    Before Alice recategorises anything, she checks her own understanding of where the line sits.

  8. Correcting the Categories

    Alice works down the uncategorised rows. Each cookie has to sit in the category that matches what it actually does, because the banner will switch whole categories on and off based on these labels. Getting a marketing cookie filed as functional means it will fire for someone who refused marketing.

  9. The Banner as It Stands

    With the inventory corrected, Alice opens the banner configuration. The live banner is shown exactly as a visitor sees it. This is the design the regulator called out.

  10. Making Refusal Real

    Alice has seen the three defects. Before she changes the configuration, she thinks through what a compliant banner actually has to offer.