Can I track my ads and still follow GDPR?
Which rules apply to ad tracking?
Two sets of EU rules, plus the ad platforms' own terms. They overlap, which is why the topic feels confusing.
| Rule | What it covers | What it means for your ads |
|---|---|---|
| ePrivacy Directive, Article 5(3), and each country's cookie law | Storing or reading anything on the visitor's device: cookies, pixels, tracking links | Consent before the tag runs, unless it is strictly needed for the service the visitor asked for |
| GDPR | Any personal data: email, phone, IP address, customer ID, hashed or not | A legal basis, clear information, contracts with your tools |
| Meta and Google terms | Data you send through their pixels, tags and APIs | You must collect consent where it is required and pass it on |
The European Data Protection Board says Article 5(3) applies to tracking pixels and to links carrying an identifier, not only to cookies (EDPB Guidelines 2/2023). The consent must be active: the Court of Justice ruled that a pre-ticked checkbox is not enough (CJEU, Planet49).
You also share responsibility. When a store embeds a Facebook tool, it can be a joint controller with Meta for collecting the data and sending it to Meta, though not for what Meta does afterwards (CJEU, Fashion ID).
Which legal basis fits ad tracking?
GDPR gives six legal grounds, including consent, contract and legitimate interests (European Commission). For ad tracking, consent is the one that holds up in practice. The cookie rule asks for consent before the pixel runs, and the platforms ask for it too. Meta's terms require you to get it wherever the law asks for consent to cookies (Meta Business Tools Terms). Google's EU user consent policy requires consent for ad personalization from visitors in the EEA, the UK and Switzerland (Google).
Your order data is a different case. You need it to deliver the order. Sending the same buyer's details to Meta to improve your ads is a separate purpose, and the Commission notes that consent for one purpose cannot be reused for another.
Does server-side tracking get around consent?
No. It changes where the data flows, not the rules for collecting it. For how the two methods work, see server-side vs pixel tracking.
| Changes | Does not change |
|---|---|
| Data passes through your server first, so you decide which fields go to Meta or Google | Reading the click ID or setting a tracking cookie still needs consent |
| Ad blockers and Safari's script cookie limits stop fewer events | Data sent through the Conversions API falls under the same Meta terms as the pixel |
| You can hold back events for visitors who said no | A hashed email is still personal data, because Meta hashes it in order to match it to a person |
On the last point: the EDPB says pseudonymised data that can be linked back to a person with extra information remains personal data (EDPB, January 2025).
What happens when it goes wrong?
Sweden's data protection authority, IMY, fined Apoteket SEK 37 million and Apohem SEK 8 million on 30 August 2024. Both had switched on a new sub-feature of the Meta pixel, which then sent data about customers' purchases of non-prescription medicines and self-tests to Meta (IMY). Meta's own terms forbid sending health or financial information, or data about children under 13. The lesson for any store: check what your pixel sends every time you turn on a new feature.
How do I set up tracking that follows the rules?
- Block ad tags until the visitor says yes, with "reject" as easy as "accept". Shopify's cookie banner controls Shopify's own pixels; other tools need to read Shopify's consent signal (Shopify Help).
- Pass the choice to Google with consent mode, including the ad_user_data and ad_personalization signals (Google).
- Send server events only for visitors who agreed, and only the fields you need.
- Sign processing terms with every tool that handles your customers' data, and name them in your privacy policy.
- Audit your tags every quarter and after every new app. See how to check your tracking setup for privacy problems.
How do I judge my ads when people say no?
Count sales in your own store. Your orders are complete whatever the banner says, while browser tools see only part of them. In 16 stores using TrueROAS, GA4 recorded a median 76% of real orders from 5 October to 1 November 2026, with declined consent as one of the causes. TrueROAS respects the consent your store collects and matches orders to ads where it can, while your order totals stay complete. For the size of the loss by market, see ad blockers, consent and cookies.
Will the rules change?
Possibly. On 19 November 2025 the European Commission proposed changes meant to show cookie banners less often, allow one-click consent and save choices in browser settings (European Commission). Until a change is adopted and in force, today's rules apply. Build your setup so the consent signal decides what fires, and a rule change becomes a settings change.

