Real-Time ROAS Tracking: What It Takes and When It's Worth It

Real-time ROAS tracking is alerting, not live reporting

You should ignore real-time ROAS for 23 hours of every day and act decisively during the one hour that exposes a fault. The exception is expensive: spend can continue while tracking, forms or CRM hand-offs fail. A disciplined approach to Google Ads management treats real-time ROAS as an alerting problem disguised as a reporting problem: you need to know within an hour that something broke, then stop watching the number.

Spend can appear within minutes. Qualified pipeline and revenue might arrive days or months later. An intraday ratio therefore combines a fast denominator with an incomplete numerator.

That does not produce a more current truth. It produces a provisional number with false precision.

Operational health deserves intraday alerts. Budget allocation deserves mature evidence. If the dispute concerns what belongs in the economic formula, settle that first with our guide to calculating true return.

The useful distinction is simple:

• Live monitoring asks whether the measurement and acquisition machinery still works.
• Daily reporting asks whether yesterday was abnormal.
• Weekly analysis asks whether bidding or targeting needs intervention.
• Monthly review asks whether accumulated data remains commercially trustworthy.

Those are four separate decisions, not four refresh rates for one metric.

Fast alerts protect operations; slower evidence protects judgement.

Four monitoring jobs require four cadences

One number cannot serve four monitoring jobs without encouraging bad decisions.

Monthly contamination review should inspect four failure modes: duplicate event IDs, internal submissions, broken campaign identifiers and stalled offline-import queues.

Weekly bidding decisions also need to sit inside a defensible B2B paid-search strategy. Faster data cannot rescue weak positioning, irrelevant keywords or an offer buyers do not understand.

The five conditions worth an immediate alert

An immediate alert needs a numerical trigger and a predetermined response. These five conditions meet that standard:

1. Conversion tracking is silent for 2 consecutive hours while at least 25 paid sessions arrive. Page the technical owner and run a test conversion within 15 minutes.
2. Spend exceeds 75% of the daily budget by midday, versus a seven-day comparable-day median of 55% or less. Investigate duplicated delivery, scheduling or an unusual traffic shift. Do not make an automatic budget change.
3. A campaign records zero primary conversions by 15:00 after averaging at least 8 per day across the previous 28 complete days. Test the landing journey and event receipt before touching bids.
4. A paid landing page returns a non-success response from two locations on 2 consecutive checks within 10 minutes. Confirm the fault, then switch to a verified destination or pause only the affected traffic.
5. The oldest CRM or offline-conversion queue item exceeds 4 hours when the normal service level is below 1 hour. Repair and replay the queue; do not label the campaign unprofitable.

A campaign averaging 8 conversions per day and reporting 0 by mid-afternoon deserves investigation. A campaign averaging 2 conversions per week does not. Low-volume silence is normal variation, not an incident.

Cadence protects accounts from both silence and overreaction.

The data-latency table for live versus daily ROAS

The revenue side and spend side run on different clocks. A “live” ratio is usable only when both clocks are inside known latency limits.

The six relevant clocks are:

For illustration, a 30-day sales cycle and a 90-day sales cycle require different cohort maturity dates. Comparing both after 7 days would reward whichever account records revenue earlier, not whichever creates better economics.

These ranges are operating allowances, not vendor guarantees. Measure your own 95th-percentile ingestion delay over 30 days and replace every generic allowance with the observed figure.

Three confounds can distort that measurement: consent loss, manual CRM behaviour and time-zone boundaries. The honest limit here is that timing analysis cannot tell you whether attribution itself is correct. That belongs in a separate examination of Google Ads ROAS accuracy.

To produce a live provisional figure, ingest spend and outcome events at least every 15 minutes and preserve both event time and ingestion time. If the numerator is more than 2 hours staler than the denominator, suppress the ratio instead of presenting missing revenue as zero.

For daily use, wait until both sides meet their latency allowance, then freeze the comparison window. A later correction should create a revised version rather than silently rewriting the earlier decision record.

Health can be live; commercial truth arrives on its own clock.

If the path from ad click to signed revenue still has gaps, Actualyse will trace each hand-off with you — book a call

When real-time ROAS tracking is worth building

A fast alert has value only when somebody can reduce the loss before the normal review.

Apply three investment gates:

1. Exposure gate: a confirmed one-hour failure can waste at least £250 of media spend or £1,000 of historically expected qualified pipeline.
2. Signal gate: at least one of three observable signals exists—25 paid sessions within 2 hours, 8 primary conversions per day, or a reliable synthetic conversion test.
3. Response gate: a named owner can acknowledge the alert within 15 minutes and contain a confirmed incident within 60 minutes.

If any gate fails, retain basic breakage monitoring and review commercial performance daily or weekly. A streaming ROAS build will create operational theatre rather than value.

Three build options

1. Basic health monitoring

Use platform delivery rules, an uptime check and a conversion heartbeat. This is the default below £30,000 monthly spend or below 5 qualified outcomes per day.

The absence of live ROAS is deliberate. Component failures are more detectable than movements in a sparse ratio.

2. Hourly batch monitoring

Pull three feeds—media cost, server-side conversion events and CRM updates—into a common store each hour. Use this between £30,000 and £100,000 monthly spend when all three investment gates pass.

Calculate a provisional ratio for context, but generate alerts from failed components and abnormal pacing.

3. Streaming event monitoring

Continuously ingest media and outcome events into an event store. Consider this only at £100,000 or more in monthly spend, at least 20 revenue-bearing outcomes per day and a genuine sub-hour response capability.

Those thresholds are starting rules, not universal laws. Failure exposure and response capability matter more than the attraction of technically fresh data.

An illustrative UK B2B example

Take an illustrative UK B2B software company evaluating hourly monitoring with seven labelled inputs:

• Monthly paid-media spend: £40,000
• Active buying days: 20 per month
• Monitored time: 10 hours per day
• Fault duration before the daily review: 3 hours
• Detection time with an alert: 0.5 hours
• Unusable-spend share during the fault: 80%
• Illustrative monitoring cost: £600 per month

The arithmetic is:

Average monitored spend per hour = £40,000 ÷ 20 ÷ 10 = £200

Exposure with daily detection = £200 × 3 × 80% = £480

Exposure with a 30-minute alert = £200 × 0.5 × 80% = £80

Avoided exposure per incident = £480 − £80 = £400

Break-even incident frequency = £600 ÷ £400 = 1.5 incidents per month

Because incidents occur as whole events, the system needs to prevent at least 2 comparable incidents per month to cover its illustrative £600 cost through spend protection alone. At 1 incident, the benefit is £400 versus a £600 cost, so the custom build loses.

This is incident economics, not a client result or a complete ROAS calculation. Opportunity loss should be added only when historical CRM records support the assumed value.

Where the missing capability is ongoing account ownership, B2B Google Ads management is the relevant route. A defined tracking or campaign intervention is better suited to fixed-scope Google Ads project support.

Buy response speed only when response speed changes the loss.

What does not work and does not matter

The version that reaches us in audits usually contains more refreshing, more automation and less decision discipline.

Four specific approaches fail:

1. Daily ROAS in a long sales cycle. Daily ROAS is noise when opportunities close weeks or months after the click. In audits, reacting to it is the most common cause of destroyed bid-strategy learning we encounter. Repeated bid, target and budget edits change the system before earlier outcomes can mature.
2. A continuously recalculated provisional ratio. Spend arrives before attributed outcomes, so the intraday ratio often falls and then recovers without any underlying change. Refreshing it more frequently multiplies observations, not evidence.
3. Routine intraday budget automation. A rule that cuts spend whenever provisional ROAS falls acts on the known latency mismatch. It can suppress campaigns before delayed conversions arrive and repeatedly disrupt bid-strategy learning. Intraday budget changes belong to confirmed incidents, not normal optimisation.
4. Minute-level reconciliation between sources. Different event times, ingestion times and attribution rules make exact short-window agreement an invalid objective. If conflicting figures are the real problem, use the separate explanation of why headline Google Ads return can mislead rather than building faster refreshes.

Our position is falsifiable: when median lead-to-close exceeds 60 days, minute-level ROAS viewing will not reduce cost per sales-qualified opportunity. A controlled 12-week test showing at least a 10% reduction with unchanged spend and qualification criteria would prove the claim wrong.

More frequent observation does not create fresher commercial evidence.

FAQ

What should happen outside normal working hours?

Use one of two named schedules. If campaigns intentionally run, retain the 15-minute acknowledgement and 60-minute containment targets. If they should be inactive, any spend above £25 or 5% of the daily budget triggers an immediate stop-and-check.

How should a low-volume B2B account detect conversion failure?

Use a synthetic submission every 60 minutes and page after 2 consecutive failures. Below 3 qualified leads per week, zero real conversions is too weak a signal for immediate alerting.

How long should alert history be retained?

Keep 13 months when annual seasonality affects traffic; otherwise retain at least 90 days. Record four fields for every alert: trigger, acknowledgement time, confirmed cause and resolution.

What false-positive rate is acceptable?

If more than 1 in 5 alerts finds no fault and produces no action across 30 days, tighten or retire the rule. At 1 in 10 or fewer, paging remains operationally credible.

Real-time systems earn their place through faster, documented incident response.

Summary

Five operating rules determine the build:

• Page an owner within 1 hour only when a numerical breakage threshold fires.
• Compare complete daily data against 28 complete days; never judge partial-day ROAS.
• Extend a 7-day bid review to 28 days when fewer than 10 primary conversions exist.
• Suppress any live ratio when numerator latency exceeds denominator latency by more than 2 hours.
• Build streaming monitoring only after the exposure, signal and response gates all pass.

Alerts deserve speed; ROAS deserves maturity.

Actualyse builds measurement and attribution setups that tie B2B ad spend to real revenue. Book a call to talk through where yours stands.