If you've spent any time managing Google Ads campaigns, you've almost certainly hit this crossroads: your Tag Manager container has both a Google Ads conversion tag and a GA4 event firing on the same action, and you're staring at two different numbers wondering which one to actually use for bidding. This isn't a minor housekeeping question — the measurement source you designate as your primary conversion in Google Ads directly shapes how Smart Bidding allocates budget, which audiences get built, and ultimately whether your campaigns grow or slowly decay. Getting this decision right is one of the highest-leverage things you can do as a PPC practitioner.
Why This Question Matters More Than Most People Realize
A common question in the r/googleads community is framed as a simple either/or: native Google Ads conversion tags vs. importing from GA4. But the real answer is more nuanced, and the stakes are higher than a reporting preference. Google's Smart Bidding algorithms — Target CPA, Target ROAS, Maximize Conversions — are only as good as the conversion signal you feed them. A noisy, duplicated, or delayed signal can quietly destroy campaign performance over weeks or months, even when your cost-per-click and quality scores look healthy.
In my experience managing campaigns with significant spend across dozens of verticals, I've seen accounts where conversion source mismanagement was the single biggest drag on performance — not the bids, not the creative, not the audience. The measurement layer was poisoning the optimization layer.
Key Insight: Smart Bidding ingests your conversion data in near real-time. GA4-imported conversions carry an inherent processing delay (typically 24–72 hours for event data to fully resolve). For high-velocity campaigns spending $500+/day, this lag can meaningfully degrade bid optimization, particularly in the critical first few weeks of a campaign or after a major budget change.
Understanding the Technical Differences
Google Ads Native Conversion Tags
The native Google Ads conversion tag (the old gtag.js or GTM Google Ads Conversion Tracking tag) fires directly on the conversion event and reports back to Google Ads almost instantaneously. It tracks within Google's own attribution ecosystem, meaning it has full visibility into view-through conversions, cross-device paths involving signed-in Google users, and the specific ad click data tied to that conversion. The tag sends data directly to the Google Ads platform without a middle layer.
Key characteristics:
- Fastest signal delivery to Smart Bidding (often sub-hour)
- Tied natively to Google click ID (GCLID) — no stitching required
- Supports enhanced conversions for better identity resolution
- Can capture view-through conversions out of the box
- Attribution window is set and controlled entirely in Google Ads
GA4-Imported Conversions
When you import a GA4 conversion event into Google Ads, you're pulling data that has already been processed through Google Analytics 4's collection pipeline. GA4 uses a session-based, event-driven model that behaves differently from Google Ads' click-based attribution. The import process introduces a processing delay, and some nuances in how GA4 handles sessions, cross-domain traffic, and user identity can result in conversion counts that diverge from what native tags report.
Key characteristics:
- 24–72 hour processing delay before data flows into Smart Bidding
- Relies on GA4's session attribution model (last non-direct click by default)
- Excellent for cross-channel reporting and customer journey analysis
- Respects GA4's consent mode and data thresholds
- Can surface conversions that native tags miss (e.g., app conversions, offline imports via GA4)
The Comparison That Actually Matters
| Factor |
Google Ads Native Tag |
GA4 Import |
| Signal speed to Smart Bidding |
Near real-time (<1 hour typical) |
24–72 hour delay |
| Attribution model |
Data-driven (or chosen model) within Google Ads |
GA4's own attribution (imported as-is) |
| View-through conversion support |
Yes, native |
No |
| Enhanced conversions support |
Yes, full support |
Partial (via enhanced conversions for web) |
| Cross-channel reporting |
Google Ads only |
Full multi-channel view in GA4 |
| Deduplication complexity |
Low (single source) |
High (requires careful setup) |
| Best for bidding optimization |
Yes |
Secondary use case |
| Best for business insights |
Limited |
Yes |
My Recommended Setup: Use Both, But Know Their Roles
As practitioners often discuss across the PPC community, the framing of "one or the other" is the wrong mental model. The right approach is to run both in parallel but assign them very deliberately different roles.
Best Practice: Use your Google Ads native conversion tag as your primary "Conversion" action (the one Smart Bidding optimizes toward). Use GA4-imported events as secondary "Observation" conversions for reporting and cross-channel analysis. This gives you the fastest, cleanest bidding signal while preserving the analytical richness of GA4 data.
Step-by-Step: How to Structure Your Conversion Actions
- Audit your current conversion actions. In your Google Ads account, go to Tools & Settings → Measurement → Conversions. Identify every action that has "Include in Conversions" set to Yes. Count them. If you have both a native tag and a GA4 import for the same action both set to "Include," you are almost certainly double-counting.
- Designate your primary conversion actions. Your primary conversions (the ones that feed Smart Bidding) should be native Google Ads tags or enhanced conversion tags — typically purchase completions, lead form submissions, phone calls. Set "Include in Conversions" to Yes only for these.
- Set GA4 imports to "Observation only." Change your GA4-imported conversion events to "Don't include in Conversions" (or set them as secondary actions). They'll still show in your all-conversions column for reference.
- Implement Enhanced Conversions on your native tags. This is non-negotiable in 2024. Enhanced conversions use hashed first-party data (email, phone) to recover conversions lost to cookie restrictions. Accounts using enhanced conversions typically see a 10–20% increase in reported conversion volume — and that's real volume Smart Bidding wasn't seeing before.
- Reconcile monthly, not daily. Compare your GA4 goal completions to your Google Ads native conversions once a month. Expect a 10–25% variance as normal. Anything beyond 30% is a signal to investigate your tagging.
Common Mistake: Setting both a native Google Ads tag AND a GA4 import for "Purchase" as primary conversions simultaneously. This creates double-counted conversion volume that inflates your reported CPA by up to 2x, causes Smart Bidding to underbid (because it thinks your CPA is better than it is), and produces reporting that is impossible to trust. I've audited accounts spending $50K+/month that have been running this way for over a year.
When GA4 Imports Make Sense as Primary Conversions
There are legitimate scenarios where importing from GA4 as your primary conversion source is the right call. These are the exception, not the rule, but they're worth understanding.
Cross-Device & App + Web Journeys
If your customers frequently start on mobile web, switch to desktop, and convert via an app — or vice versa — GA4's unified user model may actually capture more complete conversion paths than a native web tag alone. In these cases, GA4's Firebase-linked app conversions imported into Google Ads can give Smart Bidding a more complete picture of what's actually driving business outcomes.
Heavy Organic & Direct Traffic Overlap
In some business models (particularly B2B with long sales cycles of 30–90+ days), the "last Google Ads click" model dramatically undercounts assisted conversions. GA4's data-driven attribution model, when imported, can give credit to upper-funnel Google Ads touchpoints that a native tag would miss. For accounts where the average path to conversion involves 5+ touchpoints over multiple weeks, this matters.
Server-Side Tracking Architectures
If you've invested in server-side GTM and are routing events through GA4 as the central collection point, it can make architectural sense to use GA4 as the single source of truth for all conversion data and import downstream. Just be rigorous about the processing delay implications for bidding.
Key Insight: The GA4 import delay is most damaging for campaigns with fewer than 30–50 conversions per month. At that volume, Smart Bidding is already data-starved. Adding a 24–72 hour signal lag on top of low volume is like trying to drive by looking in the rearview mirror. For low-volume advertisers, native tags are absolutely critical.
The Deduplication Problem Nobody Talks About Enough
One of the most technically underappreciated issues in running both systems simultaneously is deduplication. When a user converts, both your native Google Ads tag and your GA4 tag fire. GA4 records the event. The GA4 conversion gets processed and imported into Google Ads. You now potentially have two conversions recorded for one actual business outcome.
Google has built-in deduplication logic that uses the transaction_id parameter (for e-commerce purchases) and the order_id to collapse duplicates — but this only works if you're passing these parameters consistently. For lead generation without unique transaction IDs, the deduplication is much less reliable.
How to Minimize Deduplication Issues
- Always pass a unique
transaction_id or order_id with every purchase conversion tag fire, in both your native tag and GA4 event.
- For lead gen forms, generate a unique submission ID server-side and pass it as the transaction ID in your conversion tag.
- If you're not passing unique IDs, make a deliberate choice: one system is primary for bidding, the other is for reporting only. Don't let both try to claim the same conversion.
- Review your "Conversions" vs. "All Conversions" columns monthly. A dramatic gap between the two often indicates deduplication 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, you can easily end up with 30–50% inflated conversion counts flowing into Smart Bidding, causing overbidding and wasted spend.
What This Means for Smart Bidding Specifically
Smart Bidding is a closed-loop system: the conversions you mark as primary become the optimization target, the system bids to get more of those conversions at your target CPA/ROAS, and then it uses the resulting conversion data to refine future bids. Feed it garbage, get garbage results. The quality and timeliness of your conversion signal is the single most important lever in this loop.
Here's how different setups affect Smart Bidding in practice:
- Native tags only (clean setup): Fastest signal, cleanest data. Smart Bidding has everything it needs. This is the baseline I recommend for most accounts.
- GA4 imports only: Acceptable if properly configured and you have high conversion volume (>100/month). The signal lag is less damaging at scale. Risky for low-volume accounts.
- Both set to primary (double-counting): Disaster scenario. Smart Bidding thinks it's hitting CPA targets it's not actually hitting. Campaigns look "healthy" in reporting while actual business outcomes deteriorate. I've seen accounts run this way for 6+ months before someone notices revenue declining against flat ad spend.
- Native primary + GA4 as secondary: The gold standard. Best of both worlds. You get accurate, fast bidding signals and rich cross-channel reporting.
What to Do Next: Your Action Plan
If you've read this far, you're probably already formulating what needs to change in your account. Here's the concrete action plan I'd give any practitioner inheriting or auditing an account with this setup:
- Audit every conversion action this week. Pull a full export from Tools & Settings → Conversions. Flag every action marked "Include in Conversions." Identify source (native tag vs. GA4 import). If you have duplicates, fix them before anything else — this is your highest-priority item.
- Implement Enhanced Conversions on all native tags. If you're not running enhanced conversions, you're leaving signal quality on the table. Set it up in Google Ads under the conversion action settings and update your GTM tags to pass hashed customer data. Expect 2–4 weeks to see the full impact in reporting.
- Set GA4 imports to secondary/observation status. Unless you have a specific architectural reason to use GA4 as primary (app+web journeys, server-side tracking), flip your GA4-imported conversions to "Don't include in Conversions" in Google Ads. Keep them for reference in the All Conversions column.
- Establish a monthly reconciliation cadence. Once a month, compare total conversions reported in Google Ads (native tags) vs. goal completions in GA4 for the same conversion actions. Document the variance. A healthy variance is 10–25%. Anything outside that range deserves investigation.
- Document your measurement architecture. Write down what's firing, from where, and why. This sounds basic, but in accounts with multiple contributors over time, the measurement layer becomes a archaeological dig. A simple Google Doc or Notion page describing every conversion action, its source, its role (primary vs. secondary), and the last audit date will save you hours of headaches down the road.
The bottom line is this: your native Google Ads conversion tags exist for a reason, and they're exceptionally good at what they do — feeding accurate, timely signals to Smart Bidding. GA4 is a powerful analytics platform that serves a different purpose. Forcing one to replace the other entirely means losing the strengths of both. Run them in parallel, assign them clear roles, prevent double-counting, and your measurement layer will become an asset instead of a liability.
