Your ads are approved. Your bids are competitive. Your budget isn't capped. But impressions dropped and nobody on the team can explain why.
If you're running B2B SaaS campaigns on Google Search or YouTube, there's a growing chance the culprit isn't your keywords, your creative, or your landing page. It's an account-level status called Limited Ad Serving. Google throttles your delivery without telling you what threshold you crossed or which auctions you lost. And most ops teams don't even know to look for it.
What Limited Ad Serving Actually Does
Google applies Limited Ad Serving as an account-level qualification status. The mechanism: Google reduces the number of auctions your account can enter. Your ads stay approved. Campaign settings look normal. But impressions shrink because you're excluded from auctions you'd otherwise qualify for.
The status can appear on Search, YouTube, and potentially other Google Ads surfaces. Google's own documentation describes it as a measure to protect users from advertisers who haven't established sufficient trust with the platform. What "sufficient trust" means in practice is where things get murky, because Google doesn't publish a specific threshold or scoring rubric.
That opacity is the core problem for ops teams. You can't instrument what you can't see.
Why B2B SaaS Teams Misdiagnose This
When impressions drop and ads are still approved, the instinct is to troubleshoot the usual suspects: keyword match types, bid strategy, quality score, creative fatigue. A paid media manager will burn two or three weeks testing new RSA variants before anyone checks whether the account itself is throttled.
But Limited Ad Serving isn't the only explanation for sudden impression drops, and that's where misdiagnosis cuts both ways. Before assuming you've been flagged, rule out these common causes first:
- Policy or account suspensions. Different from Limited Ad Serving. Check the "Account status" section under Billing & Payments and the Policy Manager for active violations.
- Billing or payment holds. A declined card or billing threshold issue can pause delivery without a visible campaign-level warning.
- Budget pacing artifacts. Google's daily budget pacing can suppress delivery mid-cycle, especially after a budget change. Check the "Budget" column for "Limited by budget" status.
- Targeting changes or audience shrinkage. A narrowed geo, a removed audience segment, or a keyword pause can mimic throttling.
- Auction inventory shifts. Seasonal demand drops or new competitors entering your auctions change impression share without any account-level flag.
The diagnostic gap: most teams monitor CTR, CVR, and CPA. Almost nobody monitors auction eligibility at the account-trust level. That's where the signal lives, but only after you've eliminated the more common explanations above.
The Qualification Signals Google Cares About
Google hasn't published a specific scoring model. But their advertiser verification documentation and support guidance point to a consistent pattern of trust signals:
- Advertiser verification status. Completing identity and business verification proactively is the single highest-leverage preventive step. Google's help documentation explicitly ties verification to ad serving eligibility.
- Brand clarity in ads and landing pages. Ambiguous branding, partner logos used as your own, or domains that mimic another company's name can raise flags. For SaaS teams running competitor conquesting or reseller-style campaigns, this risk is higher.
- Policy compliance history. Disapproved assets accumulate, even paused ones. Google crawls paused ads and can disapprove assets that haven't run in months if they violate current policy.
- Account maturity. Newer accounts are more exposed, though established accounts aren't immune.
The trade-off if you ignore this: fewer eligible auctions mean weaker top-of-funnel volume and higher effective CPAs on remaining traffic. That complicates CAC targets and pipeline forecasting in ways that look like a media-efficiency problem but aren't.
Run It This Week: A Diagnostic Before You Optimize
Before you touch bids or rewrite ads, run this 30-minute check:
- Check for the Limited Ad Serving notification. Log into Google Ads. Look for a banner at the account level or check the "Ad serving" status under the account-level notifications panel. If you previously dismissed it, contact Google Ads support and ask directly whether the status is active on your account.
- Rule out other causes. Check billing status, review recent targeting changes, and compare impression share trends against the "Lost IS (budget)" vs. "Lost IS (rank)" columns. A sudden spike in "Lost IS" that doesn't correlate with budget or bid changes is a stronger signal of eligibility-level throttling.
- Audit advertiser verification. Go to Tools & Settings → Verification. If you haven't completed identity and business verification, start now. This is the single most controllable variable.
- Review disapproved assets. Open the Policy Manager. Fix or remove every disapproved ad, including paused ones. Zero active disapprovals is the target.
- Scan for brand-ambiguity risk. Pull your top-spending RSAs. Does every headline make clear who the advertiser is? Does your landing page header show your brand, not a partner's?
The hypothesis (make it falsifiable): if we complete verification, clear all disapproved assets, and make brand identity explicit in RSA headlines and landing pages, then auction eligibility will stabilize within 30 days, because Google's qualification assessment weighs these trust signals.
Success = impression share recovery toward pre-drop baseline. Guardrail = CPA stays within 15% of current levels. Stop-loss = if impression share doesn't move after 30 days and the notification persists, escalate to Google Ads support with full documentation of changes made.
What Not to Over-Interpret
Not every impression drop is Limited Ad Serving. Seasonal demand shifts, competitive auction pressure, billing issues, and budget pacing changes can look similar. If your account isn't flagged, rewriting ads for brand clarity won't fix a keyword-coverage gap or a payment hold. Diagnosis first, always.
And because Google hasn't published prevalence data or specific impact ranges, treat any claim about "how common" this is or "how much traffic you'll lose" with skepticism. Anecdotal reports from agency forums vary wildly, and none of them constitute official data.
If you only change one thing, change this: add a monthly check of your account-level notification panel and verification status to your ops review cadence. It takes two minutes. The alternative is discovering a throttle weeks into a pipeline shortfall, after you've already burned cycles troubleshooting the wrong layer of the stack.
