If you run ads into Europe, two regulatory changes have quietly rewritten how your campaigns measure and target: Consent Mode v2 and the Digital Markets Act. Most advertisers implemented the first one badly and have not noticed the second one at all. Both cost money, and neither shows up as an error in your account.
Consent Mode v2: basic versus advanced is the whole decision
Consent Mode passes a user's cookie choice to Google so tags can adapt. The part that matters commercially is which version you implemented, because they are not close to equivalent.
- Basic mode blocks tags entirely until the user accepts. If they decline, Google receives nothing at all, not even the fact that a decision happened. Your conversion modelling then falls back to a generic model built from other advertisers.
- Advanced mode loads tags with consent defaulted to denied, and sends cookieless pings regardless. When someone declines you still get a signal, so Google can build an advertiser-specific model from your own traffic.
- The gap between those two is real recovered conversions. An advertiser-specific model is trained on your funnel. A general model is trained on everyone's. In a market where a large share of users decline, that difference decides what Smart Bidding learns from.
Most implementations I audit are basic mode installed by a consent plugin's default settings, with nobody having chosen it deliberately. Check which one you are running before touching anything else, because every downstream measurement fix inherits this.
The EEA consent fields you now have to send
Separately from banners, Google now requires advertisers to pass consent signals for EEA users on any customer data you upload, audience lists and offline conversions included. Two fields, covering consent for personalised advertising and for ad personalisation.
- Missing them does not throw an error, it shrinks your audiences. Lists quietly fail to match, remarketing pools thin out, and Customer Match stops doing much.
- This hits B2B hardest, because offline conversion imports from a CRM are exactly the mechanism that makes B2B SaaS paid ads work at all.
What the DMA changed, including one thing in your favour
The Digital Markets Act is usually discussed as a restriction, and for targeting it is. Fine-grained behavioural targeting simply delivers less in the EU now, and a larger share of performance comes from contextual fit and creative quality instead.
In the EU the targeting lever got shorter and the creative lever got longer. Budgets built on audience precision now underperform budgets built on message relevance.
But the DMA also handed advertisers something most never claim. Gatekeepers must now provide, on request and free of charge, daily information on the pricing and fees attached to each ad you place, including deductions and surcharges. There are tools and APIs for pulling detailed reports that used to be invisible.
Almost nobody asks. If you spend meaningfully in Europe, that data tells you what share of your budget actually reached inventory rather than fees, which is a question programmatic buyers have wanted answered for a decade. It pairs directly with the placement hygiene discussed in programmatic versus Google Ads.
Meta's pay-or-consent problem
Meta's consent-or-pay model in the EU remains contested and has already drawn a DMA fine. The practical effect for advertisers is an EU audience where a meaningful slice has opted out of personalised targeting entirely. Plan EU Meta campaigns around broader reach and stronger creative rather than the narrow interest stacks that still work elsewhere.
What to actually do, in order
- Confirm whether you are on basic or advanced Consent Mode. If basic, switching is usually the single highest-value measurement change available to an EU advertiser.
- Add the EEA consent fields to every audience and offline conversion upload, then watch match rates recover.
- Layer server-side tracking underneath. Consent handling and server-side tracking solve different problems, and EU traffic needs both. Consent decides whether you may measure; server-side decides whether you technically can.
- Request your DMA pricing reports if European spend is material, then reconcile them against what your DSP or platform reports.
- Shift testing budget from audiences to creative, because that is where EU performance now lives.
None of this is exotic. It is the unglamorous compliance and measurement layer that decides whether everything above it works, which is the same argument as the audit checklist: fix upstream before optimising downstream.
Frequently asked questions
What is the difference between basic and advanced Consent Mode?
Basic Consent Mode blocks Google tags from firing until a user accepts, so declining users send no data at all and conversion modelling uses a generic model. Advanced Consent Mode loads tags with consent defaulted to denied and sends cookieless pings either way, which lets Google build an advertiser-specific model from your own traffic and recover more modelled conversions.
Do I need Consent Mode if I only advertise outside the EU?
Not strictly, but if any meaningful share of your traffic comes from the EEA, Switzerland or the UK, you need it for those users. Many advertisers assume they have no EU traffic and find 10 to 20 percent of sessions once they check the geography report.
What are the new EEA consent fields for audience uploads?
Google requires two consent-related fields covering personalised advertising and ad personalisation on any customer data uploaded for EEA users, including audience lists and offline conversion imports. Omitting them does not produce an error; it quietly reduces match rates and shrinks your audiences.
Can advertisers really get fee breakdowns under the DMA?
Yes. The DMA obliges gatekeepers to supply advertisers, on request and at no cost, with daily information on the prices and fees attached to each ad placed, including deductions and surcharges. Very few advertisers request it, which is why most still cannot say what share of their European budget reached actual inventory.