Google has moved conversion management out of Google Ads and into GA4, and the GA4-imported key event is now the default conversion source for new WooCommerce accounts. The default carries a 6–18 hour ingestion lag versus the Google Ads native tag — meaning Smart Bidding is optimising against yesterday’s customer behaviour by default unless your account explicitly chose otherwise. Most store owners haven’t noticed the default flipped.
The UI Change Most Operators Missed
The conversion management consolidation didn’t ship with a banner. It rolled out as a UI default — new Google Ads accounts now see GA4-imported key events as the recommended conversion source, with the native Google Ads tag relegated to an alternative path under “manage conversions.”
The two paths still work. Both still feed Smart Bidding. Both can be configured for Enhanced Conversions. What changed is which one Google’s onboarding flow sets up by default — and the default is what most stores actually run, because most stores trust the platform’s recommended setup and never revisit the choice.
The result is that thousands of WooCommerce stores are running GA4-imported conversions as their primary Smart Bidding signal without having explicitly chosen that architecture. They didn’t reject the native tag; they just took the default. And the default is now substantially different from what it was eighteen months ago.
Default no longer means safe. Default means whatever Google currently prefers to centralise.
The 6–18 Hour Latency Problem
The mechanical difference between the two paths is straightforward. The Google Ads native tag fires when the conversion happens — typically a thank-you page load — and reports to Google Ads inside minutes. The GA4-imported path fires the GA4 event first, GA4 ingests and processes the event, GA4 classifies it as a key event, and only then does GA4 export it to the linked Google Ads account.
Each of those steps adds latency. ALM Corp’s analysis of the imported-conversion path puts the typical lag at 6–18 hours. For Smart Bidding strategies that update bids based on conversion volume — Maximize Conversions, Target CPA, Maximize Conversion Value — that latency becomes the granularity at which the algorithm sees customer behaviour.
The strategy doesn’t fail. It just trains on stale data. Yesterday morning’s high-intent traffic shows up in this afternoon’s bids. Today’s high-intent traffic doesn’t enter the model until tomorrow.
Smart Bidding optimised against last-night’s customer is still Smart Bidding — just slower than the auction.
You may be interested in: Google Ads Collapses Enhanced Conversions Into One Toggle in June 2026
The Volume Threshold Most Stores Don’t Hit
The case for the GA4 import gets stronger at scale. GA4’s data-driven attribution model — the cross-channel credit-allocation engine that’s the main reason to centralise conversions in GA4 in the first place — requires 400 monthly conversions before it activates.
Below the threshold, GA4 silently falls back to last-click attribution. The data-driven model isn’t disabled with a notice; it’s just not active until enough data accumulates. Stores that imported conversions specifically to access data-driven attribution and then run under 400 conversions per month are paying the latency cost of the import path without getting the attribution benefit they imported for.
The Smart Bidding side has its own threshold. Most strategies need 30–50 monthly conversions to calibrate properly. Stores below 30 conversions per month fight a continuous warm-up problem regardless of which source they use. Above 30 but below 400, the native tag is usually the better fit. Above 400 with cross-channel attribution needs, the GA4 import starts to earn its place.
The decision becomes a function of volume:
- Under 30 monthly conversions: Smart Bidding is undertrained either way; focus on volume before architecture.
- 30–400 monthly conversions: Native Google Ads tag plus Enhanced Conversions usually wins on latency without losing meaningful attribution depth.
- 400+ monthly conversions with multi-channel spend: GA4 import unlocks data-driven attribution; the latency cost is real but the cross-channel credit allocation often outweighs it.
The Configuration Failure Mode That Beats Both Paths
SR Analytics’ audit data on GA4 implementations puts a hard number on the underlying risk. 73% of GA4 implementations have silent misconfigurations causing 30–40% data loss. The misconfigurations don’t surface as errors — the dashboards still populate, the numbers still reconcile within their own world — but the underlying data is incomplete.
If 73% of GA4 implementations are silently broken at the source, then 73% of GA4-imported conversions to Google Ads are inheriting that brokenness. Smart Bidding then trains on the broken signal, and the bidding model converges on the subset of customers GA4 happened to see correctly.
The native Google Ads tag has its own failure modes — duplicate firing, GTM tag-firing race conditions, consent-mode misconfigurations — but they tend to be more visible because they live closer to the conversion event. GA4 misconfigurations sit upstream and propagate downstream silently.
groas.ai’s audit guidance notes the same Enhanced Conversions lift — 5–15% additional reported conversions — applies to both paths. The configuration discipline matters more than the source choice in practice.
You may be interested in: The Eight Hops a WooCommerce Conversion Has to Survive
The Architecture That Stops the Choice
The native-tag-vs-GA4-import question is a forced choice only if both paths originate from the browser. Server-side first-party tracking removes the choice entirely.
The architecture works like this. WooCommerce events fire once, captured server-side as the source of truth. The server-side pipeline then routes the event in parallel:
- To Google Ads via the Conversions API or Enhanced Conversions endpoint, with the original timestamp and event ID.
- To GA4 via the Measurement Protocol, with the same event ID for deduplication.
- To the store’s own warehouse — BigQuery, Postgres, wherever — for full-audience analysis.
Google Ads receives the event in seconds, not 6–18 hours. GA4 receives the same event for cross-channel attribution. The store has the raw data for its own modelling. The native-tag-vs-GA4-import decision becomes a reporting preference rather than a Smart Bidding architecture decision.
Here’s How You Actually Build This on WordPress
Transmute Engine™ is a first-party Node.js server that runs on your subdomain. The inPIPE WordPress plugin captures WooCommerce events and sends them via API to Transmute Engine, which fans out the same event to Google Ads, GA4, Meta CAPI, and your BigQuery dataset simultaneously. The latency to Google Ads stays in the seconds-not-hours range, and the GA4 path keeps the cross-channel attribution benefits without becoming the bottleneck for Smart Bidding.
Key Takeaways
- Google flipped the default conversion source for new Google Ads accounts from the native tag to GA4 imports — most stores never noticed.
- GA4-imported conversions carry a 6–18 hour ingestion lag, which becomes the resolution at which Smart Bidding sees customer behaviour.
- GA4 data-driven attribution needs 400+ monthly conversions to activate; below that threshold it silently falls back to last-click.
- 73% of GA4 implementations have silent misconfigurations, and the imported-conversion path inherits those problems downstream.
- Server-side architecture stops the choice — fan out the same event to Google Ads, GA4, and your warehouse in parallel, with no latency penalty.
Frequently Asked Questions
It depends on three variables: monthly conversion volume, attribution-model preference, and consent-mode posture. Stores under 400 monthly conversions usually win with the native tag because GA4’s data-driven attribution silently falls back to last-click below the threshold, while the native tag still feeds Enhanced Conversions. High-volume stores using cross-channel attribution often prefer the GA4 import. The wrong default is letting Google decide for you — which is what’s happening on every new account.
Google has consolidated conversion management into GA4 as part of a broader centralisation across the Marketing Platform. New Google Ads accounts default to importing key events from GA4 rather than firing the Google Ads native tag directly. The shift is a UI default change — both paths still work — but most account owners haven’t realised the default flipped underneath them.
Yes, typically by 6–18 hours. GA4 ingests events, processes them, classifies key events, and then exports to Google Ads — each step adds latency. The native Google Ads tag fires directly when the conversion happens and reports near-real-time. For Smart Bidding, the latency means the algorithm trains on yesterday’s behaviour rather than the last few hours.
Enhanced Conversions runs alongside both conversion sources. It hashes first-party data from the conversion and matches it against signed-in Google users, recovering conversions that would otherwise be lost to consent denial or cross-device journeys. The 5–15% lift Enhanced Conversions typically produces applies whether the underlying source is the native tag or the GA4 import.
Server-side first-party tracking that captures WooCommerce events once and routes them in parallel to both Google Ads (via the Conversions API or Enhanced Conversions) and GA4 (via the Measurement Protocol). The store stops choosing because both pipelines receive the same source-of-truth event with the same timestamp. Latency drops, deduplication is straightforward, and the choice between native tag and GA4 import becomes a reporting question rather than a Smart Bidding question.
Audit which conversion source your account is actually using right now — most owners are surprised by the answer. Seresa builds the architecture that lets the choice stop mattering.
