New Google Ads Conversion Action Shows Zero? The 4-6 Hour Rule

TL;DR

You created a Google Ads conversion action, connected your Shopify tracking, maybe placed a test order, and the conversions column reads zero. Before touching anything: Google's own documentation says to wait 4-6 hours after creating a conversion action before uploading conversions to it [1], and its API rejects earlier upload attempts outright [2]. That clock starts at action creation and is separate from the reporting-freshness clock (about 3 hours for last-click data [3]) and the click-recency clock (clicks under 6 hours old cannot be matched yet [4]). A test order placed ten minutes after setup trips all three at once. This article walks the zero-conversions panic in wall-clock order: what is normal at 30 minutes, at 6 hours, at 24 hours, and what genuinely needs fixing after that.

Key Takeaways

• Google instructs advertisers to wait 4-6 hours after creating a conversion action before uploading conversions; its API troubleshooting guide says to wait at least 6 hours before retrying rejected rows [1] [2].
• Conversions uploaded during that initial window can take around 2 days to appear in reports even when accepted [1].
• Two more clocks stack on top: a click less than 6 hours old cannot be matched yet, and a conversion within one day of its click may not be recorded yet [4] [5].
• Normal reporting freshness once everything is eligible: about 3 hours for the last-click attribution model, up to about 15 hours for other models [3].
• Offline-import processing typically completes in under 12 hours, but can take up to 72 hours for conversions keyed on gbraid or wbraid identifiers [4].
• "Unverified" means the conversion tag has never been seen firing; Google's troubleshooting guidance treats it as a problem when it persists beyond about 24 hours [6]. Import-type actions have no website tag to verify in the first place.
• A test order without a paid ad click carries no Google click ID, so with default settings there is nothing to import, no matter how long you wait.

Why does a brand-new conversion action show zero conversions?

Because the action itself is not eligible yet. Google states it plainly in its offline-conversion setup guide: "After creating a new conversion action, wait 4-6 hours before uploading conversions for that conversion action" [1]. The same instruction appears in the legacy file-import documentation [5], and the Google Ads API enforces it with a named error: a too-recent-conversion-action rejection, with guidance to "wait at least 6 hours after the action is created before retrying" [2].

The key distinction, and the one merchants conflate at the moment of panic: this is an eligibility gate on the action, not generic reporting lag. Reporting lag is a different clock that starts when a conversion happens. The action clock starts when you clicked "create" and runs once. Google phrases the rule for offline and import-style uploads, which is exactly the path a server-side tracking integration uses; browser-tag conversions are not what this wording covers.

There is a consolation prize in the same documentation: conversions uploaded during the waiting window are not necessarily lost, but they can take about 2 days to show in reports when they do land [1].

What happens to purchases made during the waiting period?

Some get rejected, some crawl. Uploads attempted before the action is eligible bounce with the too-recent error [2]; ones accepted near the boundary may spend up to 2 days working their way into reports [1]. So the practical setup advice is: create the conversion action first, let the window pass, and only then judge the data.

If you set up through WeltPixel Conversion Tracking, the setup wizard tells you about this waiting period at every path that creates a conversion action, precisely because purchases made before the action becomes active may be rejected by Google Ads and never appear in reports. Plan the go-live accordingly: create the action in the morning, check the numbers the next day, and resist the urge to place diagnostic test orders in hour one. A test order has a second problem anyway, covered below.

The hour-by-hour checklist: what is normal at each mark?

At 30 minutes: zero everywhere is the only possible state. The action is inside its 4-6 hour window [1]. Any click that could feed a conversion is also probably under the 6-hour click-matching threshold [4]. Nothing here is diagnosable yet; close the tab.

At 6 hours: the action is typically eligible now. If a real, paid-click order arrived, the upload can be accepted, and then normal freshness applies: conversion tracking data appears within about 3 hours under the last-click attribution model, and up to about 15 hours under other models [3]. Import processing on Google's side typically completes in under 12 hours, stretching to 72 hours for gbraid/wbraid-keyed conversions [4]. Which attribution model your account uses, and why numbers keep shifting for days afterward, is territory for attribution windows and reporting delays.

At 24 hours: with real paid-click orders in hand, you should be seeing data. If the conversions column is still zero, move to the misconfiguration checklist in the next section. One more Google-stated threshold to apply here: a conversion within one day of its click may not be recorded yet [5], so an order from last night's click may legitimately still be in flight this morning.

Enhanced conversions sub-check: if you switched on enhanced conversions during the same setup session, do not judge its diagnostics in hour one either; Google's API diagnostics report can take up to 48 hours to reflect status [7]. Setup and verification for that feature live in enhanced conversions setup and verification.

What do "Unverified" and "No recent conversions" actually mean?

The status column in Goals → Conversions describes whether Google has recently seen your conversion source, and it is written around the website-tag path. "Unverified means that the conversion tracking tag associated with this conversion action has not yet fired," and Google's own troubleshooting threshold is that the status deserves attention when it persists beyond about 24 hours [6]. "No recent conversions" means the source is verified but nothing was recorded in the last 7-14 days; "Tag inactive" means the tag has stopped being seen.

The trap for import-style actions, the type server-side integrations upload to: there is no website tag to verify. An import action shows activity only after uploads are received and processed, so early "no data yet" states on a freshly created import action are the expected condition, not a defect. The status column is a "has Google seen this source lately" indicator, not a live meter of today's conversions. Read it accordingly, and verify in Google Ads itself rather than expecting any external dashboard to mirror it.

Still zero after 24 hours: the real misconfigurations

Now, and only now, is the panic earned. Work this list in order:

1. Did any order actually come from a paid Google click? No ad click means no Google click ID on the order, and an import keyed on click IDs has nothing to key on. Organic orders and hallway test orders do not count. This is the first thing to rule out.
2. Are clickless orders expected to upload? By default they are not: with the import-without-click-ID option off (the default), orders that arrive without a Google click ID are never uploaded. If a meaningful share of your Google-driven orders lose their click IDs, that recovery path is its own topic: Google Ads conversions without a GCLID.
3. Was the click older than the action's click-through window? Click IDs whose clicks predate the conversion action's click-through lookback window are dropped before upload rather than sent to be rejected. A 90-day window (the default on actions the app creates) makes this rare; a shortened window makes it worth checking.
4. Is the app pointed at the right action, in the right account? An upload landing in a second conversion action, or a second Google Ads account, produces a convincing zero in the one you are staring at.
5. Is a tag-based action stuck at "Unverified" past 24 hours? That is Google's own threshold for a genuine tag problem [6], and it means the tag path, not the import path, needs fixing. Full setup mechanics live in the complete Google Ads conversion tracking guide.

And the handoff: if conversions are arriving fine but Google Ads consistently reports fewer than Shopify week after week, you have graduated from setup problems to a structural counting story, which is its own article.

What does a tracking app change about all this?

The clocks are Google's; nothing shortens them. What an integration controls is everything around them. WeltPixel Conversion Tracking creates the conversion action for you, pre-configured as a Purchase-category import action with a 90-day click-through window, and warns you about the 4-6 hour wait at setup so the first-day zero reads as expected rather than alarming. From then on, each Shopify order is uploaded within moments of being created, with click IDs older than your action's window dropped before upload, so the delay you experience afterward is Google's processing rather than the app queueing. Set it up once, let the clocks run out, and the conversions column starts telling the truth. Install it from the Shopify App Store, create the action, and check back tomorrow, not in ten minutes.

FAQ

How long after creating a Google Ads conversion action can conversions be uploaded?

Google's documentation says to wait 4-6 hours after creating the action [1], and its API guidance is to wait at least 6 hours before retrying rejected uploads [2]. Uploads during the window are rejected or can take about 2 days to display.

Why does my conversion action say "Unverified"?

The conversion tag associated with the action has not been seen firing yet [6]. In the first hours after setup this is normal; Google treats it as a real issue when it persists beyond about 24 hours. Import-type actions have no website tag, so tag-verification statuses do not apply to them the same way.

I placed a test order right after setup. Why doesn't it show?

Three clocks stack against it: the action's 4-6 hour eligibility window [1], the rule that clicks under 6 hours old cannot be matched [4], and the note that conversions within one day of the click may not be recorded yet [5]. And if the test order did not come from clicking a real ad, it has no Google click ID at all, so with default settings there is nothing to import.

How fast does the app send my order to Google Ads?

Within moments of the order being created on Shopify. The visible delay afterward is Google-side processing: typically under 12 hours for imports, up to 72 hours for gbraid/wbraid-keyed conversions [4].

When should I actually worry?

When you have real paid-click orders, more than 24 hours have passed, and the status column is not clearing. At that point work the misconfiguration list above: paid click present, clickless-order settings, click-through window, correct account and action.

Sources

1. Google, "Set up offline conversions using Google Click ID (GCLID)," support.google.com/google-ads/answer/7012522 (accessed July 17, 2026)
2. Google, "Google Ads API: Troubleshooting conversion uploads," developers.google.com/google-ads/api/docs/conversions/troubleshooting (accessed July 17, 2026)
3. Google, "About data freshness," support.google.com/google-ads/answer/2544985 (accessed July 17, 2026)
4. Google, "Fix discrepancies and errors in offline conversion imports," support.google.com/google-ads/answer/13321563 (accessed July 17, 2026)
5. Google, "Import conversions from ad clicks into Google Ads using files (legacy)," support.google.com/google-ads/answer/7014069 (accessed July 17, 2026)
6. Google, "The Unverified status has been showing for more than 24 hours," support.google.com/google-ads/answer/10029065 (accessed July 17, 2026)
7. Google, "About the enhanced conversions for web API diagnostics report," support.google.com/google-ads/answer/11954870 (accessed July 17, 2026)