Consent Mode and Influencer Tracking in the EU

What Consent Mode actually is (and isn't)

Consent Mode isn't a law, and it isn't a cookie banner. It's Google's own technical signaling system that tells Google Ads, Google Analytics 4 (GA4), Floodlight and Google Tag Manager what consent a visitor actually gave — accepted or declined — so Google's own tags can adjust what they collect and send. The cookie banner a visitor actually sees and clicks is still yours (or your Consent Management Platform's, CMP's); Consent Mode is just the format that banner choice gets relayed to Google in.

That distinction matters, because Consent Mode is often confused with the consent requirement itself. The two are connected but separate: the legal duty to ask for consent before setting a non-essential cookie comes from Danish and EU law (see the cookie-law section below); Consent Mode is just the technical channel that choice gets forwarded to Google through.

The four consent signals in Consent Mode v2

Per Google's own documentation, Consent Mode governs four separate signals, each covering a distinct purpose:

ad_user_data and ad_personalization are new to Consent Mode v2 — v1 only had ad_storage and analytics_storage. Per Google, using Consent Mode is a requirement to keep using Google's tools for ad personalization and measurement for visitors in the EEA, the UK and Switzerland, and if you use a Google-certified Consent Management Platform (CMP), it typically upgrades to the latest version automatically. Multiple independent compliance sources report enforcement as having taken effect on 6 March 2024, though Google's own support page describing the requirement doesn't itself state a specific date.

Basic vs. Advanced Consent Mode — what it means for your numbers

Google distinguishes between two implementations, and the difference directly determines how much data you can actually see:

• Basic Consent Mode blocks Google's tags entirely until the visitor has responded to the consent banner. If they decline, there's no data to model from — the tag never loaded in the first place.
• Advanced Consent Mode loads Google's tags before the visitor sees the consent banner, so the tag can send so-called "cookieless pings" even when consent is declined. Those cookieless pings give Google a data basis to model from — the actual precondition for behavioral and conversion modeling in GA4 and Google Ads.

In other words: choose Basic, and you lose data outright when consent is declined. Choose Advanced, and you still lose the real, individual measurement — but Google fills the gap with an estimate instead of a zero.

Conversion modeling: what Google actually does when someone says no

When a visitor declines consent under Advanced Consent Mode, Google doesn't set the cookie and doesn't store an individual user profile — instead, per Google's own explanation, it uses "behavioral modeling" and "conversion modeling" to estimate the missing activity. The model builds its estimate from high-level signals like browser type and time of day — not identifying information — to reconstruct what likely happened during the non-consented sessions.

That modeling is the whole point of Consent Mode from Google's side: without it, declined visitors vanish without a trace from Google Ads' and GA4's reporting. With it, a modeled, estimated figure shows up instead of a gap. It's still not the same as a real, individual attribution — but it isn't a zero either.

What happens to an influencer sale when consent is declined?

This is where an influencer tracking link fundamentally diverges from Google Ads and GA4 — and it's the central point of this article. The tracking link a commission calculation depends on (see how influencer tracking actually works) isn't a Google tag and isn't part of Consent Mode at all. If a customer declines marketing-cookie consent in your own cookie banner, the tracking system's cookie — whether it's Make Influence's or anyone else's — simply never gets set. There's no modeling to fill the gap. The sale still happens in the store's own system, just with no creator attached to it — the exact same mechanism as when a cookie expires or gets blocked by the browser, just triggered by a deliberate "no" instead of a technical limit (see attribution windows in influencer marketing for the technical-expiry version of the same problem).

That means a brand that has Consent Mode dialed in and sees sensible, modeled numbers in Google Ads can easily be sitting on an influencer tracking setup that's genuinely missing a meaningful share of its data — with no warning, because Google and influencer tracking are two separate systems that respond very differently to the exact same "no".

Consent Mode is not the same thing as the consent requirement itself

Consent Mode is Google's technical answer to a legal requirement, not the requirement itself. The underlying duty to ask for consent before setting a non-essential cookie — whether it's a Google cookie, an influencer tracking cookie, or anything else — comes from the EU's ePrivacy Directive, implemented in Denmark as the cookie regulation ("cookiebekendtgørelsen"), and applies alongside GDPR. Influencer marketing and GDPR already notes briefly that cookie consent is a separate rulebook from GDPR's Article 6; this article goes into what that consent actually has to satisfy, and what happens technically when it's given or declined.

Denmark's cookie consent rules

Per Datatilsynet's own guidance, using cookies and similar technologies has to satisfy both the data protection rules and the cookie regulation at the same time. Consent, per Datatilsynet, must be voluntary, informed and actively given — the user needs a genuine choice, free of coercion, misleading framing or pre-ticked boxes. A tracking or marketing cookie — which is what an influencer tracking link typically sets — doesn't fall under the "strictly necessary" exemption; that exemption only covers cookies required to deliver a service the user actively requested, such as a shopping cart. A commission-tracking or marketing cookie therefore needs explicit consent regardless of whether it comes from Google or from an influencer tracking platform.

In a joint guidance document with the Danish Agency for Digitalisation (Digitaliseringsstyrelsen) from May 2025, Datatilsynet also sharpened specific requirements for banner design itself: "reject all" has to be available in the first layer, on equal footing with "accept all" — same click, same visual weight — and withdrawing consent has to be as easy as giving it. A banner that makes "accept" a single click and "reject" three clicks doesn't meet the standard for a free, informed choice.

IAB TCF vs. Google Consent Mode — two different things

Consent Mode is Google's own signaling system for Google's own tags. IAB Europe's Transparency and Consent Framework (TCF), currently version 2.2, is something else: an industry standard many ad networks and adtech vendors — not just Google — use to exchange consent signals with each other. Most commercial CMPs (Cookiebot, OneTrust, Cookie Information and similar) support both simultaneously in practice: they forward the visitor's choice to Google in Consent Mode format and to the rest of the adtech ecosystem in TCF format. You don't have to choose between the two — but it's worth knowing that a misconfiguration in one doesn't automatically fix the other.

What about Meta and TikTok?

Meta and TikTok don't use the term "Consent Mode" — that's specifically Google's own name for its own system. But the underlying legal requirement is the same: marketing pixels and server-side APIs like Meta's Conversions API and TikTok's Events API (both covered in server-side and cookieless tracking in influencer marketing) still need to be gated by real consent before they send data about an EU user — server-side tracking isn't a shortcut around the consent requirement, just a different technical channel for the data consent actually governs. In practice, your CMP needs to block Google's, Meta's and TikTok's tags at the same time, not just Google's.

Comparison: what happens when consent is given or declined?

The discount-code row is worth dwelling on: because a discount code isn't a technical tracking mechanism but something the customer types in at checkout themselves, it's unaffected by whether consent was given or declined. That's the same underlying point that already applies to browser blocking — see discount codes vs tracking links — just driven here by a deliberate customer choice instead of a technical limit.

Worked example: how big is the gap? (hypothetical)

The numbers below are illustrative only, built to demonstrate the mechanism — not a real Make Influence customer case, and not an actual consent-decline rate for any specific audience or industry.

Assume a brand runs an influencer campaign with 1,000 tracking-link clicks that genuinely lead to 300 purchases. Assume further — purely for illustration — that 40% of visitors decline marketing-cookie consent in the brand's own banner. That means 120 of the 300 purchases (40%) happen where the tracking cookie is never set at all, because the customer actively said no. The remaining 180 purchases (60%) track normally, subject only to the usual browser-based losses covered in how influencer tracking actually works.

Over the same period, Google Ads — with Advanced Consent Mode enabled — shows a modeled estimate for the equivalent declined sessions in its own reporting, an attempt to fill that gap. The influencer tracking link has no equivalent model. The 120 purchases aren't "estimated lower" — they're not in the system at all. Without a discount code as a backstop, there's no way to recover them after the fact.

Decision framework

• IF you already use Google Ads or GA4 to measure your influencer traffic → make sure your CMP supports Consent Mode v2 and is configured for Advanced (not Basic) implementation, so you at least get a modeled figure instead of a gap.
• IF you primarily measure influencer commission through a tracking link → remember that Consent Mode does nothing for that link. The tracking cookie needs to sit in the same "marketing" category in your CMP as Google's own cookies, and a declined consent means an untracked sale, not a modeled one.
• IF you want the most robust coverage across consent status → pair the tracking link with a discount code, exactly as with browser blocking; see discount codes vs tracking links.
• IF your consent banner makes "reject" harder to find than "accept" → that's not just a legal risk under Datatilsynet's 2025 guidance, it's also a direct driver of more declined consents, and therefore more untracked sales.

Common mistakes

• Assuming Consent Mode "solves" consent for the whole campaign. It only governs how Google's own tags respond to a consent decision that's already been made somewhere else — your own cookie banner.
• Assuming the influencer tracking link is covered because Google Ads looks fine. The two systems are separate and respond very differently to a declined consent.
• Confusing a modeled figure with a real one. Conversion modeling is an estimate built from aggregated signals — not an individual attribution to a specific creator.
• Setting up server-side tracking and assuming it makes consent unnecessary. Server-side is a different transport route for the data — not an exemption from needing consent in the first place.

Make Influence's operational perspective

Make Influence's own tracking link isn't a Google tag, so it isn't part of Google Consent Mode. Our cookie, described in how influencer tracking actually works, belongs in the same category as any other marketing or tracking cookie in your own cookie banner — it needs consent on exactly the same terms, and we recommend placing it there rather than assuming your Google setup automatically covers it. In our experience, it's exactly that assumption — "we've handled cookies, because we set up Consent Mode" — that most often leads to an influencer tracking gap nobody has noticed yet.

FAQ

Is Consent Mode a legal requirement in itself?

No. The actual duty to obtain consent for non-essential cookies comes from the cookie regulation and GDPR. Consent Mode is Google's technical solution for how that consent gets reported onward to Google's own tags.

Does Advanced Consent Mode mean we no longer need a cookie banner?

No, the opposite. Advanced Consent Mode assumes you already have a cookie banner collecting valid consent — it only changes when and how Google's tags respond to that answer.

Does Consent Mode cover Make Influence's or other affiliate platforms' tracking links?

No. Consent Mode applies specifically to Google's own tags (Ads, Analytics, Floodlight, Tag Manager). An influencer tracking link is a completely separate cookie that needs its own category in your cookie banner and is governed by the cookie regulation on the same terms as any other non-essential cookie.

Can we use a modeled Google figure to "recover" the influencer sales we lost to declined consent?

No. Google's modeling is built specifically for Google's own conversions and can't be repurposed to estimate which of your influencer sales genuinely lacked a creator attribution.

Is a discount code exempt from the consent requirement?

Yes, in practical terms — the code isn't a tracking technology that sets anything in the browser, so it doesn't need cookie consent to function as a tracking mechanism. See discount codes vs tracking links for the full trade-off.

What's the difference between IAB TCF and Google Consent Mode?

TCF is an industry standard used by many adtech vendors to exchange consent with each other. Consent Mode is Google's own, separate signaling system for Google's own tags. Most CMPs support both at once.