Cookie consent and analytics for ecommerce websites: what the rules require

How ePrivacy, the GDPR, Planet49, EDPB and CNIL guidance and the UK's 2026 PECR changes apply to cookie banners, analytics and Google Consent Mode.

Key points

  • Article 5(3) of the ePrivacy Directive requires consent before storing or reading information on a visitor's device unless it is strictly necessary for a service they requested.
  • Since Planet49 (2019), pre-ticked boxes are not valid consent, and visitors must be told how long cookies last and whether third parties can access them.
  • Rejecting should be as easy as accepting; regulators treat hidden or visually downplayed reject options as deceptive design.
  • Google Consent Mode communicates consent choices to Google tags; it does not collect consent, and its advanced mode still sends cookieless pings.
  • Since 5 February 2026 UK law allows some first-party analytics without consent if visitors are informed and can object; EU rules have no equivalent general exemption yet.

Cookie banners are the most visible piece of privacy compliance on any online shop, and among the most frequently got wrong. The rules behind them are not complicated, but they come from two overlapping regimes, have been refined by courts and regulators, and changed materially in the UK in 2026. This guide explains what applies to an ecommerce site as of November 2026, how analytics fits in, and where tools such as Google Consent Mode help and where they do not.

The legal basis: ePrivacy Article 5(3), not just the GDPR

The consent requirement for cookies comes from Article 5(3) of the ePrivacy Directive, as implemented in each member state’s national law. It applies to storing information, or gaining access to information already stored, in a user’s terminal equipment. Consent is required unless the storage or access is for the sole purpose of carrying out a communication, or is strictly necessary to provide a service the user has explicitly requested.

Two features are often misunderstood. First, Article 5(3) applies whether or not the information is personal data. Second, it is not limited to cookies. The EDPB’s Guidelines 2/2023, finalised in October 2024, take the view that tracking pixels, tracking links, local storage, device fingerprinting and certain uses of scripts that instruct the browser to send information all fall within its scope.

The GDPR then supplies the definition and standard of consent, and governs whatever processing of personal data follows. The EDPB’s consent guidelines set out what that standard means: freely given, specific, informed and unambiguous, given by a clear affirmative act, and as easy to withdraw as to give. They also state that scrolling or continuing to browse is not consent.

Planet49: the ruling that set the baseline

In Planet49 (C-673/17), decided on 1 October 2019, the Court of Justice considered an online lottery that used a pre-ticked checkbox to obtain agreement to cookies. The Court held that consent given through a pre-ticked box which the user must untick to refuse is not valid consent under Article 5(3), and that this holds whether or not the information stored or accessed is personal data. It also held that the information given to users must include how long cookies will remain active and whether third parties can access them.

Practical consequences for a shop: no pre-selected toggles for non-essential categories, no “by using this site you agree” notices, and a cookie policy that lists durations and third-party recipients rather than generic categories.

What regulators expect from a banner

The EDPB’s Cookie Banner Taskforce report, adopted in January 2023, recorded the common positions of national authorities on practices raised in a wave of complaints. The report does not have the formal status of guidelines, but it is the clearest statement of what authorities consider problematic:

  • No reject option on the first layer. Most authorities considered that offering “accept all” on the first layer without an equivalent way to refuse breaches the rules.
  • Pre-ticked boxes on a second layer are not valid consent.
  • Deceptive link design, such as presenting refusal as a small text link within a paragraph while acceptance is a button.
  • Deceptive colours and contrast, assessed case by case, where the reject option is visually suppressed so that it is hard to see.
  • Claiming legitimate interest for non-essential cookies, or misclassifying tracking cookies as essential.
  • No easy way to withdraw consent afterwards, for example a persistent link or icon.

National authorities have enforced these points independently, and the EDPB’s guidance on deceptive design patterns reinforces the general principle that interface design must not push users towards the option that benefits the business.

Most analytics tools set or read identifiers on the device, so they fall within Article 5(3). Whether consent is required depends on whether an exemption applies.

The EU position and the CNIL approach

The ePrivacy Directive contains no explicit analytics exemption. Some national authorities interpret “strictly necessary” to cover narrowly configured audience measurement. The French CNIL is the most developed example. Its guidance on audience-measurement tools, updated in July 2025, allows exemption from consent only where the tracker is used solely to measure the site’s audience on behalf of the publisher, produces only anonymous statistical data, is not combined with other processing or passed to third parties in identifiable form, and does not enable tracking across sites or apps. The CNIL also recommends informing users, limiting cookie lifetime to about 13 months and retaining data for no more than 25 months.

The CNIL notes that some widely used market tools fall outside the exemption where the provider reuses data for its own purposes, and it provides a self-assessment tool for vendors. A vendor’s self-assessment is not a CNIL certification; the site operator remains responsible for its own configuration. The CNIL’s approach is persuasive in France and is often cited elsewhere, but other authorities may take a stricter line. Our comparison of ecommerce analytics tools discusses how different tools can be configured.

The UK after the Data (Use and Access) Act 2025

The UK has moved further. The Data (Use and Access) Act 2025 inserted a new Schedule A1 into PECR, in force since 5 February 2026. It allows storage or access without consent where the sole purpose is to collect statistical information about how a service or website is used with a view to improving it, provided the information is not shared except with someone helping make those improvements, the user is given clear and comprehensive information, and the user has a simple, free means of objecting and does not object. A similar exception covers adapting a website’s appearance or functionality to user preferences.

The conditions are cumulative and the purpose must be sole: an analytics tag that also feeds advertising audiences does not qualify. The ICO published final guidance on storage and access technologies in April 2026. The same Act raised the maximum PECR penalty to the UK GDPR level of £17.5 million or 4% of global turnover. For a UK shop with EU customers, the EU rules still apply to those visitors.

Google Consent Mode is a mechanism for passing a visitor’s consent choices to Google tags. It recognises four main signals: ad_storage and analytics_storage (whether advertising and analytics cookies may be used), and ad_user_data and ad_personalization (whether user data may be sent to Google for advertising, and whether it may be used for personalised advertising). Google’s documentation is explicit that Consent Mode does not collect consent; the site operator remains responsible for obtaining it, through its own banner or a consent management platform.

Google describes two implementations. In basic mode, Google tags do not load until the visitor interacts with the banner, and nothing is sent to Google if consent is refused. In advanced mode, tags load immediately with consent set to denied by default and, while consent is denied, send cookieless pings containing functional information such as a timestamp, user agent and referrer, along with aggregate signals. Google uses these to model conversions and other metrics.

In our assessment, advanced mode needs careful legal review in the EU. Even without cookies, a script that runs before consent and instructs the browser to send information may engage Article 5(3) under the EDPB’s 2/2023 reading, and the pings still involve processing that must be disclosed and justified under the GDPR. Basic mode is the more conservative choice; advanced mode trades legal certainty for measurement coverage.

Server-side tagging: useful, but not an exemption

Server-side tagging moves tag execution from the visitor’s browser to a server the merchant controls, which then forwards selected data to analytics and advertising vendors. It can improve page performance and gives the merchant more control over what each vendor receives, for example by stripping IP addresses before forwarding.

It does not remove the consent requirement. If a first-party cookie is still set or read on the device, or a browser script still collects device information, Article 5(3) applies as before. And forwarding data from your server to an advertising platform is a disclosure under the GDPR that needs a lawful basis and must appear in your privacy notice. In our view, the main risk with server-side setups is opacity: because data flows are no longer visible in the browser, it is easier for a site to drift into sending data that visitors refused. Gate server-side forwarding on the same consent state as client-side tags, and document it.

Reform: what may change

The Commission’s Digital Omnibus proposal of November 2025 would move the cookie rules for personal data into the GDPR, add limited exemptions for low-risk purposes such as aggregated audience measurement, and support machine-readable consent signals from browsers. The Council agreed its negotiating position on 21 October 2026; according to published reports, it keeps the cookie rules in the ePrivacy framework and shortens the period before a site may ask again after a refusal. Negotiations with the European Parliament continue, and the final shape is uncertain. Nothing in the current law changes until a text is adopted and applies.

Practical banner checklist

  1. Inventory every cookie, pixel, SDK and script, with purpose, duration and recipient. Repeat after every new app or plugin.
  2. Block before consent. No non-essential tag, pixel or server-side forward fires until the visitor opts in.
  3. Equal choices on the first layer: “Accept all” and “Reject all” with the same prominence, plus a route to granular settings.
  4. No pre-ticked categories and no “continue browsing means consent”.
  5. Specific information: purposes, durations and third parties, in line with Planet49.
  6. Easy withdrawal through a persistent link or icon, effective immediately.
  7. Record consent with timestamp, banner version and choices.
  8. Map analytics to the right rule for each market: consent in most EU states, the CNIL exemption only if your configuration meets it, and the PECR statistical exception in the UK only with notice and an objection route.
  9. Configure Consent Mode deliberately, choosing basic or advanced with a documented rationale.
  10. Test in a clean browser profile: refuse everything and check network requests.

Bottom line

A compliant banner costs some measurement data, and that trade-off is real for shops that rely on analytics to improve conversion. But the rules are now settled enough that the main risks come from implementation errors, not legal uncertainty. Configure for the strictest market you serve, document your choices, and treat the banner as part of your wider GDPR obligations rather than a stand-alone widget.

This article is general information, not legal advice; for decisions about your business, consult a qualified adviser.

Sources and further reading

  1. Directive 2002/58/EC (ePrivacy Directive) — EUR-Lex
  2. Judgment of the Court in Case C-673/17, Planet49 — EUR-Lex
  3. Guidelines 05/2020 on consent under Regulation 2016/679 — European Data Protection Board
  4. Report of the work undertaken by the Cookie Banner Taskforce — European Data Protection Board
  5. Guidelines 2/2023 on Technical Scope of Art. 5(3) of ePrivacy Directive (version 2.0) — European Data Protection Board
  6. Cookies : solutions pour les outils de mesure d'audience — CNIL
  7. The Privacy and Electronic Communications (EC Directive) Regulations 2003, Schedule A1 — legislation.gov.uk
  8. Consent mode overview — Google for Developers