Why GA4 Imports Can Break Smart Bidding (And How to Fix It)

What Smart Bidding actually trains on

Smart Bidding — Target CPA, Target ROAS, Maximise Conversions, Maximise Conversion Value — learns by identifying patterns in the auction signals that preceded conversions. It needs conversions to learn from. The accuracy of those conversions as a signal is the most important variable in whether the algorithm performs.

Every conversion action in Google Ads has one critical setting: Include in Conversions. When set to ON, the action is Primary — it feeds the Conversions column and Smart Bidding optimises toward it. When set to OFF, the action is Secondary: it records data and appears in your All Conversions column for attribution analysis, but Smart Bidding does not use it as a target.

The default path when linking GA4 to Google Ads sets imported events to Include in Conversions ON. Many accounts that use this path end up with a GA4 import as their only Primary signal and no native Google Ads tag at all. If a native tag is never implemented, Smart Bidding trains entirely on GA4’s output. That may be acceptable as a temporary setup, but the further GA4’s modelled numbers diverge from actual business outcomes, the more the algorithm trains on the gap.

Correct conversion architecture

Signal How Google Ads gets it Attribution method Include in Conversions

          Native Google Ads tag (GTM)
          Fires on purchase page in user’s browser, on the actual click
          Click-based — observed directly
          ON — Primary
        

GA4 import Pulled from GA4 property via linked account GA4 event import, processed through GA4 attribution and modelling where applicable OFF — Secondary

For Google Ads bidding, the native Google Ads tag is usually the cleanest primary optimisation signal. The GA4 import remains useful for full-funnel reporting, attribution comparison and audience building — but not as the primary bidding signal when a native tag is available.

When can a GA4 import be Primary?

If no native Google Ads tag exists yet, a GA4 import may be better than having no conversion signal at all — Smart Bidding needs something to train on. Treat it as a transitional setup. Once a native tag or clean offline conversion import is in place, move the GA4 import to Secondary and use it for reporting and attribution comparison.

Native tags vs GA4 imports: what the difference actually is

A native Google Ads conversion tag fires in the user’s browser, on the specific page you nominate — typically the order confirmation or thank-you page. It records a conversion within Google Ads’ own click-to-conversion measurement path, at the moment of the event. This keeps the conversion close to the ad click that preceded it.

GA4 imports take a different path. Before reaching Google Ads, the conversion passes through GA4’s event collection, attribution, and modelling layer. GA4 uses cross-device joining, consent-state modelling, and data-driven attribution to reconstruct what it estimates happened across a user’s full journey. That is a more complete picture of customer behaviour — but it is also further removed from the clean click-to-conversion signal that Smart Bidding is designed to train on.

Neither signal is inherently wrong. Under optimal conditions — full consent, single-device, clean implementation — GA4’s numbers will be close to the native tag. Under real-world conditions — iOS privacy restrictions, consent mode modelling gaps, cross-device journeys — they can diverge. GA4 may over-count (modelling fills gaps generously), under-count (consent restrictions reduce what is directly observable), or attribute the same purchase differently than Google Ads’ own tracking.

GA4 imports are valuable for full-funnel reporting, multi-touch attribution analysis, and building audiences. The practical limitation is as a Smart Bidding primary signal: the algorithm will train on whatever number GA4 reports, including the estimated components. A native Google Ads tag keeps that signal closer to Google Ads’ own measurement system.

Three ways GA4 imports corrupt Smart Bidding signals

The problem takes three distinct forms depending on how the account is set up. Most accounts have at least one of them.

GA4 import set as Primary with no native tag

The most common version. GA4 is linked to Google Ads, the purchase event is imported, it defaults to Include in Conversions ON, and nobody implements a native Google Ads tag. Smart Bidding trains entirely on GA4’s modelled output.

The account looks fine on paper in the short term. CPA holds, the bidding strategy stays in the learning phase briefly and then stabilises, conversions report consistently. What shifts, usually over weeks or months, is efficiency. ROAS softens. The new customer mix drifts toward people who were already likely to buy. Impression share on competitive terms drops without an obvious cause.

By the time the gap is identified, Smart Bidding has been training on a signal that does not perfectly reflect actual business outcomes. The model carries that history even after the conversion architecture is corrected — it takes time to retrain on the improved signal.

✕ Common wrong setup

GA4 — Purchase (imported) Primary ↑

No native tag in the account. Smart Bidding trains entirely on GA4’s modelled output. The algorithm has no native Google Ads conversion tag as its primary signal.

✓ Correct setup

Google Ads tag — Purchase (GTM) Primary ↑

GA4 — Purchase (imported) Secondary

Native tag provides the observed signal. GA4 import stays in All Conversions for reporting and attribution analysis. Smart Bidding trains on the observed data.

Both GA4 import and native tag set as Primary (double counting)

A more fragile version. The account has a native Google Ads tag and a GA4 import, both set to Include in Conversions ON. Smart Bidding now sees two Primary conversions for some purchases: the observed tag and the GA4 model. Conversions are counted twice in the Conversions column for purchases that both signals capture.

The effect on bidding: Smart Bidding interprets these double-counted events as a success signal. The algorithm over-optimises toward auction patterns that appear to produce two conversions, anchoring bid decisions to an artificially inflated CPA floor.

Identifying this: compare the Conversions column in Google Ads against actual order volume in your ecommerce platform for the same date range. Some natural variance exists — cross-device journeys, different attribution windows — but a ratio significantly above 1:1 is a signal of structural duplication. You can also check by looking at the Source column in your Conversions table: if you see both Google Analytics and Website for the same event category, both may be Primary.

Non-purchase events included as Primary conversions

The hardest to catch. A GA4 import includes engagement or browse events — view_item, add_to_cart, begin_checkout — set to Include in Conversions ON alongside the purchase event. Smart Bidding now treats a product view or add-to-cart as an equivalent success signal to a completed purchase. The Conversions column becomes a mix of real purchases and engagement events, and the algorithm optimises toward all of them equally.

In real account audits, the distortion can be severe. A view_item event on an ecommerce site can fire hundreds of times per session across multiple pages — if that event is set to Primary, it can represent 80–90% of the Conversions column, with actual purchases making up the remainder. Smart Bidding trained on this signal is effectively optimising for product browsing rather than purchase.

The fix is immediate: go to Tools & Settings → Measurement → Conversions in Google Ads, and check every action showing Include in Conversions ON. Turn off anything that is not a completed purchase or the specific macro-conversion you want the campaign to drive. Engagement events and micro-conversions belong in the Secondary (All Conversions) column only.

How to diagnose the problem in your account

The quickest way to identify which version you have is to audit the Conversions table directly. Navigate to Tools & Settings → Measurement → Conversions. This lists every conversion action, its source, and whether Include in Conversions is ON or OFF.

Diagnostic reference

What you see Likely cause First action

Only GA4 imports showing Include in Conversions ON, no native tag Smart Bidding has no native Google Ads tag as its primary signal — only GA4’s processed output Implement native GTM tag, then demote GA4 import to Secondary

Both a native tag AND a GA4 import showing ON for the same event Duplicate counting — some conversions appearing twice in Smart Bidding target Set the GA4 import to OFF (Secondary). Keep native tag ON.

Conversion column volume is much higher than actual order count Browse or micro-conversion events (view_item, add_to_cart) set to Primary Check each ON action by category. Set non-purchase events to OFF.

CPA holds but ROAS softening over several months Model drift — Smart Bidding trained on modelled signal, optimising for approximations Audit conversion architecture, fix signal quality, allow 14+ days to retrain

Conversion column shows only one GA4 import and no other actions No native tag in account — common post-GA4-link account setup Add a native Google Ads purchase tag via GTM as a priority

How to fix it

Three steps. The first two are the critical path — do them in order. The third improves measurement coverage but is not a blocker.

Demote GA4 imports to Secondary

In Google Ads: Tools & Settings → Measurement → Conversions. Click each GA4-imported conversion action, then Edit settings. Set Include in Conversions to OFF.

Do the same for any micro-conversion events — add_to_cart, view_item, begin_checkout, sign_up — that are currently set to ON. These events belong in the Secondary column. They still record and appear in All Conversions for reporting, but they are removed from the Smart Bidding signal.

Important: if you demote all Primary actions before a native tag is in place, Smart Bidding will enter a learning phase with no conversion signal to optimise toward. If the GA4 import is currently your only Primary signal and you have no native tag yet, implement the native tag first (step 02), confirm it is recording correctly, then demote the GA4 import. Do not leave Smart Bidding without any Primary conversion action.

Implement a native Google Ads conversion tag via GTM

In Google Ads: Tools & Settings → Measurement → Conversions → New conversion action → Website. Set the category to Purchase, enter a conversion name, and set the value to use a variable (dynamic conversion value). Note the Conversion ID and Conversion Label that are generated.

In GTM, create a new tag of type Google Ads Conversion Tracking. Enter the Conversion ID and Conversion Label from the step above. Set the Conversion Value to your transaction revenue data layer variable (e.g. {{DLV - transaction_revenue}}). Set the trigger to fire on your purchase confirmation or thank-you page — this should be a page that is only visible after a successful transaction.

Once published, this tag fires in the user’s browser on the actual purchase page, on the actual click from Google Ads. In Google Ads, ensure this action is set to Include in Conversions ON. This is now your Primary signal — the one Smart Bidding trains toward.

For lead generation accounts, the same principle applies: optimise toward the deepest reliable macro-conversion available. A native form-submission tag is usually the right starting point. If CRM data is available and GCLID matching is reliable, a clean offline qualified-lead import can be a stronger Primary signal than a form-submit alone — because it reflects lead quality, not just lead volume. GA4 form-submit events should remain Secondary in the same way GA4 purchase events should for ecommerce.

For a step-by-step walkthrough of the full conversion tracking setup and common errors, see the conversion tracking fix guide.

Enable Enhanced Conversions on the native tag

Enhanced Conversions supplements the native tag by sending a hashed first-party data signal — typically a hashed email address from the purchase confirmation page — alongside the conversion event. When Google can match that hash to a signed-in Google account, it can attribute conversions that would otherwise be missed due to cookie restrictions, ITP, or iOS privacy controls.

To enable it: in Google Ads, go to Tools & Settings → Measurement → Conversions → select your primary purchase action → Enhanced conversions → Turn on. Choose the GTM setup method. In GTM, you will need to add the Enhanced Conversions variables — typically the customer’s email address pulled from the confirmation page and hashed using SHA256 before sending.

Enhanced Conversions does not replace the observed tag. It extends the coverage of that tag into environments where cookies are restricted. The result is more complete conversion measurement without changing the fundamental architecture: native tag primary, GA4 import secondary.

What to expect after the fix

Smart Bidding retrains when the conversion signal changes. After setting the GA4 import to Secondary and establishing the native tag as Primary, expect a learning phase. During this period, Smart Bidding is re-calibrating to the new signal — bids may fluctuate and conversion volume may look different from the previous baseline.

The Conversions column will likely report fewer conversions than before if you have removed micro-conversions from the Primary set. That is the number correcting to reflect actual purchases rather than a mix of purchases and engagement events. The All Conversions column will continue to show the full picture.

ROAS reporting may also shift. If the GA4 import was over-counting conversions (due to modelling), CPA will appear to increase once the observed signal replaces it. This is measurement accuracy, not performance decline — you are now seeing what was actually happening rather than the model’s interpretation of it. Give the account 14 days before drawing conclusions.

2026 Context

Consent Mode and the modelling gap

With Consent Mode v2, Google models conversions for users who decline analytics or ad cookies. This modelling — sometimes called behavioural modelling — attempts to estimate the conversions that occur in the cookieless portion of your traffic based on patterns from users who did consent. The result is that your GA4 conversion totals include both directly observed events and Google’s probabilistic estimates for users it cannot directly track.

This modelling is useful for understanding the true scale of your conversions. For Smart Bidding, a native Google Ads tag keeps the conversion event within Google Ads’ own measurement path — closer to the ad-click-to-conversion signal the algorithm is designed to train on. Consent Mode still matters: consent state can affect what tags observe directly versus what is estimated. Enhanced Conversions can improve coverage where consented first-party data is available, supplementing the native tag rather than replacing it. If you are relying on GA4’s modelled output as your only Primary signal, each additional modelling layer — consent state, cross-device, attribution — adds further distance from the actual transaction. For more on tracking architecture and common gaps, the conversion tracking guide covers the full diagnostic.

FAQ

What does “Include in Conversions” mean in Google Ads? +

Include in Conversions is the setting that determines whether a conversion action is Primary or Secondary. When set to ON, the action feeds into the Conversions column and is used as Smart Bidding’s optimisation target. When set to OFF, the action is Secondary: it still records and appears in the All Conversions column for reporting, but Smart Bidding does not use it as a target. This single setting controls what the algorithm trains on.

Will turning off GA4 imports hurt my conversion reporting? +

No — setting a GA4 import to Secondary (Include in Conversions OFF) does not delete the data. The import continues to record and the conversion count remains visible in your All Conversions column. The only change is that Smart Bidding stops using it as its primary target. You lose nothing from a reporting perspective; you gain a cleaner bidding signal.

How do I know if Smart Bidding is training on the right signal? +

Go to Tools & Settings → Measurement → Conversions. Look at the Include in Conversions column. Every action showing ON is feeding Smart Bidding. If any of those are GA4 imports, engagement events (view_item, add_to_cart), or micro-conversions, that is the problem. The correct state: one Primary action showing ON — your native Google Ads purchase tag. Everything else OFF.

What is Enhanced Conversions and do I need it? +

Enhanced Conversions supplements your native Google Ads tag by sending hashed first-party data (typically a hashed email from the purchase confirmation page) alongside the conversion. When Google can match that hash to a signed-in Google account, it fills in attribution gaps caused by cookie restrictions and iOS privacy controls. It does not replace the native tag — it works alongside it. For most ecommerce accounts, enabling it when you set up the native tag is worth doing.

My GA4 conversion count is much higher than my actual orders — why? +

The most common cause is that non-purchase events have been imported from GA4 and set to Include in Conversions ON. Events like view_item, add_to_cart, or begin_checkout count as conversions in the Conversions column if they are set to Primary. Browse events can outnumber completed purchases many times over. Go to Tools & Settings → Measurement → Conversions, check each action set to Include in Conversions ON, and turn off anything that is not a completed purchase.

Lewis Phillips Performance marketer · 11 years

I audit Google Ads accounts across ecommerce and lead generation. GA4 imports sitting as the Primary conversion action — with no native tag — is the single most common measurement error I find. This guide reflects what that looks like in practice and what fixing it actually involves.

LinkedIn →