Google Ads Data Transmission Control is a setting, rolled out in January 2026, that lets you decide what data reaches Google when a user denies or limits advertising consent — from blocking advertising data entirely to transmitting limited data with identifiers redacted while still enabling conversion modeling (Google Ads Help). For a B2B SaaS lead-gen account, it is the control that decides whether Smart Bidding still gets a modeled conversion signal from consent-denied traffic or goes partially blind. This post explains what the control does, why the June 2026 consent change made it a performance lever and not just a compliance detail, and the exact setting most SaaS accounts should pick.
The context that makes this urgent: on June 15, 2026, Google made Consent Mode the single gate on whether GA4 data flows into Google Ads, with ad_storage becoming the key consent state governing advertising identifiers (Secure Privacy). After that change, a consent-denied user whose transmission control is not configured to allow limited modeled data simply disappears from your advertising signal. We cover the GA4 side of that split in the June 2026 GA4 and Google Ads consent split.
What Data Transmission Control actually is
Data Transmission Control is a layer that sits on top of Consent Mode, not a replacement for it. You must already have Basic or Advanced Consent Mode configured, because the transmission control cannot function independently — it only acts on the signals Consent Mode has already classified as granted or denied. It applies solely to Google tags and is configured through the Google Ads UI, which means it is a Google Ads setting a growth team can own, not a code change that always requires engineering.
When a user has not granted advertising consent, the control gives you two meaningful choices. You can transmit limited advertising data only — aggregate data with identifiers redacted — which preserves conversion modeling, or you can block advertising data entirely until consent is granted. Behavioral analytics can be allowed or blocked separately. The distinction matters because “consent denied” is not a small slice of traffic in the EU and UK; it is a large and growing share, and whichever option you pick is applied to all of it. This is the same first-party-data discipline that underpins Consent Mode v2 and enhanced conversions.
How to configure it, step by step
The setting lives in Data Manager, not the campaign settings most managers check daily, which is part of why it is easy to miss. The path is: open Data Manager, select Google Tag (Manage), then choose Manage data transmission. Enable Restrict advertising data transmission, and then select your transmission option.
For most B2B SaaS lead-gen accounts, the right option is Transmit limited advertising data only, which shares aggregate data with identifiers redacted when advertising consent has not been granted — keeping conversion modeling alive rather than losing the signal. The alternative, blocking advertising data outright, is the higher-compliance stance but costs you the modeled conversions. Because the control is UI-only and applies only to Google tags, confirm your Google tag is the one firing your conversions before you rely on it; accounts running conversions through a server container should cross-check against their server-side tracking setup so the two do not contradict each other (Leadgen Economy).
Block or transmit: the decision that has a performance cost
The choice between blocking and transmitting limited data is usually framed as a pure compliance question. It is not — it has a measurable performance cost, and marketing should be in the room when it is made. Blocking advertising data entirely when consent is denied is the conservative, strict-GDPR reading your legal or privacy team may prefer. Transmitting limited data with identifiers redacted keeps conversion modeling flowing so Smart Bidding continues to learn from consent-denied traffic.
For a low-volume B2B SaaS account, that difference can be decisive. Smart Bidding needs a minimum volume of conversions to optimise, and in privacy-restricted regions a large share of conversions are now modeled rather than observed. Block them and you can push a campaign below the threshold the algorithm needs — the same thin-data trap that undermines bidding in accounts with long sales cycles, which we cover in measuring pipeline from Google Ads. The decision should be deliberate and joint: if legal requires blocking, marketing should know the bidding cost it carries and plan around it, not discover it in a performance dip three weeks later.
Why this is a bidding issue, not just a privacy one
Smart Bidding is only as good as the conversion data it sees. When Google made Consent Mode the single authority over GA4-to-Ads data flow in June 2026, it concentrated the entire advertising signal through one gate — and Data Transmission Control is the valve on that gate. Set it to block, and the algorithm optimises on a thinner, systematically biased sample (only consented users), which skews bidding toward whatever segments happen to consent. Set it to transmit limited modeled data, and the algorithm sees a fuller, more representative picture.
This is why the setting belongs on a paid-search manager’s audit checklist, not buried in a privacy review. A B2B SaaS account that quietly switched to blocking after a consent-banner update can show a slow, unexplained decline in conversion volume and bidding stability with no campaign change to point to. The fix is to verify the transmission setting as part of your tracking foundation alongside your offline conversion stack. If you are not certain how your account is currently configured, a structured Google Ads audit will surface the transmission setting and the rest of your consent-era tracking, and the free 10-point audit checklist is a quick way to begin that review before anything else changes.