"Accept cookies or pay to read" has spread from newspapers to recipe sites and forums. In January 2025 the ICO said the model can be lawful in the UK, with conditions. What those conditions are, what they don't cover, and what a site running one should do with GA4.

What the ICO said.

The ICO's guidance, published on 23 January 2025, says a consent or pay model can comply with UK law if people have a genuine choice. It asks the organisation to assess, and write down, four things:

  1. Power imbalance. If people rely on the service and would lose out by refusing, consent is unlikely to be freely given. A dominant platform is in a different position from a hobby site.
  2. An appropriate fee. The price of the ad-free option has to be reasonable, not set so high that it's a sham.
  3. Equivalence. The paid version should be the same service, not a worse one.
  4. Privacy by design. The consent side should still collect only what's needed for personalised advertising, with everything else off.

The ICO now marks this guidance as under review, because of the changes made by the Data (Use and Access) Act, so it may change. No new version had been published when this was last checked.

The model is about personalised advertising. It's not a licence to track. Under PECR, non-essential cookies still need consent, and the paying visitor hasn't given it.

The ICO's wider position on cookies hasn't softened: the same day, it announced a review of the UK's 1,000 busiest websites. By December 2025, 979 of them passed its checks, and by August 2026 the ICO reported 992, or 99%, after letters, investigations and 17 preliminary enforcement notices.

What it means for GA4.

A consent or pay site has three kinds of visitor, and each needs a different tracking state.

  • Consented. GA4, Google Ads, Consent Mode v2 set to granted, and whatever ad tech the site runs. The normal case.
  • Paying. No personalised advertising, and no consent for non-essential cookies either. GA4 may only run if the visitor is asked separately and says yes, or if the use fits a PECR exception. The Data (Use and Access) Act 2025 added exceptions for some low-risk purposes, discussed in GA4 after the Data (Use and Access) Act, and whether a GA4 setup fits one depends on how it's configured. Nobody should assume.
  • Neither yet. Before the choice, nothing non-essential loads. The banner isn't a loading screen.

In practice that means the subscription state has to reach Tag Manager, usually as a dataLayer variable set on login, and the consent manager has to know about it. A site that fires the same tags for subscribers and consenters has built the easy half of the model.

The EU is stricter.

In April 2024 the European Data Protection Board said that very large platforms should normally offer a free alternative without behavioural advertising, not just a choice between paying and consenting.

That opinion is about the largest platforms, but EU regulators have been cooler on the model than the ICO, and a UK site with EU readers should expect the stricter reading to apply to them. See GA4 and EU consent rules.

What to check.

  1. Log in as a subscriber and watch the network requests. Only essential requests, and anything the subscriber separately agreed to, should go out.
  2. Decline to pay and decline consent. Does the site still work, and does anything load?
  3. Check that the consent and subscription states both reach Tag Manager, and that Consent Mode reflects them
  4. Read the written assessment. If there isn't one, that's the first job.

The free tracking checker shows what a page loads before anyone chooses. Marc Alexander sets up Consent Mode v2 and GA4 for UK publishers and other businesses, and the guide to GA4 and UK GDPR covers the rest of the rules.

Sources.

Checked on 13 November 2026.