Real-Time vs Batch
Data & TrackingAlso: Real-Time Data vs Batch Data · Streaming vs Batch Processing
Quick definition
Real-time and batch describe two ways data moves through a system. Real-time processing updates data the moment an event happens. Batch processing collects events and processes them together on a schedule, often hourly or daily. Most marketing stacks use a mix of both depending on what the data feeds.
How it varies across Australia
Australian marketing teams tend to over-invest in real-time infrastructure for dashboards that get checked once a day. The gap between what's technically live and what's actually acted on in real time is wide across most industries we review.
See data and tracking maturity across Australian industries →What it actually means
Real-time is a light switch. Flip it and the room is lit immediately. Batch is a delivery truck. Orders pile up during the day and everything arrives together at a set time, usually overnight.
In marketing terms, real-time processing means an event like a click, a purchase or a form fill updates your systems within seconds. Batch processing means those same events get queued and pushed through together, often as a scheduled job that runs every hour or once a day.
The confusion usually starts when someone says their dashboard is real-time when the underlying pipeline is actually batch running every 15 minutes. That's close enough for most reporting but it's not the same thing, and the distinction matters when you're troubleshooting why a conversion event or a segmentation update hasn't shown up yet.
Real-time infrastructure costs more to build and maintain than batch. It also introduces more failure points because there's no buffer to absorb a bad event before it hits your reporting or your CRM. Most attribution and reporting use cases don't need it. Personalisation, fraud detection and abandoned cart triggers usually do.
Real-time is a light switch. Batch is a nightly delivery truck. Most marketing decisions only need the truck.
How it shows up
It shows up in the gap between what a dashboard claims and what it delivers. A tool labelled 'live' that actually refreshes every 30 minutes is running near-real-time, not true real-time. It shows up in CRM workflows, where a lead captured on a landing page either triggers an instant email (real-time) or gets picked up in the next nightly sync (batch). It also shows up in cost. Cloud vendors charge a premium for streaming infrastructure over scheduled batch jobs, so finance teams often notice it first.
The Australian context
Australian businesses running on offshore cloud infrastructure sometimes see batch jobs scheduled against a US timezone by default, which means data that should refresh overnight local time actually lands mid-afternoon here. It's a small thing that causes disproportionate confusion when a team assumes their dashboard is showing yesterday's numbers and it's actually two days behind.
Where people get this wrong
Related terms
Common questions
Is Google Analytics 4 real-time or batch?
Both. Google Analytics 4 (GA4) has a real-time report showing activity from the last 30 minutes, but standard reporting runs on a batch pipeline that can take up to a day to fully process and reconcile. Don't judge campaign performance off the real-time view alone.
Do I need real-time data for my marketing stack?
Only if a decision or automated action genuinely needs to happen within seconds, like fraud detection, abandoned cart triggers or live personalisation. Most reporting, attribution and campaign optimisation work fine on batch data refreshed daily or hourly.
Why does my dashboard say real-time but the numbers lag?
Many tools labelled real-time actually run near-real-time batch jobs on a short interval, like every 15 or 30 minutes. Check the vendor's documentation for the actual refresh interval rather than trusting the label.
Does batch processing lose data?
Not if built correctly. Batch processing delays when data arrives but shouldn't lose it. Data loss usually comes from a broken pipeline, a failed job, or events not being captured at the source, not from the batch model itself.
Debrief
Get the next one
No spam. No fluff. Just the next article, straight to your inbox.
Keep exploring
About New Rebellion
New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.
How we think →