Skip to content
watchingthat
Operations Control Platform · Early warning

Revenue dropped Tuesday. Know Tuesday.

Anomaly detection in minutes, not the morning report. Every alert carries the revenue at risk — named in dollars, and routed to the owner who can fix it in about 90 seconds.

A Watching That Anomaly Monitor mid-event: Gross Impressions collapsed to zero against its baseline, the Monitor firing an ALARM, and a receipt band reading Detected — caught the moment it broke, Revenue at risk $253K priced on the alert, Routed to a named owner in about 90 seconds.
The problem

Revenue doesn't fail loudly.

Fill collapses at 04:14; a partner starts erroring; unused inventory drifts. The pacing dashboard catches up at 09:30 — and by then it’s five hours of exposure you’ll only fully see at month-end. By the time the morning report names it, the day’s already compounded. You’re not short of dashboards. You’re short of the one thing that matters the moment a number moves: how much is this costing me, right now, and who fixes it?

Before

Every tracked KPI stays green. Fill rate holds at 77%, so the drop hides in a metric no dashboard watches — and only surfaces a quarter late, in the monthly revenue report.

Before: a performance dashboard where every tracked KPI stays green — fill rate holds at 77%, render rate and CPM steady — while avails and impressions volume, a metric no dashboard watches, craters 75%. The drop only surfaces a quarter late, in the monthly revenue BI, after an exec emails asking why revenue fell.
After

Watching That watches every metric, not just your KPIs. The same drop is auto-flagged the moment it happens, priced in dollars, and pushed to a named owner — the day it breaks, not a quarter later.

After: the real Watching That Anomaly Monitor auto-flags the same 75% drop in Gross Impressions the moment it happens — even though it isn't a tracked KPI — and pushes an alert to Slack and email naming the revenue at risk, the cause, and the owner, the day it broke.
01 · Time-to-detect

By the time the morning report lands, the revenue is already gone.

Five hours of exposure between the deviation and the dashboard — reconstructed after the fact, priced by the CRO in a meeting you weren’t in.

02 · Revenue at risk

The alert fires. The alert does not carry a dollar figure.

A deviation chip. A red arrow. Maybe a percentage. None of it answers the one question the CRO is about to ask — how much? By the time someone stitches the exposure together from three systems, the window to act has closed.

03 · Action before loss

You see the anomaly. You still don’t know whose surface it is.

Is it the ad server? The SSP? The SSAI endpoint? The partner? The alert lives in one system; the root lives in another; the owner lives in a third. Three tabs open, the hour compounding, the exposure still live.

What we do · Monitoring

We watch your live revenue surfaces.

Watching That’s Monitoring watches your live revenue surfaces and tells you the moment one breaks — with the dollars attached.

Detect — continuous runtime checks across your ad servers, SSPs, SSAI endpoints and partner connections, each Anomaly Monitor watching one metric on one surface against its own learned baseline.

Price — the instant a Monitor fires, the deviation is priced: the alert carries the revenue at risk in dollars, not a colour on a chart.

Resolve — the fire lands with a named root and a named owner, routed in about ninety seconds through a three-stage routing tree, then reconciled end-of-day with the exposure number behind it.

The clock starts at the deviation — not at the morning report.

The real Watching That Anomaly Monitor surface: a threshold monitor on Gross Impressions across CTV-East, the baseline and lower-threshold plotted against live volume, with an ALARM (caught runtime anomaly) / OK (within baseline) legend — continuous monitoring, read-only across the stack.
Continuous monitoring, read-only across the stack — the anomaly layer as it actually looks.
Proof

What it's worth to know on Tuesday.

Pay-TV operator · caught incident
$50K/hr
fill collapse caught in minutes and routed before the hour compounded

At national pay-TV scale, a fill collapse started mid-evening. A Monitor caught it in minutes — not at the 09:30 morning report — priced the deviation at roughly $50K an hour, and routed it to the named SSAI owner before the hour compounded. The exposure was named on the alert, from the deviation.

— Pay-TV operator (anonymised)

Publisher · New York Post
2M+
daily impressions protected, video + display

“Watching That has given us full control of our video advertising. Their diagnostics and troubleshooting tools have helped us find, fix and solve revenue-impacting issues much more quickly and easily than before.”

— Amanda Gomez, VP Revenue Operations, New York Post

We already watch your stack.

Read-only across ad servers / SSPs / SSAI / partner connections

FreeWheel
Ad Server
Beachfront
SSP
JWP Connatix
SSP
Google Ad Manager
Ad Server
Index Exchange
SSP
Magnite
SSP
Microsoft Advertising
Ad Server
Nexxen
SSP
OpenX
SSP
PubMatic
SSP
Sharethrough
SSP
SpringServe
Ad Server
TripleLift
SSP
Yahoo Advertising
SSP
Amazon Ads
Ad Server

…plus the SSAI endpoints and partner connections in between.

Questions

Early warning, answered.

What does Watching That detect?

Live revenue anomalies on your monetisation surfaces: fill collapses, pacing deviations, partner-side error spikes, unused-inventory drift, measurement bugs. Each Anomaly Monitor watches one metric on one surface against its own learned baseline, continuously — and prices the deviation in dollars the moment it fires.

Is it real-time?

No. It runs on a continuous monitor cadence, not real-time streaming. The promise is "minutes, not the morning report": the clock starts at the deviation rather than at the next pacing report, so you catch a Tuesday drop on Tuesday — typically within minutes — while you can still act on it.

What do you mean by "named in dollars"?

Every alert carries the revenue at risk as a dollar figure, not a colour on a chart. The deviation is priced on the way out, so you triage by exposure — and the figure is reconciled end-of-day in Report.

Does it replace my ad server or SSP?

No. It's a read-only monitoring layer that watches across your ad servers, SSPs, SSAI endpoints and partner connections; it sits across them, it doesn't touch or replace them.

How is this different from my pacing dashboard or morning report?

A pacing dashboard tells you something moved, after the fact, with no dollar figure and no owner. Watching That detects the deviation as it happens on the monitor cadence, prices it in dollars, names the root and the owner, and routes it in about ninety seconds — before the hour compounds.

Start here

The drop,
named in dollars.

Anomaly detection in minutes, not the morning report — every deviation priced in dollars and routed to a named owner before the day compounds.