Journal · Markets and the law

Cookies, consent and ads in Europe: what a small firm has to do

In the EU, your site may not set advertising cookies or fire a Meta or Google pixel until the visitor agrees, and rejecting must be as easy as accepting. Google requires consent signals from EEA visitors for ad measurement and personalisation, and Spain's regulator, the AEPD, fines sites that load trackers before the click.

Written by
Last updated
Reading time
10 minutes
In this guide10 sections
  1. Two laws decide when a tag may fire
  2. What valid GDPR cookie consent looks like
  3. Google: the consent policy and Consent Mode v2
  4. Meta: the Pixel and the Conversions API
  5. What your reports lose, and what modelling gives back
  6. Cookieless analytics: when you still need consent
  7. The DSA rules that reach small advertisers
  8. Three Spanish cookie fines
  9. A 10-step check before you run ads
  10. Sources

An ad click lands on your site, and the Meta Pixel and the Google tag want to fire at once. In the EU they may not, until the visitor agrees. This guide is for a small interior studio, architect or reformas company in Spain; the rules apply EU-wide. It covers the laws, a valid banner, Google, Meta, measurement, the Digital Services Act and three Spanish fines, then a 10-step check. This is information, not legal advice: for your own site, ask a data protection lawyer. When I run ads for a firm, they run in its own ad account, paid with its own card, with stop rules agreed before the first euro.

Two laws decide when a tag may fire

First, the ePrivacy Directive. Article 5(3) allows storing or reading information on a visitor’s device only if they have “given his or her consent”, after “clear and comprehensive information” (EUR-Lex, Directive 2002/58/EC). The exception is storage “strictly necessary” for a service the visitor asked for. A quote form’s session cookie qualifies; an ad pixel does not.

Spain wrote the rule into article 22.2 of its e-commerce law, the LSSI. Breaking it is a minor infringement under article 38.4 g), fined up to EUR 30,000. A repeat within three years becomes serious: EUR 30,001 to 150,000 (BOE, Ley 34/2002).

The second law is the GDPR. Consent must be “freely given, specific, informed and unambiguous”, given “by a statement or by a clear affirmative action”. Article 7(3) adds: “It shall be as easy to withdraw as to give consent” (EUR-Lex, GDPR). Breaching consent conditions can cost up to EUR 20 million or 4% of worldwide turnover, whichever is higher.

On 7 October 2024 the EDPB, the board of the EU’s data protection authorities, adopted guidelines on Article 5(3). A tracking pixel triggers it “even if this storage is not permanent”. The script that builds a pixel counts as “gaining access”, and fingerprinting is covered too (EDPB Guidelines 2/2023). A tool sold as “cookieless” is not automatically outside the rule.

The EDPB’s guidelines settle three points (EDPB Guidelines 05/2020):

  • Scrolling or swiping “will not under any circumstances” count as consent.
  • “The use of pre-ticked opt-in boxes is invalid under the GDPR.”
  • Hiding the content until someone clicks “Accept”, a cookie wall, means consent is not freely given.

In January 2023 the EDPB’s cookie banner taskforce reported that “a vast majority of authorities” treat a banner with no reject option on any layer that has an accept button as an infringement. Colours and contrast that push the accept button are judged case by case, and fail when “obviously misleading” (EDPB taskforce report, 17 Jan 2023).

Spain’s regulator, the AEPD, updated its cookie guide in July 2023 to follow the EDPB on deceptive design, with 11 January 2024 as the deadline (Cuatrecasas, 11 Jan 2024). The current edition, dated May 2024, says the first layer must carry three controls (AEPD, Guía sobre el uso de las cookies):

  1. An “Aceptar” button or equivalent, easy to see.
  2. A “Rechazar” control “similar al anterior”: if accepting is a button, rejecting is a button too.
  3. A “Configurar” control that opens a panel to choose cookies at least by purpose.

Withdrawing must be “tan fácil como” consenting, for example through settings that are always reachable. As good practice, a consent should last no more than 24 months.

On the bannerValid in SpainNot valid
First layerAccept, Reject, ConfigureAccept and “Settings” only
RejectThe same kind of control as AcceptA small grey link
Before any clickStrictly necessary cookies onlyAnalytics or a pixel already loaded
Changing your mindA “Cookie settings” link on every pageNo way back once accepted

Google’s EU user consent policy covers visitors in the EEA, the UK and Switzerland. You “must obtain end users’ legally valid consent” to cookies where the law requires it, and to “the collection, sharing, and use of personal data for personalization of ads”. You must “retain records of consent” and explain how to revoke it (Google, EU user consent policy).

For EEA visitors, Google says that to keep using its tags “for measurement, and for ad personalization, and remarketing features”, you “must collect consent” and “share consent signals with Google” (Google Ads Help, EEA changes). Its consent-mode page says advertisers “need to send verifiable consent signal(s)”, and that action may be needed “to preserve ads personalization features before March 2024” (Google Ads Help, consent mode).

Consent Mode passes the visitor’s choice to Google’s tags. Version 2 carries four signals (Tag Manager Help):

SignalCoversWhen denied
ad_storageAdvertising cookiesNo new ad cookies are written
analytics_storageAnalytics cookiesNo analytics cookies read or written
ad_user_dataSending user data to Google for adsPersonal data for ads is switched off
ad_personalizationPersonalised ads and remarketingRemarketing stops receiving data

Personalised ads need both ad_user_data and ad_personalization granted.

There are two set-ups (Google Ads Help, About consent mode). In basic mode, tags wait for the banner, and if the visitor declines “no data is transferred to Google at all”. In advanced mode, tags load at once and send cookieless pings while consent is denied, and the default is “a consented state” unless you set it. Given how widely the EDPB reads Article 5(3), basic mode is the cautious choice in Spain.

Meta: the Pixel and the Conversions API

Meta’s Business Tools Terms, effective 3 November 2025, say that where informed consent is required, “such as but not limited to the European Union”, you “must ensure, in a verifiable manner” that the visitor gives “all necessary consents” first (Meta Business Tools Terms).

On the Pixel, call fbq(‘consent’, ‘revoke’) before the Pixel starts, on every page, then fbq(‘consent’, ‘grant’) once “affirmative consent” is given (Meta for Developers, GDPR). Test that your consent platform does this.

The Conversions API sends events from your server, not the browser. It is no way round the banner. Meta’s guide: “If you have logic for controlling consent with respect to sharing Pixel data, use the same logic” for the Conversions API (Meta for Developers, Conversions API).

The same terms bar sending Meta data that includes “health information” or “other categories of sensitive information”. A reformas enquiry might read “a walk-in shower for my father after his stroke”. Send the fact that a form was sent, never what it said.

What your reports lose, and what modelling gives back

When a visitor rejects, no ad cookie links their enquiry to the click. Google fills part of the gap with modelled conversions, shown in the “Conversions” column. To model, Google Ads needs “700 ad clicks over a 7 day period, per country and domain grouping” (Google Ads Help, consent mode modeling). Google Analytics 4 needs 1,000 events a day from visitors who declined, for 7 days, and 1,000 daily users who accepted on 7 of the last 28 days (Analytics Help).

Take a reformas company in Valencia spending EUR 20 a day on search ads. 700 clicks a week is 100 a day, which would need a cost per click of EUR 0.20. Most small accounts will see consented conversions only. So count enquiries where they arrive: the form inbox, WhatsApp and the phone, each with the source the client names. Then judge a campaign on cost per real enquiry over several weeks (how to read an ads report).

Meta has a second gap. In April 2025 the European Commission found Meta in breach of the Digital Markets Act over user choice. On 8 December 2025 it announced that Meta would offer EU users, from January 2026, fully personalised ads or “more limited personalised advertising” (European Commission). Meta’s October 2026 quarterly report says it launched less personalised ads in November 2024, has made “significant modifications” since, and is appealing. It calls them “less relevant and effective” (Meta 10-Q, Q3 2026). You cannot opt out as an advertiser: part of your audience sees ads chosen on less data.

France shows the exemption at its widest. The CNIL lets audience-measurement cookies run without consent if their purpose is “strictement limitée” to measuring the site’s audience for the site alone. They must produce “données statistiques anonymes uniquement”, with no cross-referencing and no passing of data to third parties. The CNIL recommends a 13-month cookie life and 25 months’ retention (CNIL, 4 July 2025). Tools that reuse the data for their own purposes fall outside.

Spain sets conditions rather than a flat rule. The AEPD’s general guide does not list analytics among the exempt cookies: first-party, aggregated, statistical cookies are low risk, “although they are not exempt” (AEPD guide). But in January 2024 the AEPD published a separate guide on audience-measurement tools, which the general guide points to: such cookies “could be exempt from consent under certain conditions” (AEPD, January 2024). The conditions, in short: they measure only the site’s own audience, for the publisher alone, and produce anonymous statistics only; the data is not combined with anything else, not passed on and not used to follow anyone across sites; services that reuse the data for other purposes are out; visitors are told; the cookie lasts a limited time, such as 13 months, without renewing on each visit, and data is kept 25 months at most; and with a provider, a GDPR Article 28 contract forbids reuse. If your tool meets every condition, and you can show it, analytics can run before consent. If it misses one, it goes behind the banner.

The DSA rules that reach small advertisers

The Digital Services Act has applied since 17 February 2024. Its ad rules bind the platforms, and they shape what you can buy (EUR-Lex, DSA):

  • Labels (Article 26(1)). Each ad shows that it is an ad, on whose behalf it runs, who paid, and the main targeting parameters.
  • No sensitive-data targeting (Article 26(3)). No ads based on profiling with the GDPR’s special categories: health, religion, ethnic origin, political opinions, sexual orientation and the rest of Article 9(1).
  • No profiling ads to minors (Article 28(2)). Not where the platform knows “with reasonable certainty” the user is a minor.
  • A public ad archive (Article 39). Very large platforms keep each ad, its advertiser, payer, dates and targeting, until a year after it last ran. Anyone can read your audience settings.

In each case the AEPD loaded the site and listed what was set before any click.

CaseWhoWhat the AEPD foundFine
PS/00079/2023The owner of a one-person news site, after a visitor’s complaintGoogle Analytics cookies before consent; rejecting in the panel changed nothing; no way to withdrawEUR 2,000; paid EUR 1,600 on 2 July 2023
PS/00051/2023Grupo Massimo DuttiNo permanent way to withdraw consent, and «Rechazar todas» did not remove cookies already accepted (the vague purposes on the first layer were not held an infringement)EUR 5,000
PS/00284/2024SEAT, on the AEPD’s own initiativeNon-technical cookies before consent; no way to change the choice laterEUR 20,000 proposed; paid EUR 12,000

The AEPD takes 20% off for admitting responsibility and another 20% for paying early, which is how SEAT reached EUR 12,000. One complaint about a one-person site was enough in the first case. In all three the fix is the same: nothing loads before the click, and “Reject” works.

A 10-step check before you run ads

  1. List every tracker. Open the site in a private window, cookies cleared, and note each cookie and outside request before any click.
  2. Sort them. Strictly necessary (session, security, load balancing, language choice) against the rest.
  3. Pick a consent platform that sends Consent Mode v2. Google names CMP partners (Google Ads Help).
  4. Put Accept, Reject and Configure on the first layer. Same size, same style for Accept and Reject.
  5. Block before consent. Analytics, the Google tag, the Meta Pixel, session recorders and any embed that sets cookies wait for a yes.
  6. Set Consent Mode defaults to denied for EEA visitors. Basic mode unless your lawyer agrees to advanced.
  7. Wire the Meta Pixel. Revoke before it starts, grant on consent, and make the Conversions API follow the same choice.
  8. Keep a way back and a record. A “Cookie settings” link in the footer, consent logs kept, consent renewed within 24 months.
  9. Update the cookie and privacy pages. Name each tool, its purpose and who receives the data.
  10. Check the ads. No targeting by health or other sensitive traits, nothing aimed at minors, no form contents sent to a pixel. Then find your own ads in the platform’s ad library.

Repeat step 1 after every change: a new plugin can add a tracker your banner does not know.

Sources

  1. 01
  2. 02
    GDPR, Regulation (EU) 2016/679 (opens in a new tab)

    EUR-Lex27 April 2016eur-lex.europa.eu

  3. 03
  4. 04
  5. 05
  6. 06
  7. 07
  8. 08
  9. 09
    Nuevo criterio de la AEPD sobre cookies (opens in a new tab)

    Cuatrecasas11 January 2024cuatrecasas.com

  10. 10
  11. 11
  12. 12
  13. 13
  14. 14
    EU user consent policy (opens in a new tab)

    Google21 November 2026google.com

  15. 15
    Regulatory changes for EEA traffic (opens in a new tab)

    Google Ads Help21 November 2026support.google.com

  16. 16
    Adapt to regulatory changes with consent mode (opens in a new tab)

    Google Ads Help21 November 2026support.google.com

  17. 17
    Set up and manage consent (opens in a new tab)

    Tag Manager Help21 November 2026support.google.com

  18. 18
    About consent mode (opens in a new tab)

    Google Ads Help21 November 2026support.google.com

  19. 19
    About consent mode modeling (opens in a new tab)

    Google Ads Help21 November 2026support.google.com

  20. 20
    [GA4] Behavioral modeling for consent mode (opens in a new tab)

    Analytics Help21 November 2026support.google.com

  21. 21
    Meta Business Tools Terms (opens in a new tab)

    Meta3 November 2025facebook.com

  22. 22
    Meta Pixel and the GDPR (opens in a new tab)

    Meta for Developers21 November 2026developers.facebook.com

  23. 23
    Conversions API implementation (opens in a new tab)

    Meta for Developers21 November 2026developers.facebook.com

  24. 24
    Meta commits to give EU users choice on personalised ads (opens in a new tab)

    European Commission8 December 2025digital-markets-act.ec.europa.eu

  25. 25
    Form 10-Q, Q3 2026 (opens in a new tab)

    Meta Platforms (SEC)22 October 2026sec.gov

  26. 26

About the author

Abdelrahman Shalaby

I’m the founder of Fairhewn: Egyptian, a native Arabic speaker, born and raised in the UAE.

I design and build every website myself, and run ads and social media for interior, fit-out, joinery and remodeling firms. I answer every message.

More about me

See your homepagebefore you pay.

Book a free 20-minute call. I design your homepage from your project photos, and you see it before you pay anything.