TL;DR
Every platform runs two separate clocks on the same purchase. The receipt clock says whether the event arrived, and it runs in seconds to minutes on a live verification surface built for that question. The reporting clock says when the event appears in the numbers you screenshot for a meeting, and it runs in hours. Most "my conversions are missing" panics come from reading the second clock while asking the first clock's question. This page is the ledger of both, per platform, with each figure attributed to the platform that publishes it.
Key Takeaways
- Check receipt on a live surface: GA4 Realtime shows the last 30 minutes [1], DebugView's Seconds stream shows the last 60 seconds [2], and Meta and TikTok both have a Test Events tab.
- Google Ads publishes its own freshness figures: conversions refresh in about 3 hours under last-click attribution and 15 hours under other models, while clicks, impressions, and cost run on a 1-hour target [3].
- GA4 documents "typically a few minutes" for Realtime, 2 to 6 hours for intraday data, and daily data ready at 3:30 pm in the property time zone, and says explicitly that none of it is an SLA [5].
- TikTok asks you to "allow up to 2 hours processing time" before event statuses update in Ads Manager, and states that event data is not displayed in real time [4][6].
- Meta publishes no reporting-latency figure at all. Our working rule is to verify Meta receipt in the Test Events tool and treat the last 48 hours of Meta totals as provisional.
- Google's guidance for a newly created conversion action is to wait 4 to 6 hours before uploading conversions to it, which is an import-path instruction rather than a property of the action [7].
- Silence on the receipt clock is a fault. Slowness on the reporting clock is the product working as documented.
The two-clock ledger
| Platform | Receipt: verify here | Reporting: settles in |
|---|---|---|
| GA4 |
Reports → Realtime, last 30 minutes [1] |
Intraday 2 to 6 hours; daily data ready 3:30 pm, property time zone [5] |
| GA4 (parameters) |
Admin → Data display → DebugView, Seconds stream = last 60 seconds [2] |
Same as above |
| Google Ads | No live equivalent for uploaded conversions | 3 hours last-click; 15 hours other attribution models; 1-hour target for clicks, impressions, cost [3] |
| Meta | Events Manager → Data sources → Test events |
No published figure; last 48 hours provisional (our rule of thumb) |
| TikTok | Events Manager, Test Events tab | Up to 2 hours for statuses in Ads Manager [4]; event data not shown in real time [6] |
Two rows deserve a second read.
The Google Ads split between 3 hours and 15 hours is the most useful number on this page, because almost nobody knows it exists. The same account, looking at the same conversion action, refreshes five times slower once the attribution model moves away from last click. If your team compares a data-driven view in the morning against a last-click view in the afternoon, they are comparing two freshness states as well as two models.
The Meta row states an absence. Meta publishes plenty about how fast you should send events, asking that server events go out "in real time or in batches close to real time" [8], and maintains a page of recommended and maximum delay times for web events [9]. It publishes no equivalent figure for how long its own reporting takes to settle. The 48-hour provisional rule in that row is ours, arrived at from support cases rather than from Meta, and it is labelled that way everywhere it appears on this page.
Why the two clocks are separate systems
A purchase on your store sets off two independent processes at each destination. Ingestion receives the event, validates it, and makes it visible on a diagnostic surface built for exactly the question you are asking. Attribution and aggregation then decide which click earned the sale, apply the window, fold the result into campaign totals, and refresh the reporting tables.
The gap between them is not a queue you are waiting in. These are different systems with different service levels, and the platforms document them separately when they document them at all. Google Analytics is the most explicit, listing Realtime at "typically a few minutes", standard intraday data at 2 to 6 hours, and daily data ready at 3:30 pm in the property's time zone, with a warning that these are typical figures and "not a guarantee, nor an SLA or an SLO" [5].
Which model of the sale each platform files, and on which calendar day, is a third question again. We covered that in attribution windows and reporting delays on Shopify, and it stays out of this article. Here the question is only how long before you can see the thing at all.
The one check worth running
Put a real order through, then read the receipt column of the ledger above for whichever platforms carry your spend. A real order matters because the events you care about most are the ones that only exist at the end of a checkout, and a synthetic click never produces them. Give GA4 a minute, Meta and TikTok their test tabs, and skip Google Ads entirely, since server-side conversion uploads have no live equivalent in the interface. Our DebugView setup guide covers turning on debug mode for your own browser, which is what puts the event parameters on screen. If the event shows on the receipt clock, your tracking works, and everything after that is arithmetic on somebody else's schedule.
When should you actually worry?
| Platform | Still normal | Start investigating |
|---|---|---|
| GA4 | Nothing in standard reports before the next 3:30 pm [5] | Nothing in Realtime 30 minutes after a confirmed order [1] |
| Google Ads, existing action | Zero conversions for the first 3 to 15 hours [3] | Zero after 24 hours with orders confirmed elsewhere |
| Google Ads, new action | Zero when you uploaded inside the 4 to 6 hour wait Google asks for [7] | Zero after a full day past that wait |
| TikTok | Status unchanged for 2 hours [4] | Nothing in Test Events during a live session |
| Meta | Totals moving for the last 2 days (our rule of thumb) | Test events tool silent while you browse the store |
The right-hand column is always the receipt clock. Every genuine tracking failure appears there, and every false alarm appears in the left-hand column. The new-conversion-action case generates the most support tickets of the five, and it has its own article: a new Google Ads conversion action showing zero, and the 4 to 6 hour rule.
One more source of phantom delay is worth naming. Time zones delay nothing, but they move sales across day boundaries, so a store on UTC+3 reporting into a platform set to UTC will always look like it is missing yesterday evening. Align the zones before you count anything.
What a tracking app can and cannot change here
It can change when the platform receives the event, and that is the whole of its influence. WeltPixel Conversion Tracking sends the server-side purchase from Shopify's orders/create webhook within seconds of the order being recorded, so the event is already at the platform by the time you open a test tab, instead of waiting on a browser that may have closed. Its dashboard shows delivered and skipped counts per platform, which separates "we never sent it" from "they have not processed it yet" without opening five tabs.
What no app changes is the refresh schedule on the other side. Nothing installed on your store speeds up Google Ads' 15-hour clock for non-last-click models or moves GA4's 3:30 pm daily build. Any tool implying otherwise is selling a delay it does not control.
FAQ
Why do my Google Ads conversions still show zero hours after the sale?
Google refreshes conversion data roughly every 3 hours under last-click attribution and every 15 hours under other attribution models [3]. If the conversion action is new, Google also asks you to wait 4 to 6 hours before uploading conversions to it [7], so an upload made inside that wait explains a zero too.
How quickly should a purchase appear in GA4?
Within minutes on Reports → Realtime, which covers the last 30 minutes of activity [1], and within 60 seconds in DebugView if debug mode is on for your browser [2]. Standard reports are a different clock: 2 to 6 hours intraday, with daily data ready at 3:30 pm in the property's time zone [5].
Is TikTok's dashboard supposed to be this slow?
Yes. TikTok states that event data is not displayed in real time [6] and asks you to allow up to 2 hours of processing before statuses update [4]. Use the Test Events tab for anything you need an answer on today.
Why does Meta not publish a reporting delay?
Meta documents how fast you should send events rather than how fast it reports them [8][9]. With no published figure, our working rule is to verify receipt in the test events tool and treat the last two days of Meta totals as unfinished. That rule is ours, not Meta's.
If you would rather watch events land per platform than reconstruct the timeline afterward, WeltPixel Conversion Tracking delivers each Shopify order server-side to the nine integrations it supports and logs what went where, at $39 a month flat, with a free GA4-only plan for up to 100 storefront orders a month [10].
Paste the worry table into the runbook your team opens the morning after a launch. It answers the question that gets asked at 8 a.m. before anyone has had time to look anything up.
Sources
- Google Analytics Help, "Realtime report", support.google.com/analytics/answer/9271392, accessed September 4, 2026
- Google Analytics Help, "DebugView", support.google.com/analytics/answer/7201382, accessed September 4, 2026
- Google Ads Help, "About data freshness", support.google.com/google-ads/answer/2544985, accessed September 4, 2026
- TikTok Ads Manager Help, "About data connection for website optimization", ads.tiktok.com/help/article/about-data-connection-for-website-optimization, accessed September 4, 2026
- Google Analytics Help, "Data freshness", support.google.com/analytics/answer/12233314, accessed September 4, 2026
- TikTok Ads Manager Help, "About diagnostic and monitoring tools in TikTok Events Manager", ads.tiktok.com/help/article/tiktok-events-manager-monitor-and-diagnose, accessed September 4, 2026
- Google Ads Help, "Set up conversion tracking for your website", support.google.com/google-ads/answer/7012522, accessed September 4, 2026
- Meta for Developers, "Conversions API best practices", developers.facebook.com/docs/marketing-api/conversions-api/best-practices, accessed September 4, 2026
- Meta Business Help Center, "Recommended and maximum delay times for web, app and offline events", facebook.com/business/help/801591810609156, accessed September 4, 2026
- WeltPixel Conversion Tracking, Shopify App Store listing, apps.shopify.com/weltpixel-conversion-tracking, accessed September 4, 2026