Do affiliate cookies need consent? In the EU and the UK, generally yes. Cookies, pixels and similar technologies used to record which affiliate sent a visitor and to attribute a sale aren't "strictly necessary" for a service the visitor asked for, so the ePrivacy Directive and PECR require opt-in consent before they are set or read. The UK's new 2026 exemptions for statistics and site appearance don't cover them, and the ICO's April 2026 guidance specifically uses affiliate tracking pixels as an example that needs consent.

That doesn't mean affiliate marketing stops working in Europe. It means consent has to be collected in the right places, by the right party, and that attribution increasingly relies on methods that don't depend on tracking people who said no.

General information, not legal advice.

Why affiliate cookies aren't strictly necessary

The strictly necessary exemption covers storage or access that is essential to provide a service the user has explicitly requested: a login, a shopping basket, security or load balancing. The UK's new PECR Schedule A1 lists examples such as fraud prevention, fault detection and remembering what a user entered.

Affiliate tracking exists so that a publisher gets paid and a merchant can measure its marketing. The visitor gets nothing from it they asked for. The ICO's updated storage and access technologies guidance stresses that strict necessity is judged from the user's point of view and that funding a service isn't enough. EU regulators have taken the same line for years.

Not "statistical" either. The UK statistical exemption covers statistics to improve your own service, shared only with someone helping you do that. Attributing a sale to a publisher so that commission can be paid is a commercial purpose involving a third party, so it falls outside the exemption.

A typical journey has three stages. Each involves different parties and different rules.

StageWhat happensWhose consent banner?
1. On the publisher's pageVisitor reads a review; scripts, pixels or redirect cookies may loadPublisher's, for anything set or read on the publisher's site
2. The click and redirectLink passes through a network or tracking domain, which may set a cookie and append a click IDThe network's domain sets it; in practice the network relies on consent collected downstream, which is a known weak spot
3. On the merchant's siteMerchant stores the click ID (cookie or server-side) and reports the conversionMerchant's

The EDPB's Guidelines 2/2023 confirm that the ePrivacy rule covers URL-based tracking and pixels, not only cookies, so moving the identifier into the URL doesn't remove the question. It changes who stores it and where. For a refresher on the mechanics, see how affiliate cookies work.

Affiliate cookie consent in the EU vs the UK

EU / EEAUK
Consent needed for affiliate cookies and pixels?YesYes
2026 changesNone in force; Digital Omnibus proposals onlyStatistical and appearance exemptions, which don't cover affiliate tracking
Regulator stanceConsent for marketing and attribution trackersICO guidance names affiliate pixels as needing consent
Maximum penaltySet nationally; GDPR fines where personal data is misused£17.5m or 4% of worldwide turnover under PECR

The ICO has said it is examining whether some low-risk advertising measurement might be exempted in future, which would require new regulations. Don't build on that until it happens.

What publishers should do

  1. Find out what your pages set. Plain affiliate links set nothing on your site. Network banner scripts, smartlinks, on-page pixels and your own redirect scripts often do.
  2. Gate anything that tracks. Put network scripts and pixels in your CMP's advertising or marketing category so they load only after consent. Don't mark them "necessary".
  3. Keep your redirect clean. A self-hosted redirect that just appends a random sub-ID and forwards the visitor is low risk. One that sets a long-lived visitor cookie needs consent.
  4. Never put personal data in sub-IDs. Use random references, not emails, usernames or anything identifying.
  5. Explain it. Your banner and privacy notice should say plainly that you earn commission and that partners record clicks.
  6. Ask your programs how they handle consent on their side and whether they support server-to-server tracking.

Your roles matter too: networks are usually independent controllers of the tracking data, not your processors. See controller vs processor roles for affiliates.

A first-party affiliate cookie is set on the merchant's own domain rather than the network's. It survives browser restrictions on third-party cookies far better, but it is still a cookie for marketing attribution, so it still needs consent. "First-party" is a technical term, not a legal exemption.

Server-to-server (S2S) tracking moves the conversion report off the browser: the merchant stores the click ID server-side and posts the conversion back to the network. This reduces reliance on cookies and is more robust, but if the click ID is stored in the browser to begin with, or combined with identifiers, consent questions remain. Our guides on S2S vs pixel tracking and whether server-side tracking is GDPR compliant go into the detail.

The impact on attribution

When visitors reject tracking, some sales go unattributed. How many depends on the audience, the banner design and the merchant's setup. A hypothetical illustration: if 40% of a merchant's EU visitors reject marketing cookies and the merchant tracks only with consented cookies, a publisher could see a substantial share of genuine referrals go uncredited. Programs that combine consented tracking with server-side click-ID matching, where they have a lawful basis to do so, typically lose less.

What you can do:

  • Compare your click logs with reported conversions by program and flag big gaps.
  • Favour programs with transparent consent handling and S2S postbacks; ask about it when you negotiate.
  • Diversify towards deals less sensitive to attribution loss, such as flat fees or hybrid deals with a guaranteed element.

Compare tracking platforms and their approaches in our affiliate tracking platforms directory.

Frequently asked questions

Can affiliate cookies be classed as strictly necessary?

No. Regulators in the EU and UK treat attribution and commission tracking as serving the publisher and merchant, not a service the visitor requested. Labelling them necessary to avoid consent is a common and risky mistake.

If I only use plain affiliate links, do I need a cookie banner?

Not for the links themselves, if nothing is set or read on your site. You may still need one for analytics, ads or embeds. The network and merchant need consent for tracking on their domains.

Do the UK's 2026 cookie exemptions cover affiliate tracking?

No. They cover statistics used to improve your own site and appearance preferences. Affiliate tracking and advertising still need consent.

Next steps

Run a quick audit of what your pages set before consent and move any affiliate scripts behind your banner. For the full compliance picture, read our pillar guide to GDPR for affiliate websites, and browse more in our GDPR and cookies section.