Marketers want as much tracking data as possible. Privacy law sets limits on how it can be collected. Getting consent right is not just a legal box to tick; it shapes how much data reaches ad platforms and how campaigns are measured. This guide is general information, not legal advice, so check your own setup with a qualified adviser where needed.
The rules that apply
| Law | What it covers |
|---|---|
| PECR | Storing or accessing information on devices, including cookies and pixels |
| UK GDPR | Processing personal data, including data collected through tracking |
| Data Protection Act 2018 | UK framework alongside UK GDPR |
The ICO regulates both and publishes guidance on cookies and similar technologies. The Academy's glossary explains PECR, GDPR and the ICO.
Why ad pixels need consent
PECR requires consent before storing or accessing information on a device unless it is strictly necessary for a service the user requested. Advertising and cross-site tracking are not strictly necessary, so ad pixels and advertising cookies generally need opt-in consent before they fire.
What valid consent looks like
- Freely given: refusing must be as easy as accepting.
- Specific: separate choices for different purposes, such as analytics and advertising.
- Informed: clear explanation of what is tracked and by whom.
- Unambiguous: an active choice, not pre-ticked boxes or scrolling.
- Before tracking: pixels should not fire until consent is given.
Good cookie banner practice
- Offer accept and reject options with equal prominence on the first layer.
- Group cookies by purpose and let people choose.
- Explain each purpose in plain language.
- Name the third parties involved, such as Meta and TikTok.
- Let people change their choice easily later.
- Record consent choices.
Making pixels respect consent
Configure your tag manager or website platform so advertising tags only fire after consent. Many consent management platforms integrate with tag managers to block tags by default. Test by rejecting cookies and checking that no advertising requests are sent. Browser developer tools show network requests, so you can confirm that calls to Meta, TikTok or LinkedIn only appear after you accept.
Consent modes
Some platforms offer modes that adjust tracking based on consent signals, sending limited or no identifiers when consent is refused. These can help, but they do not remove the need for a compliant banner, and any data processing must still have a lawful basis.
Server-side tracking and consent
Server-side tools such as the Conversions API do not avoid consent requirements. If they use personal data about visitors who refused tracking, that may still be unlawful. Pass consent status through to server-side events and send data only for people who agreed. The Academy's guide to the Conversions API explains setup.
Customer lists and custom audiences
Uploading customer emails to create custom audiences is processing personal data. You need a lawful basis, a clear privacy notice and proper handling. The Academy's guide to custom audience GDPR explains what to check.
Impact on measurement
When people refuse tracking, platforms see fewer conversions, and reported results fall below real results. Expect a gap between ad platform figures and your own sales data, and explain it in reports. Use UTM tags, first-party analytics with appropriate consent and modelled measurement to fill the picture. The Academy's guide to UTM tracking helps.
Enforcement
The ICO has warned many websites about non-compliant cookie banners and has made cookie compliance a stated priority. Beyond fines, poor practice damages trust with customers who expect honest handling of their data.
Platform behaviour and consent
Platforms optimise on the data they receive. With fewer tracked events, systems rely more on modelling and broader signals. Meta's documented organic feed signals are meaningful interactions (comments, shares), watch time, relationship closeness, content type preferences✓, while ad optimisation leans on conversion data; less data can mean slower learning, so clean consented data becomes more valuable.
Who is responsible
The website owner is responsible for the cookies and pixels on their site, even when an agency or developer installed them. If an agency runs your ads, agree in writing who maintains the consent setup and how changes are checked. Platforms also require advertisers to confirm they have the necessary consents in their terms, so responsibility cannot be passed back to Meta or TikTok.
A practical checklist
| Check | Done? |
|---|---|
| Banner offers equal accept and reject options | |
| Advertising tags blocked until consent | |
| Purposes and third parties explained | |
| Consent recorded and changeable | |
| Server-side events respect consent status | |
| Privacy notice covers ad tracking and custom audiences | |
| Setup tested after every website change |
A worked example
A clothing retailer's banner only offered an accept button, and the Meta Pixel fired on page load. After a review, it adds a reject button of equal prominence, groups cookies by purpose and configures its tag manager to block advertising tags until consent. Reported conversions in Meta fall slightly, but the retailer's measurement is now lawful and its own sales data, combined with UTM tracking, shows campaigns are still profitable.
Common mistakes
- Firing pixels before consent.
- Banners with no reject option or a hidden one.
- Assuming server-side tracking avoids consent rules.
- No privacy notice covering advertising.
- Never testing the consent setup.
Learning the rules
The Academy's legal and ethical module in the third level covers data protection, PECR and advertising rules, and the paid social module covers tracking setup. The free assessment shows where you would start.
