Open your analytics dashboard, watch a visitor land on your site, and see… nothing. Refresh the page five minutes later and suddenly three sessions appear. The “real-time” label sits right there in the interface, but the data doesn’t match what’s happening right now.
Most analytics platforms advertise real-time dashboards, but very few update continuously. The refresh interval—the gap between when an event happens and when it appears in your dashboard—varies wildly depending on what you’re measuring, which plan you’re on, and how the platform processes data behind the scenes.
If you’re making decisions based on dashboard numbers, you need to know what’s actually current and what’s been batched, sampled, or delayed.
What “real-time” actually means in analytics platforms
Google Analytics 4 is the clearest example. The Real-Time report updates every few seconds and shows activity from the last 30 minutes. But the moment you leave that report and open Acquisition or Engagement, you’re looking at data that’s between 24 and 48 hours old. GA4 processes most reports in daily batches, not continuously.
Plausible and Fathom refresh their main dashboards every 60 seconds. If you’re watching live, you’ll see new pageviews appear roughly once a minute. That’s fast enough for most use cases, but it’s not instant—if you’re running a launch and want to know whether traffic spiked in the last ten seconds, you’re still guessing.
Matomo’s live widget updates every few seconds when you’re on a self-hosted instance, but their cloud version throttles refresh rates on lower-tier plans to reduce server load. If you’re on the cheapest plan, expect updates every 60 to 90 seconds.
Mixpanel and Amplitude update event streams within seconds, but their funnel and cohort reports recompute on a schedule—usually every 15 minutes to an hour, depending on data volume. If you’re tracking a funnel and refresh the page expecting new conversions, you might be looking at stale totals.
Dashboard widgets vs. raw event logs
Most platforms separate their real-time event stream from their aggregated dashboards. The event stream is fast—often sub-10-second latency—because it’s just appending rows to a log. The dashboard, on the other hand, has to query, filter, and aggregate that data, which takes time.
If you need to confirm that a tracking event fired, check the event log or debugger, not the dashboard. GA4’s DebugView updates within seconds. Mixpanel’s live view shows events as they arrive. Plausible doesn’t have a separate event stream, so you’re waiting for the dashboard refresh no matter what.
For solo operators, this split matters when you’re testing campaigns or debugging tracking. If you fire a test event and immediately check the dashboard, you might think tracking is broken when it’s actually just queued.
Refresh intervals by metric type
Not all metrics update at the same speed, even within the same platform.
Pageviews and sessions: These usually update within 60 seconds on most platforms. Plausible, Fathom, and Matomo all refresh these quickly because they’re simple counters.
Conversion goals and funnels: These can lag by 5 to 15 minutes because the platform has to check whether a session completed a multi-step sequence. GA4 conversions often take 24 hours to appear in standard reports, even though they show up faster in the Real-Time view.
Revenue and e-commerce data: Expect delays of 15 minutes to several hours. Platforms batch these queries to avoid hammering payment APIs. If you’re tracking Stripe revenue through a Zapier webhook, the event might fire instantly, but your analytics dashboard might not recompute totals until the next scheduled job runs.
Attribution reports: These are almost never real-time. Attribution models require matching sessions across days or weeks, so most platforms run these overnight. If you’re checking which campaign drove yesterday’s signups, you’re probably looking at data that’s 12 to 36 hours old.
When refresh speed actually matters
For most content-driven businesses, real-time updates don’t change decisions. Checking traffic once or twice a day is enough. But there are a few cases where refresh intervals matter:
During a launch or campaign: If you’re running a ProductHunt launch or a limited-time promo, you want to know within minutes whether traffic is spiking and whether conversions are happening. A 24-hour delay in GA4 means you’re flying blind.
When debugging tracking: If you just installed a new analytics snippet or updated a conversion goal, you need fast feedback to confirm it’s working. Waiting an hour to see if a test event fired wastes time.
If you’re running paid ads: Ad platforms like Facebook and Google Ads update their dashboards every few minutes. If your analytics platform lags by an hour, you can’t cross-check whether the traffic you’re paying for is actually landing on your site.
For everything else—weekly traffic trends, month-over-month growth, cohort retention—real-time refresh doesn’t matter. A daily batch report is fine.
How to work around slow dashboards
If your analytics platform is too slow for your needs, you have a few options:
Use the platform’s event debugger or live view instead of the main dashboard when you need instant feedback. GA4’s DebugView, Mixpanel’s live feed, and Matomo’s visitor log all update faster than their aggregated reports.
Set up a separate real-time dashboard using a tool like Geckoboard or Databox, pulling from your analytics API. These tools query your data every few minutes and display it in a single view. It’s overkill for most solo operators, but if you’re coordinating a launch with a team, it helps.
Accept that some metrics will always lag and plan around it. If you’re checking conversion rates, don’t expect up-to-the-minute accuracy. Check once in the morning, make decisions, and move on.
Most platforms won’t tell you their exact refresh intervals unless you dig through their docs or ask support. If you’re evaluating a new analytics tool, test it during signup: fire a few test events, note the time, and see how long it takes for them to appear in each report.
If you’re running a content business and want more breakdowns like this, subscribe to One Two Three Send. One email a day, no fluff, just the infrastructure details that solo operators actually need.