/ Blog
Home Blog Contact Buddy Ads Builder Audit Engine

Google Ads conversion or GA4 - what is everyone using?

Tracking & Measurement

Use your native Google Ads conversion tag as your primary conversion action — the one Smart Bidding optimizes toward — and import GA4 events as secondary, observation-only actions for cross-channel reporting. Running both set to "Include in Conversions" simultaneously creates double-counting that inflates CPA figures and corrupts Smart Bidding signals. The two tools serve different purposes; assign them different roles.

Key takeaways

  • Native Google Ads conversion tags deliver signal to Smart Bidding in near real-time; GA4-imported conversions carry a 24–72 hour processing delay that can degrade bid optimization, especially on low-volume campaigns.
  • Setting both a native tag and a GA4 import as primary conversions for the same action double-counts conversions, causing Smart Bidding to underbid and producing untrustworthy CPA reporting.
  • GA4 imports are valuable as secondary, observation-only conversions for cross-channel journey analysis — not as the primary bidding signal for most accounts.
  • Enhanced conversions on your native tags are non-negotiable: they recover signal lost to cookie restrictions and typically surface 10–20% more conversion volume that Smart Bidding was previously missing.
  • A monthly reconciliation between Google Ads native conversions and GA4 goal completions — with a healthy variance of 10–25% — is the simplest way to catch measurement drift before it damages performance.
Key terms
Primary conversion action
A conversion action marked 'Include in Conversions' in Google Ads that Smart Bidding directly optimizes toward when setting bids.
Enhanced conversions
A Google Ads feature that sends hashed first-party customer data (email, phone) alongside a conversion tag to recover conversions lost to cookie restrictions.
GCLID
Google Click ID — a parameter automatically appended to landing page URLs by Google Ads to link ad clicks to subsequent conversion events.
Signal delay
The 24–72 hour processing lag between a GA4 conversion event firing and that data becoming available to Smart Bidding after import into Google Ads.
Deduplication
The process of ensuring a single real-world conversion event is counted only once across measurement systems, typically accomplished by passing a unique transaction ID.

Why does the conversion source you choose matter so much?

The conversion actions marked "Include in Conversions" in Google Ads are the direct input to Smart Bidding. [1] Maximize Conversions, Target CPA (now an optional target inside Maximize Conversions), and Target ROAS (an optional target inside Maximize Conversion Value) all bid based exclusively on that signal — not on GA4 data, not on your intuition. [2] Feed the algorithm a noisy or delayed signal and it optimizes toward the wrong outcome, regardless of how well the rest of the account is structured. This question came up in a recent r/googleads thread, framed as a simple either/or — but the real answer is about assigning each system the role it was built for. In accounts I manage, conversion source mismanagement has been a bigger drag on performance than bids, creative, or audience targeting combined.

How are native Google Ads conversion tags and GA4 imports technically different?

Native Google Ads conversion tags

A native Google Ads conversion tag fires directly on the conversion event and reports back to the Google Ads platform almost instantaneously. [3] Because the tag is tied natively to the Google Click ID (GCLID), there is no identity stitching required between the ad click and the conversion. [4] It supports view-through conversions, cross-device paths for signed-in Google users, and full enhanced conversions for web. Attribution windows and models are set entirely within Google Ads. [5]

GA4-imported conversions

When you import a GA4 conversion event into Google Ads, the data has already been processed through GA4's collection pipeline — introducing a 24–72 hour delay before it influences Smart Bidding. [7] GA4 uses a session-based, event-driven model with its own attribution logic (last non-direct click by default, with data-driven attribution available), which can diverge meaningfully from Google Ads' click-based attribution. [8] The import also inherits GA4's consent mode thresholds and data processing rules. [9]

Factor Native Google Ads Tag GA4 Import
Signal speed to Smart Bidding Near real-time (<1 hour typical) 24–72 hour delay
Attribution model Set in Google Ads (data-driven or chosen model) GA4's model, imported as-is
View-through conversions Yes, native No
Enhanced conversions Full support Partial (enhanced conversions for web only)
Cross-channel reporting Google Ads only Full multi-channel view in GA4
Deduplication complexity Low (single source) High (requires unique transaction IDs)
Best for Smart Bidding Yes — primary use case Secondary; use as observation
Best for business insights Limited Yes
Key Insight: The GA4 import delay is most damaging when a campaign generates fewer than 30–50 conversions per month. At that volume, Smart Bidding is already data-starved. Adding a 24–72 hour lag on top of low conversion volume means the algorithm is effectively steering blind. For low-volume advertisers, native tags are not optional — they are critical.

What is the right way to structure both systems together?

The correct mental model is not "one or the other" but "primary versus secondary." Use your native Google Ads conversion tag as the primary action Smart Bidding optimizes toward, and use GA4-imported events as observation-only actions for cross-channel measurement.

  1. Audit every conversion action. In Google Ads, go to Tools & Settings → Measurement → Conversions. Export the full list and flag every action with "Include in Conversions" set to Yes. Identify the source of each — native tag or GA4 import. If you have both for the same action both set to primary, that is your highest-priority fix.
  2. Designate native tags as primary. Purchase completions, lead form submissions, phone calls — set "Include in Conversions" to Yes only for the native-tag versions of these actions.
  3. Set GA4 imports to observation only. Change GA4-imported conversion events to "Don't include in Conversions." They will still appear in your All Conversions column for reference and reporting.
  4. Implement enhanced conversions on all native tags. Enhanced conversions use hashed first-party data — email, phone number — to recover conversions lost to cookie restrictions. [6] Accounts I work with typically see a 10–20% increase in reported conversion volume after implementation; that is real signal Smart Bidding was not previously receiving.
  5. Reconcile monthly. Compare Google Ads native conversions to GA4 goal completions for the same actions once a month. A variance of 10–25% is normal. Anything beyond 30% warrants a tagging investigation. For a structured approach, the marketing analytics auditor can surface discrepancies quickly.
Best Practice: Native Google Ads tag as primary (bidding signal) + GA4 import as secondary observation (reporting) is the gold standard. You get the fastest, cleanest Smart Bidding input and the analytical richness of GA4's cross-channel view — without sacrificing either.

When does it make sense to use GA4 imports as the primary conversion source?

GA4 imports as your primary source are the exception, not the rule, but there are legitimate scenarios where they provide a more complete conversion picture than a native web tag alone.

App + web journeys

If customers regularly start on mobile web and convert inside an app — or vice versa — GA4's unified user model, linked with Firebase, may capture more complete conversion paths than a native web tag. In these cases, importing Firebase-linked app conversions via GA4 can give Smart Bidding a more accurate view of what is driving business outcomes.

Long-cycle B2B with heavy organic and direct traffic

For accounts where the average path to conversion spans 30–90 days and involves five or more touchpoints, a last-click native tag dramatically undercounts assisted Google Ads conversions. GA4's data-driven attribution model, when imported, can credit upper-funnel touchpoints that a native tag would miss entirely. See how GA and Google Ads measure conversions differently for a deeper look at this dynamic.

Server-side tracking architectures

If your organization has built a server-side Tag Manager setup routing events through GA4 as the central collection point, using GA4 as the single source of truth and importing downstream can make architectural sense. The processing delay implications for bidding still apply, so this approach works best at higher conversion volumes.

Key Insight: Even in these edge cases, monitor the 24–72 hour signal delay against your conversion volume. If you are running <50 conversions per month, the lag compounds the data-starvation problem and native tags should be prioritized regardless of architecture.

Why is deduplication a bigger problem than most practitioners realize?

When both a native Google Ads tag and a GA4 tag fire on the same conversion event, two separate conversion records can reach Google Ads — one from the native tag directly, one through the GA4 import pipeline. Google's built-in deduplication logic uses the transaction_id parameter (or order_id for e-commerce) to collapse duplicates, but only when these parameters are passed consistently. [3] For lead generation without unique transaction IDs, deduplication is unreliable.

In accounts where both sources are set to primary without unique IDs, in-platform conversion counts can run 30–50% above actual business outcomes. Smart Bidding then believes it is hitting CPA targets it is not actually hitting — campaigns appear healthy in reporting while real revenue quietly declines against flat ad spend. I have audited accounts spending $50K+ per month that have been in this state for over a year. For more on how this problem surfaces in practice, see common Google Ads conversion tracking failures.

Common Mistake: Assuming Google automatically deduplicates everything perfectly. It does not — especially for non-transactional conversions like contact form fills, phone calls, and content downloads. Without unique transaction IDs, both sources set to primary will inflate conversion counts flowing into Smart Bidding, causing overbidding and wasted spend that is very difficult to diagnose after the fact.

What to do next

  1. Audit every conversion action this week. Export your full conversion action list from Tools & Settings → Measurement → Conversions. Flag every action marked "Include in Conversions," identify its source (native tag vs. GA4 import), and resolve any duplicates before making any bid strategy changes. Use the 250-point Google Ads audit engine to surface measurement issues systematically.
  2. Implement or verify enhanced conversions on all native tags. If enhanced conversions are not active, set them up under the conversion action settings in Google Ads and update your GTM tags to pass hashed customer data. Allow 2–4 weeks for the full impact to appear in reporting. [6]
  3. Set all GA4-imported conversions to observation only. Unless your account falls into one of the documented exceptions (app + web journeys, server-side architecture), flip GA4 imports to "Don't include in Conversions" in Google Ads. Keep them visible in the All Conversions column for reference.
  4. Add unique transaction IDs to every conversion tag fire. For e-commerce, pass order_id consistently in both your native tag and GA4 event. For lead gen, generate a server-side submission ID and pass it as transaction_id. This is what makes Google's deduplication logic actually work.
  5. Establish a monthly reconciliation cadence. Once a month, compare native Google Ads conversions to GA4 goal completions for the same actions. Document the variance. 10–25% is normal; beyond 30% means something in your tagging deserves investigation. For ongoing monitoring, the Buddy AI Google Ads agent can flag anomalies between audit cycles.

Frequently asked questions

Does the GA4 processing delay actually affect Smart Bidding in practice?

Yes, particularly for campaigns under 50 conversions per month or any campaign coming out of a learning phase. Smart Bidding ingests conversion data continuously; a 24–72 hour lag means recent bid adjustments are optimized on stale signal. At higher conversion volumes (>100/month), the delay is diluted across a larger dataset and becomes less critical — but it never disappears entirely.

How do I check whether I am currently double-counting conversions?

Go to Tools & Settings → Measurement → Conversions in Google Ads and look for any conversion action where both a native tag and a GA4 import for the same user action are set to "Include in Conversions." Then compare your Conversions column to All Conversions for the same period — a gap significantly larger than 15–25% often signals double-counting. A reliable conversion tracking setup eliminates this ambiguity at the source.

What variance between Google Ads conversions and GA4 goal completions is normal?

A variance of 10–25% is typical and expected, driven by differences in attribution models, session definitions, cross-device handling, and processing timing. Anything beyond 30% consistently warrants investigation — common causes include misfiring tags, deduplication failures, consent mode discrepancies, or a GA4 import that is still set as a primary conversion action alongside a native tag.

Should I use GA4 or native tags for phone call conversions?

Native Google Ads call conversion tracking is strongly preferred for phone calls. GA4 does not natively capture call conversions from Google Ads in the same way, and there is no reliable transaction ID to use for deduplication. Set up call conversions directly in Google Ads using the native call tracking feature, and treat any GA4 call data as supplemental reporting only.

Does enhanced conversions replace the need for GA4 imports?

No — they solve different problems. Enhanced conversions on native tags recover signal lost to cookie restrictions by using hashed first-party data, improving the accuracy and volume of your existing conversion tags. [6] GA4 imports provide cross-channel attribution across non-Google traffic sources. Enhanced conversions make your native tags better; GA4 imports make your reporting broader. Both are worth using in their correct roles.

What if my organization requires GA4 as the single source of truth for all conversion data?

That is a valid architectural decision, especially in server-side or enterprise setups. If GA4 must be the single source, import conversions into Google Ads from GA4 — but set clear expectations: the 24–72 hour signal delay will affect Smart Bidding performance, particularly for lower-volume campaigns. Compensate by ensuring conversion volume is high enough (>50–100/month per campaign) for the algorithm to function reliably despite the lag. See measuring success in Google Ads for broader measurement architecture guidance.

References

  1. Google Ads Help. “About conversion measurement.” Accessed Nov 10, 2026.
  2. Google Ads Help. “About Target CPA bidding.” Accessed Nov 10, 2026.
  3. Google Ads Help. “Set up your web conversions.” Accessed Nov 10, 2026.
  4. Google Ads Help. “Add a Google tag to your website.” Accessed Nov 10, 2026.
  5. Google Ads Help. “About conversion windows.” Accessed Nov 10, 2026.
  6. Google Ads Help. “About enhanced conversions.” Accessed Nov 10, 2026.
  7. Google Analytics Help. “Get started with attribution.” Accessed Nov 10, 2026.
  8. Google Ads Help. “About attribution models.” Accessed Nov 10, 2026.
  9. Google for Developers. “Consent mode overview.” Accessed Nov 10, 2026.
  10. Original community discussion: r/googleads thread on Reddit.

Related Reading

AI Disclosure: This article was generated with AI assistance based on a community discussion on Reddit r/googleads. Expert analysis and practitioner perspective by John Williams, Founder, AHMEEGO · Google Ads Practitioner with $350M+ in managed Google Ads spend. AI was used to draft and structure the content; all strategic recommendations reflect real campaign experience.