You implemented a cookie banner two years ago, ticked the GDPR box, and never thought about it again. Then your Smart Bidding started underperforming, conversions dropped quietly month over month, and nobody could explain why. Nine times out of ten, the answer is the same: your Consent Mode v2 setup is running in Basic Mode when it should be running in Advanced Mode, and Google is throwing away the data that would have rescued your campaigns.
Consent Mode v2 has been mandatory for EU advertisers since March 2024, but most B2B teams treat it as a compliance task and never tune the technical configuration. Cookie Script's research shows that globally, only 31% of users accept tracking cookies, which means the 69% who reject are invisible to your tracking unless Consent Mode is set up to recover them. This post walks through the configuration that actually works in B2B. For the full picture on conversion tracking with cookie consent, see our complete guide to Google Ads conversion tracking with cookie consent.
Basic Mode vs Advanced Mode: The Decision That Matters
Consent Mode v2 has two implementation modes, and almost every problem we see in B2B accounts comes down to running the wrong one. Basic Mode blocks all Google tags from firing until the user gives consent. It is simple to implement but data dies the moment a user clicks "Reject". Advanced Mode lets the tags fire in a privacy-safe state without cookies, sends cookieless pings to Google, and lets Google's modeling engine reconstruct the missing conversions later.
The difference matters because B2B traffic tends to skew toward technically aware users who reject more often than a B2C audience. If your reject rate is 50% and you are in Basic Mode, Google sees half of your actual funnel and Smart Bidding optimizes against that half. The result is the slow, invisible underperformance that finance keeps asking about.
Unless you have a specific legal reason to block all tags, Advanced Mode is the correct default for B2B in the EU. The extra setup is small and the data recovery is significant.
How Conversion Modeling Works (and When It Activates)
Conversion modeling is the feature that justifies Advanced Mode. Google uses behavioral signals from consented users (device type, time of day, page sequence, referrer) to estimate how unconsented users likely behaved. Those estimated conversions show up in Google Ads as modeled conversions, which Smart Bidding then optimizes against.
Modeling only activates above a minimum traffic threshold. According to Google's official documentation, "You have a daily ad click threshold of 700 ad clicks over a 7 day period, per country and domain grouping" before modeling kicks in. For most small B2B accounts running narrow geographic targeting, this threshold is the actual blocker, not the technical setup. If you are running 300 clicks per week in DACH, modeling will not activate and you will see only the raw, observed conversions.
Advertisers typically see 15-25% uplift in reported conversions from modeling alone. The uplift is data Smart Bidding now has access to that you previously lost on every cookie rejection.
If you fall below the threshold, two practical options exist. Either consolidate small countries into a single domain grouping (which a multilingual B2B site often does anyway), or layer Enhanced Conversions on top of Consent Mode to recover data through hashed first-party signals instead of modeling. Most B2B accounts need both layers.
Step-by-Step Setup with a Certified CMP
Consent Mode v2 only works with a Google-certified Consent Management Platform. The CMP captures the user's consent decision and passes four signals to Google Tag Manager: ad_storage, analytics_storage, ad_user_data, and ad_personalization. Without a certified CMP, the signals will not flow correctly and you will be running broken Consent Mode without realizing it.
For the DACH market, three CMPs cover almost all B2B installations: Cookiebot, Usercentrics, and Consentmanager. All three are Google-certified, all three support Advanced Mode out of the box, and all three integrate with Google Tag Manager through a documented template. Pick based on legal entity (Cookiebot is Danish and popular for GDPR-strict installations, Usercentrics is German and common in enterprise DACH, Consentmanager is the budget option).
The setup sequence is simple if you do it in order. Install the CMP and configure consent categories. Enable Advanced Consent Mode in the CMP dashboard. In Google Tag Manager, set up the default consent state (denied) and the update consent state that fires on the CMP's consent event. Verify with the Google Tag Assistant that consent signals reach Google before any tag fires. Wait 48 hours, then check Google Ads diagnostics for the "Consent Mode" status to confirm the signal is being received.
Common Mistakes B2B Advertisers Make
Running Basic Mode by accident. Many CMPs default to Basic Mode unless you explicitly toggle Advanced. The user clicks "set up Consent Mode v2", assumes it is configured, and never realizes they are blocking all tags on reject. Check your CMP's dashboard and verify the mode setting is on Advanced before anything else.
Forgetting the default state. Consent Mode requires a default consent state set to denied before any user interaction. If your GTM does not fire a default state, Google reads the absence of signal as inconsistent and modeling will not activate. The default state must come first in the data layer, then the update state comes when the user accepts or rejects.
Stopping at Consent Mode. Consent Mode is the foundation, not the full solution. Pair it with Enhanced Conversions (for first-party data matching on lost cookies) and, at higher budgets, server-side tracking (for browser-restriction bypass). For the full stack, see our B2B server-side tracking guide.
Conclusion
Consent Mode v2 is not a checkbox. It is a critical piece of Google Ads infrastructure that determines whether Smart Bidding sees 50% of your conversions or 75%. Run Advanced Mode, hit the modeling threshold (or consolidate countries until you do), use a certified CMP, and verify the consent signals are actually reaching Google. The setup takes a few hours, the impact lasts as long as the account runs, and the alternative is paying for Google Ads while half your data quietly disappears. For the broader strategy across all four layers of B2B conversion tracking, see our complete guide to conversion tracking with cookie consent.
Frequently Asked Questions
Do I still need Consent Mode v2 if my reject rate is very low?
Yes, even at a low reject rate, Consent Mode v2 is required for remarketing list eligibility in the EEA and for Google's continued audience features in EU campaigns. The compliance side is independent of the recovery side. If you sell to EU customers and run Google Ads, Consent Mode v2 in Advanced Mode is the safe default regardless of consent acceptance numbers.
What happens if I am below the 700-click threshold for modeling?
Modeling will not activate and you will only see observed conversions, not modeled ones. The fix is one of three options: consolidate country targeting so all EU traffic flows into one country/domain grouping, increase Google Ads budget to drive enough volume, or layer Enhanced Conversions on top of Consent Mode so that hashed first-party data still recovers conversions even without modeling. For B2B with narrow geographic focus, Enhanced Conversions is usually the more practical fix.
Can I use a homemade cookie banner instead of a paid CMP?
Technically yes, you can pass consent signals manually through the Google Tag Manager API. Practically no, it is not recommended. A homemade banner makes you responsible for consent capture, audit logging, and ongoing CMP compatibility with Google's changes, which arrive every few months. The 30 to 100 EUR per month for Cookiebot or Usercentrics is far cheaper than the engineering time you will spend maintaining a custom solution and the legal risk of a non-compliant banner.