Skip to main content
TrackingConsulting
Now booking · 2–4 day turnaround

Consent Mode warnings · Conversion tracking

Recover 40–80% of your Consent Mode warnings ad revenue.

Done-for-you 1st-party server-side tracking on Meta, Google, TikTok and Microsoft. Built in 2–4 days. You own the entire stack. No monthly SaaS fees.

✓ 30-minute call · No commitment · You leave with a written remediation plan even if we’re not the right fit.

Built in 2–4 daysOne-time fee95% accuracy guaranteed400-day cookie lifetime1st-party server-side

Built on — and certified for — the platforms that matter

Stape

Pro Partner

Meta

Tech Provider

Google

Tag Manager

TikTok

Events API

Microsoft

UET Partner

LinkedIn

CAPI Partner

Pinterest

CAPI Partner

Built on the same partner stack used by enterprise DTC brands.

Ariful Islam — Founder, Tracking Consulting

Meet your consultant

Ariful Islam

Founder · 8+ years in paid media & tracking

Verified earnings

$200K+

earned on Upwork

Top Rated Plus
4.9/5 · 300+

Verify the receipts

You work directly with Arif — no SDR, no account manager.

By the numbers

No fake testimonials. Just the math.

70+

Platforms supported

Shopify · Woo · Magento · BigCommerce · 65 more

8+ / 10

Meta EMQ guaranteed

in writing — keep working free until hit

2–4d

Build to live

accurate data flowing within 7 days

$0

Monthly fees, ever

one-time fixed price · you own the stack

400d

Cookie lifetime

max RFC 6265bis allows · 57× Safari ITP

9

Ad channels covered

Meta · Google · TikTok · MS · LI · Pin · Snap · Reddit · X

95%+

Tracking accuracy

verified vs Stripe · GA4 · ad-platform reports

30 min

Free founder call

no SDR · no pitch deck · written remediation plan

Numbers from realistic engagements. Your specific recovery depends on your iOS share, ad-blocker rate, and current setup — we’ll quantify it on the call.

Real clients · real videos · real outcomes

Don’t take our word for it. Watch the receipts.

Founders, marketers, and agency owners describing the before-and-after of their Consent Mode warnings tracking rebuild — in their own words, on camera.

The problem

Why the warning won't clear

Consent Mode warnings-specific issues
Leak #01

Your CMP loads after your tags do

The consent default command has to run before gtag or GTM. If the banner script is async, or loaded as a GTM tag itself, the first pageview fires with no consent state at all and Google logs the hit as unconsented.

Leak #02

You wired two signals when v2 needs four

ad_storage and analytics_storage were the whole story under v1. ad_user_data and ad_personalization are separate signals now, and Google's check looks for all four before it drops the EEA flag.

Leak #03

Tag-level Consent Settings are left at "Not set"

GTM's per-tag additional consent checks default to nothing. Tags you assumed were gated fire regardless of the banner, and the ones you meant to run early get held anyway. Neither matches what the page promised.

Leak #04

A global denied default hits traffic that never needed it

One worldwide denied-by-default state means your US visitors get the EEA treatment — throttled tags, modeled data — for a rule that never applied to them. Region-scoped defaults cover both without the collateral damage.

Who this is for

Honest about who we’re a fit for.

We don’t take every project. Here’s how to tell if we’re right for you.

Good fit

You’re a great fit if…

  • You run Consent Mode warnings (or are migrating to it)
  • You spend $5K+/month on paid ads (Meta, Google, TikTok, Microsoft, LinkedIn)
  • Your reported ROAS doesn’t match what your bank account is saying
  • You want to own your tracking stack — no monthly SaaS fees forever
  • You have 2–4 days to do this once and never think about it again
Not a fit

Skip us if…

  • You spend less than $500/month on paid ads (browser pixel is fine)
  • You want a SaaS dashboard with monthly fees forever (Triple Whale, Hyros)
  • You need attribution modeling — we fix the data foundation, not multi-touch reports
  • You want a 6-month enterprise consulting engagement (we ship in 4 days)
  • You expect us to manage your ad accounts (we don’t — that’s a different service)

If you’re still unsure, book the call anyway — we’ll tell you straight whether we can help.

Our position

If your reported ROAS disagrees with your bank account, you don’t have an attribution problem. You have a data foundation problem. No SaaS dashboard fixes that — only a rebuilt 1st-party server-side stack does.

Ariful Islam — Founder
The outcome

What changes once consent is wired the way Google's check expects

The warning clears, and you know exactly why

Server-side

Default before update, four signals present, state reported on every load. You get the before-and-after from Tag Assistant's consent view so the fix is evidence, not a claim.

Conversion modeling becomes eligible

8+ EMQ

Google only models the denied portion of traffic when consent signals arrive in the expected shape and volume. Wired correctly, a denied session still contributes to modeled conversions instead of disappearing entirely.

Your tags do what the banner said they'd do

Deduped

Each tag carries an explicit consent check, so a visitor who declines doesn't quietly pick up an advertising cookie anyway. That gap is the one that turns a technical issue into a legal one.

US privacy signals handled by the same mechanism

Backend-verified

A Global Privacy Control header or a CPRA opt-out maps onto the same consent state as an EEA denial, so you run one consent system rather than two half-finished ones.

The full transformation report

Before vs after — built in 2–4 days, accurate data within 7 days

We deliver the 1st-party server-side stack in 2–4 business days. Each metric below measured 7 days pre-launch vs 7 days post-launch using your own ad-platform reports + Stripe + GA4. No 30-day waiting game.

Attribution accuracy

  • Reported ROAS vs Stripe match
    Before60% (35% drift)
    After95%+ match
  • iOS conversion match rate
    Before~58%
    After~92%
  • Cross-domain click-ID retention
    Before~40%
    After~95%
  • Server-attributed conversions
    Before0%
    After100%

Audience quality

  • Meta Event Match Quality
    Before4.5 / 10
    After8+ / 10
  • Cookie lifetime (Safari)
    Before7 days (ITP cap)
    After400 days (max allowed)
  • Lookalike seed-list size
    BeforeShrinking as signal decays
    AfterRebuilt from server-side matches
  • Identity match params sent
    Before1–2 (email maybe)
    After9 (email · phone · IP · UA · click_id · etc.)
  • Retargeting list health
    BeforeDecaying
    AfterCompounding

Bidding performance

  • Smart Bidding stability
    BeforeRetraining weekly
    AfterLocked-in
  • CPA trend
    BeforeDrifts up as signal degrades
    AfterBidding learns from complete data
  • ROAS variance week-over-week
    Before±35%
    After±5%
  • Conversion volume Meta sees
    Before65%
    After95%+

Compliance & ownership

  • GDPR / CCPA audit-ready
    BeforeWeak
    AfterAudit-clean
  • Consent Mode v2 wiring
    BeforeNot configured
    AfterFully wired + verified
  • 3rd-party cookie deprecation ready
    BeforeNo
    AfterYes
  • Data ownership
    BeforeVendor-locked
    After100% yours

Server-side

money events from your backend

8+ / 10

Meta EMQ guaranteed

95%+

tracking accuracy

A typical engagement

The shape of a typical Consent Mode warnings rebuild

We’re not going to invent a fake testimonial here. Instead — here’s the realistic pattern of what happens, anonymized but accurate to engagements we ship.

Day 0 — They arrive

A 7-figure Consent Mode warnings store spending ~$25K/month on Meta. Reported ROAS shows 4.1× in Ads Manager. Their bookkeeper’s number says 2.6×. The founder doesn’t know which is real, so they keep doubling down on what looks like a winning campaign — except cash flow tells a different story.

Day 1 — Audit

We screen-share. Within 20 minutes we’ve found the leaks: native pixel firing twice on iOS, CAPI dedup using the wrong event_id (Meta is double-counting), GA4 showing 38% (not set), and the Customer Events API never enabled. The 1.5× ROAS gap explains itself.

Day 2–3 — Build

Server-side GTM container goes live on data.theirstore.com. Meta CAPI rebuilt with full advanced matching. Google Enhanced Conversions wired. TikTok Events API turned on. All event_ids deterministic. iOS recovered.

Day 4 — Launch

Live-fire test purchases through every funnel step. Meta Event Match Quality goes from 4.5 to 8.7 — verified live in Events Manager. They get a Notion runbook + Loom walkthrough so their dev team can extend it.

Day 5–7 — Accuracy

Conversion data starts flowing cleanly. Day 7: reported ROAS reads 2.8× (matches Stripe within 5%). Lookalike audiences grow because Meta finally has clean seed data. Their CAC dashboard makes sense for the first time in a year.

Day 30 — The math compounds

Smart Bidding has 30 days of clean signal. CPA drops 18%. They scale Meta budget 40% because they finally trust the data. Net new revenue from the recovered tracking: roughly $14K/mo above what they were getting before.

Numbers above are realistic averages from engagements we’ve shipped. Your specific recovery depends on your iOS share, ad-blocker rate, and current setup — we’ll quantify it on the call.

The cookie window unlock

400-day cookie lifetime — the longest your browser allows

Default Consent Mode warnings setups put cookies on a 7–30 day timer. Safari ITP caps client-set cookies at 7 days. That kills your retargeting windows, shrinks lookalike audiences, and starves Smart Bidding of historical signal.

We set 1st-party cookies via HTTP headers on your own subdomain — exempt from ITP’s 7-day cap. Lifetime: 400 days. The maximum Chrome, Firefox and Safari currently permit.

  • 57× longer retargeting window vs Safari default

    Reach users who saw your ad 6 months ago instead of last week.

  • Bigger lookalike seed pools

    More retained users in your custom audience = better lookalike quality on Meta, Google, TikTok.

  • Smart Bidding has 13× more signal history

    Algorithms optimize on 400 days of behavior, not 7 days. CPA stabilizes faster.

  • Critical for high-AOV / long-consideration purchases

    If your average buyer takes 30+ days to convert, default cookies miss them. 400-day cookies don’t.

Cookie lifetime — head to head

How long cookies survive in real-world traffic

Safari ITP (default)7 days
Chrome / Firefox (typical)30 days
Meta default retargeting window90 days
Google Ads default cookie540 days(but capped by browser)
Our 1st-party server-side400 days

400 days is the hard maximum enforced by RFC 6265bis (Chrome 104+, Safari 17+, Firefox 110+). We set it via HTTP Set-Cookie: Max-Age=34560000 on your subdomain. Survives Safari ITP’s 7-day client-side cap.

Under the hood

What’s actually happening on your server-side stack

Six capabilities your default Consent Mode warnings setup doesn’t have. Built on the same Stape Pro stack used by enterprise DTC brands.

Cookie window

Cookie Keeper

400-day 1st-party cookies

Set via HTTP headers on your subdomain — the maximum browsers allow. Survives Safari ITP’s 7-day cap that kills retargeting.

Ad-block resistance

Custom Loader

Custom-loaded GTM scripts

Your gtm.js and analytics scripts load through a custom path on YOUR domain. uBlock, AdBlock Plus, Brave can’t identify them as trackers.

Attribution

Click ID Restorer

Click ID restoration

fbclid / gclid / ttclid / wbraid recovered from the URL and persisted server-side. Multi-redirect funnels stop dropping attribution. Safari user IDs restored.

Profit signal

POAS Data Feed

POAS — Profit on Ad Spend

Send actual profit data (not revenue) to Meta / Google. Smart Bidding optimizes for the metric that matters: net margin, not gross revenue.

Identity

User ID

Cross-session User ID

Stable userID generated server-side from IP + UA + SSL fingerprint. Stitches anonymous → known → returning visitors across 400 days.

Audience signal

GEO Headers

GeoIP enrichment

Country, region, city, postal code passed to Meta / Google CAPI from your server — without exposing the raw user IP to the browser.

Compliance

Anonymizer

PII hashing by default

Email, phone, name, address are SHA-256 hashed on your server before they leave for Meta or Google. Zero raw PII in transit.

Quality filtering

Bot Detection

Bot traffic detection

Bot/scraper traffic identified at the gateway and blocked from polluting your audiences. Smart Bidding optimizes against humans, not bots.

Reliability

Dedup logic

Browser ↔ server dedup

Deterministic event_id and event_time so Meta / Google never double-count. Your reported ROAS stops contradicting Stripe.

Reputation

Dedicated IP

Dedicated outbound IP

Your sGTM gets a dedicated static IP for outgoing CAPI requests. Better deliverability to Meta, Google, TikTok — no shared-IP noise.

Residency

Multi-region

EU / US region routing

GDPR-conscious stores route their CAPI traffic through EU regions (Stape EU or self-hosted GCR europe-west). No US data hop.

Data warehouse

BigQuery export

BigQuery + Looker dashboard

Server logs + GA4 raw events streamed to BigQuery. Looker Studio dashboard branded for your team. Premium tier.

We’re official Stape Pro partners — every Power-Up above is enabled and configured for you. Or we self-host the equivalent on your Cloud Run / GKE if your traffic justifies the cost crossover. You pick.

Live data flow

What your stack is doing — right now

Every conversion fires through your subdomain, gets enriched with hashed identity params, deduped against the browser pixel, then forwarded to Meta CAPI, Google EC, TikTok Events API and Microsoft UET in parallel.

You see this stream live in your sGTM debug console — not a SaaS dashboard you rent. It’s your data, on your server, on your subdomain.

  • p99 latency< 80ms
  • Avg. event payload9 identity params
  • Browser → Server dedupDeterministic event_id
  • Failure handlingRetry · queue · dead-letter
sgtm-debug · data.fix.com
streaming
10:42:18[INFO ]evt=PageView | id=ev_a3f2.. | ua=ios17 | ip_hash=ok
10:42:18[OK ]→ meta.capi status=200 emq_pred=8.6
10:42:18[OK ]→ google.ec status=200 match=enhanced
10:42:24[INFO ]evt=AddToCart | id=ev_b1c8.. | val=$84.00
10:42:24[DEDUP]browser↔server merged on event_id=b1c8..
10:42:24[OK ]→ meta.capi status=200 emq_pred=8.7
10:42:24[OK ]→ tiktok.eventsapi status=200
10:42:31[INFO ]evt=Purchase | id=ev_c9d4.. | val=$184.00
10:42:31[POAS ]profit=$58.42 sent (margin 31.7%)
10:42:31[OK ]→ meta.capi status=200 emq=8.8 ✓
10:42:31[OK ]→ google.ec status=200 ✓
10:42:31[OK ]→ microsoft.uet status=200 ✓
10:42:33[BOT ]blocked: ua=AhrefsBot · 1 evt suppressed
uptime: 99.98%all channels healthy
Every paid-media channel · 1st-party server-side

CAPI / Events API ready for every ad platform you run

One server-side gateway. Every major ad platform fed real conversion data, deduped, with full identity match.

Meta

Conversions API

Server-side

Google

Enhanced Conv.

Server-side

TikTok

Events API

Server-side

Microsoft

UET Server

Server-side

LinkedIn

CAPI

Server-side

Pinterest

CAPI

Server-side

Snapchat

CAPI

Server-side

Reddit

CAPI

Server-side

X / Twitter

Events API

Server-side
What you get

What we change in the consent chain

Item 01

The default state placed ahead of everything

The consent default command moved into the document head, before GTM and gtag, with wait_for_update tuned so the banner has time to answer without visibly stalling the page.

Item 02

Four v2 signals, scoped by region

ad_storage, analytics_storage, ad_user_data and ad_personalization set per region — EEA and UK denied by default, other regions set to whatever your counsel's policy actually says.

Item 03

Per-tag consent settings across the container

Every tag given explicit additional consent checks instead of "Not set", written up as a table you can hand to legal without translating it first.

Item 04

Your CMP wired to the update command

CookieYes, Cookiebot, Osano, Termly or an in-house banner hooked to fire consent update on accept, on reject, and on a later preference change — including the returning visitor whose choice is already stored.

Item 05

Consent state carried into the server container

The decision travels with the event to sGTM, so server-side tags respect it too. A server container that fires regardless of consent is the most common thing we find and the least often noticed.

Item 06

Tag Assistant and Ads diagnostics evidence

Screenshots of the consent view and the Google Ads diagnostics panel before and after, so you can see the flag change state rather than take our word for it.

The honest math

Three ways to fix your tracking. One of them makes sense.

Option 1

Hire a senior tracking engineer

$15K–$25Kin dev cost

or 2–4 weeks of senior FTE time

  • 2–4 weeks before anything ships
  • Misses iOS / Safari / dedup edge cases
  • No EMQ guarantee — it’s “done” when they say so
  • Pixel debugging is not their day job

Option 2

Triple Whale / Hyros / Northbeam

$300–$2,000/month forever

$18K–$120K over 5 years

  • You rent a dashboard — they own your data
  • Cancel and you lose attribution overnight
  • Per-event / per-visitor pricing surprises
  • Still doesn’t fix your underlying tracking
Recommended

Option 3 — us

Done-for-you 1st-party server-side

$400–$1,800one-time

pay once · own the stack forever

  • Live in 2–4 days · accurate data within 7
  • iOS / Safari / dedup all handled by default
  • Meta EMQ 8+ guaranteed in writing
  • You own everything — server, container, runbook

We’re upfront: if you have a senior in-house dev with capacity and 4 weeks, hiring is fine. If you spend $1M+/yr on ads and want a SaaS dashboard layered on top, Triple Whale works. For most paid-ad advertisers between, we’re the math that makes sense.

From the founder’s desk
Ariful Islam — Founder
Available now

Ariful Islam

Founder & lead engineer

  • Experience8+ years in tracking
  • Engagements300+ DTC brands shipped
  • Specialty1st-party sGTM · CAPI
  • PartnerStape Pro · Meta Tech

“I’ll personally walk through your tracking on the call. No SDR. No sales pitch.”

I’ve spent 8 years rebuilding tracking for DTC brands, SaaS founders, agencies, and one thing I’ve learned: most tracking problems aren’t technical — they’re trust problems. You don’t know who to believe. Your current vendor swears it’s fine. Meta’s reports look great. Stripe says otherwise.

On our call, I’ll personally show you exactly what’s leaking, exactly what it would cost to recover, and whether you should hire us at all. If your current setup is genuinely fine, I’ll tell you. If a $400 browser-side fix is enough, I’ll say so. No upsell pressure.

Book the call. Worst case, you walk away with a free 47-point audit checklist. Best case, we deliver your 1st-party server-side stack in 2–4 days and your data is fully accurate within 7 days.

Arif— Founder

How it works

Built in 2–4 days. Accurate data within 7.

We deliver the entire 1st-party server-side stack in 2–4 business days. You start collecting accurate, deduped conversion data the moment it goes live — and within 7 days every signal is flowing cleanly to Meta, Google, TikTok and the rest.

1Day 1

Kickoff + audit

30-min call. We map your current pixels, GTM, dataLayer, consent setup, and ad-platform integrations. You get a written report of every leak.

2Day 2–3

Build the stack

Server-side GTM container deployed on your subdomain. Meta CAPI · Google EC · TikTok Events API · Microsoft UET wired. Identity match + dedup configured.

3Day 4

QA + go-live

Live-fire test purchases across every funnel step. Meta EMQ verified at 8+. Tag Assistant + Pixel Helper passes. Side-by-side report delivered.

4Day 5–7

Verify accuracy

Your data flows clean. Within 7 days every signal — Meta, Google, TikTok, Microsoft — is fully accurate. Notion runbook + Loom walkthrough handoff.

Diagnose it honestly

EEA warnings on EEA traffic are expected. Ungated tags are not.

The warning itself isn't the fault. It's Google telling you a requirement now attaches to that conversion action, and on an account with European visitors that's a configuration job with a clear finish line. What's actually broken is when your tags ignore the banner your visitors just answered.

Normal — not a fault

  • A consent warning on an account with real EEA or UK traffic

    Expected, and it's configuration work rather than a bug. Google attaches the requirement to the conversion action the moment measurable European traffic reaches it. You wire the four v2 signals and the flag clears.

  • A US-only account seeing the same warning

    Almost always a slice of European visitors nobody knew about — organic, a referral, a VPN-heavy audience, a stray campaign. Check GA4 by country before assuming something is misconfigured.

  • Reported conversions moving after consent is wired right

    If tags used to fire for people who declined, the raw count drops. If modeling becomes eligible where it wasn't, modeled conversions come back. Movement in either direction is the fix landing, not a new problem.

  • GA4 showing modeled conversions on European traffic

    Behavioral and conversion modeling is exactly what Advanced consent mode buys. Modeled rows appearing on denied EEA sessions means the signals are arriving in the shape Google expects them in.

Actually broken

  • The warning stays red after your CMP says v2 is on

    A ticked box in the CMP dashboard doesn't mean the default command ran first. If the banner script is async, or loaded as a GTM tag itself, the first pageview goes out with no consent state at all.

  • Ad cookies get written for a visitor who clicked Reject

    Decline the banner, then look in DevTools for `_gcl_aw`, `_gcl_au` or `_fbp`. Anything advertising-related appearing after a rejection is the failure that turns a technical issue into a legal one.

  • US traffic throttled by a global denied default

    One worldwide denied state gives American visitors the EEA treatment — held tags, modeled data — for a rule that never applied to them. Region-scoped defaults cover both without the collateral damage.

  • The server container fires regardless of the decision

    Web tags respect the banner, the consent state never reaches sGTM, and server-side tags forward everything anyway. This is the most common thing we find and the least often noticed.

Diagnostic sequence

How to see your own consent state in about twenty minutes

GTM's consent debug view answers most of this without anyone touching your container settings.

  1. 1

    Open the GTM consent view in a fresh incognito window

    GTM Preview, then the Consent tab, and look at the very first event in the timeline. If ad_storage reads "not set" before the banner has been answered, your default command never ran in time.

  2. 2

    Check all four v2 signals by name

    In that same view, confirm ad_storage, analytics_storage, ad_user_data and ad_personalization are all present. Two of four is a v1 setup, and Google's check will keep flagging it no matter what the CMP says.

  3. 3

    Click Reject, then read the cookie jar

    DevTools, then Application, then Cookies. Any advertising cookie written after a rejection means the tags aren't genuinely gated — whatever the per-tag settings claim in the container.

  4. 4

    Come back to the site as a returning visitor

    Close the tab and reopen the site. The stored choice has to replay as a consent update on the second visit. Plenty of banners fire update on the click and never on the replay, so returning visitors run unconsented.

  5. 5

    Check where your European traffic actually comes from

    GA4, Reports, then Demographics by country, filtered to EEA and UK. Most US advertisers carrying this warning aren't targeting Europe at all — they just have European visitors nobody had counted.

  6. 6

    Read the Google Ads diagnostics panel itself

    Open the conversion action and go to Diagnostics. It names the unmet requirement in plain language, and screenshotting it before you change anything gives you the before half of your evidence.

Source-of-truth validation

How we prove the consent flag actually cleared

Consent work is easy to claim and easy to check, so we check it in both states and hand over the screenshots either way.

Source of truthGoogle Ads conversion-action diagnostics · GTM consent debug view
  • Capture the consent view before and after, showing the default command firing ahead of the first tag on the page.
  • Confirm all four v2 signals are present and region-scoped, with EEA and UK denied by default and other regions per policy.
  • Load the site as a declining visitor and verify no advertising cookie is written at any point afterward.
  • Reopen as a returning visitor and confirm the stored choice replays as a consent update, not just on the original click.
  • Screenshot the Google Ads diagnostics panel once the EEA requirement stops being flagged on the conversion action.
  • Send a test event and confirm the consent state arrives in the server container alongside it, and that tags honor it.

Straight talk

When a full Consent Mode v2 build is premature

Consent work is worth doing properly, and it isn't worth doing early.

  • You serve US-only traffic, see no warning in Ads or GA4, and no state law puts you in scope. Set sane defaults and revisit later.
  • Your CMP ships a native GTM template and your only gap is ad_user_data and ad_personalization. That's an hour of your own time.
  • Counsel says no request may reach Google before consent. That's Basic consent mode and a policy call — no engineering also buys you modeling.
  • You run analytics only, with no remarketing and no conversion tags. The v2 advertising signals have nothing on your site to gate.

Got questions?

The honest answers.

No buzzwords, no upsell. If we don’t know, we say so.

01Can I fix this myself?

The obvious part, yes. If your CMP ships a native GTM template, installing it and adding ad_user_data and ad_personalization gets a lot of accounts over the line in an hour. Three things catch people out and are worth budgeting a day of testing for: load order, because the default has to fire before your tags; region scoping, because a global denied default hurts traffic that never needed it; and the returning visitor, whose stored choice has to replay as an update on the second visit. Use GTM's consent debug view and check all three states.

02Does this make us compliant?

No one can honestly promise that, and I'd be careful with anyone who does. What we do is make the technical signals match the choice your banner collected and the policy your counsel wrote. Whether that policy is correct for your jurisdictions, your data flows and your vendors is a legal question, and we're not lawyers. We'll happily give your attorney the tag-by-tag table so they can review what's actually firing.

03We're a US company. Why are we getting an EEA warning?

Google flags the conversion action, not the campaign. If any measurable share of traffic hitting that tag comes from the EEA or UK — organic, referral, a stray campaign, a VPN-heavy audience — the requirement attaches. Most US advertisers we see with this warning aren't targeting Europe at all; they just have European visitors.

04Will my reported conversions drop after this?

They can move either way, and you should expect movement. If tags were previously firing for people who declined, that stops, and the raw count goes down. If modeling becomes eligible where it wasn't, modeled conversions come back in. Either way the underlying orders are unchanged — you're correcting the measurement, not the business.

05Basic or Advanced Consent Mode?

Advanced for most advertisers: tags load and send cookieless pings before consent, which is what makes modeling possible. Basic blocks tags entirely until consent and gives up the modeling. If your counsel takes the position that no request should reach Google before consent, you take Basic and accept less data. That's a legal call, not a technical one.

06Does this affect GA4 as well as Google Ads?

Same signals, same plumbing. GA4's behavioral and conversion modeling keys off analytics_storage and the consent state arriving in the expected shape. When the Ads warning clears, the GA4 property notice usually clears with it, because both were reading the same missing signals.

07When do we NOT need this?

If you serve US-only traffic, run nothing in the EEA or UK, see no warning in either platform, and no US state law currently puts you in scope, a full v2 build is premature. Set sane defaults, make sure your banner isn't accidentally blocking Conversion Linker, and revisit if you expand or if your legal exposure changes.

Still have questions? Book a 30-min call — bring them all.

The call

What happens on your free 30-min call

No pitch deck, no SDR, no upsell pressure. Founder-led. Bring your ad-platform screens and your Consent Mode warnings setup — we’ll work through it together.

Min 1–5

We get the lay of your store

What you sell, what you spend on ads, who handles dev. Quick context-gathering — no questionnaire upfront.

Min 5–15

We audit your tracking live

Screen-share. We open your Meta Events Manager, GTM, and ad reports. You see exactly which conversions are leaking.

Min 15–25

We map a fix

What needs rebuilding, what stays. The exact Consent Mode warnings setup we'd ship and what it would recover for you.

Min 25–30

Decide. Or don’t.

If we're a fit, we send a 1-page proposal in writing. If not, you walk away with a free remediation plan you can hand to anyone.

No pitch deckFounder-led, not SDRYou leave with a written planZero commitment
Free · 30 minutes · No commitment

Send me your URL and I'll tell you which tag is triggering the flag

I'll load your site in both consent states, record what each tag does, and send back the specific sequencing problem — usually it's one script loading in the wrong order.

Free · 30-min consultation · No commitment · Replies in under 2 hours · Available worldwide via WhatsApp

95% guarantee · fixed-fee