Launch Offer2 free audits with all 229 checks. No credit card required.Start free audit

Smart Bidding and GA4 Key Events: The Data Sufficiency Threshold (2026)

Intermediate

How many conversions does Smart Bidding need?

Google's published thresholds for Smart Bidding to operate effectively in 2026: Target CPA bidding requires 30+ conversions in the past 30 days per campaign, Target ROAS requires 50+ conversions, Maximize Conversions and Maximize Conversion Value need at least 15+ conversions for stable performance.

Below these thresholds, Smart Bidding's machine learning model lacks training data and either holds bids in a learning phase (visible as "Limited - data" status in the campaign UI) or reverts to behaviour close to broad-match bidding. The 7-day learning period after any significant change (bid strategy switch, budget change >20%, target adjustment) further compounds the data sufficiency challenge.

Combined with the GA4 ↔ Google Ads conversion import lag and Consent Mode V2 acceptance rates, the practical conversion threshold is often higher than Google's published numbers.

The published thresholds

Google's official guidance per bid strategy:

Bid strategyMin conversions per campaignLookback windowNotes
Target CPA30 conversionsPast 30 daysRecommended for steady-volume conversion goals
Target ROAS50 conversionsPast 30 daysRequires conversion values; needs more volume than tCPA
Maximise Conversions15 conversionsPast 30 daysUseful below tCPA threshold
Maximise Conversion Value15 conversionsPast 30 daysUseful below tROAS threshold for value-aware bidding
Enhanced CPCNone publishedn/aLegacy, less effective than full Smart Bidding

These are minimums. Stable performance typically requires 2–3x these numbers — a campaign at exactly 30 conversions may meet the minimum but produce volatile bid behaviour. The "Limited by Budget" or "Limited - data" status in Google Ads campaign reports is your warning indicator.

What "30 conversions per campaign" actually means

The threshold counts conversions from Google Ads' perspective, not GA4's:

  • Conversions imported from GA4 via the Ads ↔ Analytics link count
  • Native Google Ads conversion tracking counts
  • Conversions from before the bid strategy was activated count toward the threshold but don't help the model learn
  • Modelled conversions (conversions reconstructed from cookieless pings) count

So a campaign with 25 observed conversions + 8 modelled conversions = 33 conversions total = above tCPA threshold.

This matters because Consent Mode V2 directly affects Smart Bidding eligibility. Properties with low V2 acceptance (under 60%) lose modelled conversions and may fall below threshold even when raw observed conversions seem sufficient.

The 7-day learning period

Whenever a campaign undergoes a significant change, Smart Bidding enters a 7-day learning period:

  • Bid strategy switch (manual to tCPA, tCPA to tROAS, etc.)
  • Target value change (tCPA goal up/down by >15%)
  • Budget change of >20%
  • Major audience or geographic expansion
  • New conversion event added or removed

During learning:

  • Bids may be unstable
  • CPA/ROAS targets are aspirational, not enforced
  • Volume can fluctuate significantly
  • Performance compared to pre-change is misleading

Stakeholders need to know: don't make decisions based on the first 7 days after a Smart Bidding change. Annotate the change date in your dashboards. Compare performance to pre-change only after 14 days have passed.

The four data quality requirements

Beyond raw volume, Smart Bidding requires conversion data quality:

1. Conversion event must be marked as a key event in GA4

For GA4-imported conversions to feed Smart Bidding, the event must be marked as a "key event" in GA4 (formerly "conversions"). Admin → Events → toggle "Mark as key event" on.

Common bug: a custom event that should be feeding Smart Bidding isn't marked as a key event, so the import doesn't work. Check this if Google Ads doesn't see conversions you expect.

Want to see whether attribution loss is already distorting your channel data?

2. Cross-account conversion import enabled

The GA4 ↔ Google Ads link must be configured for cross-account conversion import. Admin → Product links → Google Ads links → Configure → Enable "Personalised advertising" and "Conversion import."

Without this, Smart Bidding only sees Google Ads' native conversions (from gtag-based conversion tags), not your GA4 events.

3. Conversion values must be present and consistent

For tROAS and Maximize Conversion Value, every conversion needs a value. Conversions firing with value: 0 or missing values:

  • Are still counted toward conversion volume
  • Are NOT useful for tROAS optimization
  • Drag down the average conversion value the algorithm learns

The fix: ensure every important conversion event includes a value parameter. For lead-gen, assign monetary value to leads (e.g., £100 per qualified lead based on close rate × deal size).

4. Latency from conversion to import

Smart Bidding learns most effectively when conversions are reported quickly. The standard GA4 → Ads import has 12–48 hour lag — fine for stable Smart Bidding but problematic for quickly changing campaigns.

For latency-sensitive campaigns, two options:

  • Enhanced Conversions — fires conversions in real time with hashed user data
  • Offline conversion import — for offline conversions like sales calls, import within 90 days via the Google Ads API

What happens below threshold

Common patterns when campaigns are below conversion threshold:

Pattern A — "Limited - data" status. The campaign UI shows this status. Smart Bidding still operates but with reduced confidence. Bids are conservative; volume may be capped below budget.

Pattern B — Manual-CPC-like behaviour. Without enough learning data, the algorithm reverts to behaviour patterns close to broad-match manual bidding. Spend continues but optimisation lift over manual is minimal.

Pattern C — Volume volatility. Some days the campaign spends full budget; others it spends almost nothing. The algorithm hasn't learned which queries to bid on.

Pattern D — High learning-period CPA. First 30 days after activation can show CPA 2–3x your target as the algorithm explores. Some learning is necessary; persistent overshooting indicates insufficient data.

The remediation playbook for under-threshold campaigns:

  1. Aggregate conversion events. Instead of "demo_request" + "trial_signup" + "contact_form" as separate conversions, treat them all as a single "lead" conversion event. Combined volume hits threshold.
  2. Use Maximize Conversions instead of tCPA. Lower threshold (15 vs 30), more flexible.
  3. Loosen geographic or audience targeting to increase conversion volume — at the cost of less precise targeting.
  4. Wait for volume to grow naturally if the business is scaling.
  5. Stay on manual or Enhanced CPC as last resort if Smart Bidding genuinely can't get enough data.

How to check Smart Bidding health

Five-step health check:

  1. Google Ads → Campaigns → look at the Status column. "Limited" or "Eligible (Limited)" warnings mean data sufficiency issues.
  2. Click into each campaign → Settings → Bid strategy section. Shows current learning phase status if active.
  3. Check the conversion volume per campaign per 30 days. Compare to threshold for the bid strategy.
  4. In GA4, verify the events feeding Ads are marked as key events. Admin → Events.
  5. Check the GA4 ↔ Ads link. Confirms conversion import is active.

Run this monthly. The "Limited" status often appears silently after seasonal volume drops or budget changes.

FAQ: Smart Bidding and GA4 Key Events: The Data Sufficiency Threshold

What should a team validate first when smart bidding and ga4 key events: the data sufficiency threshold appears?

Reproduce the problem in the live implementation, isolate whether it is scoped to one report or flow, and compare it against at least one secondary source before changing the setup.

How do I know whether the fix actually worked?

You need before-and-after evidence in the browser and in the downstream report. A clean-looking dashboard without validation is not enough.

When should this become a full GA4 audit instead of a quick fix?

If the issue touches attribution, consent, revenue, campaign quality, or data trust for more than one workflow, it is usually safer to audit the surrounding implementation than patch only the visible symptom.

Check Smart Bidding and GA4 Key Events: The Data Sufficiency Threshold before campaign reporting gets blamed for the wrong issue

Run a free GA4 audit to spot attribution breaks, UTM governance issues, self-referrals, and source/medium loss fast.

These findings come from auditing thousands of GA4 properties. See how your property compares

GA4 Audits Team

GA4 Audits Team

Analytics Engineering

Specialising in GA4 architecture, consent mode implementation, and multi-layer audit frameworks.

Share