01 · Configs
Set by hand, across systems that don’t check each other.
Dayparts, caps, segments and partner rules, all set by hand across systems that never check each other. A daypart that won’t fire stays invisible until it’s live.
Operations Control Platform · Confidence
Ship every campaign knowing it's clean.
Automated QA across every config, compliance rule and partner handoff — so the misconfig, the breach or the broken handoff is caught before launch, not after the advertiser or the regulator.
The problem
A campaign breaks before it ever goes live.
In the config, the compliance rule, or the partner handoff. You don’t see it in the UI — you see it when the advertiser complains, the regulator calls, or the revenue doesn’t show.
Before
Eyeball each campaign in the ad-server UI, one system at a time, and hope nothing breaks once it’s live.
After
Checked automatically, across the whole stack, against every rule you set — flagged off-spec before it ships.
02 · Compliance
Alcohol, gambling, pharma, political — on every line.
Alcohol, gambling, pharma, political, brand-safety — they have to hold on every line. When one slips, the regulator finds it before you do.
03 · Partners
Every handoff is a place it can silently break.
Every SSP, ad server, SSAI and distribution handoff is a place it can silently break.
What we do · Validation Monitors
A QA layer across your stack.
Watching That runs a library of ~100 Validation Monitors spanning configs, compliance and partner handoffs. They check every campaign against the rules you set — before it ships and at every handoff. Inspect on demand, or let them watch continuously. When something’s off-spec — a daypart that won’t fire, a restricted creative in the wrong slot, a handoff dropping impressions — you know while you can still fix it. Read-only: it validates what’s configured, it doesn’t touch your ad server.
Proof
What it's worth to catch it before it ships.
Broadcaster · Compliance (anonymised)
80+
Validation Monitors in production
A major broadcaster runs 80+ Validation Monitors in production across configs, compliance and partner handoffs — so the regulator wasn't the first to know.
— Broadcaster · Compliance (anonymised)
Publisher · New York Post
2M+
daily impressions protected, video + display
“Watching That has given us full control of our video advertising… find, fix and solve revenue-impacting issues much more quickly.”
— Amanda Gomez, VP Revenue Operations, New York Post
We already plug into your stack.
Read-only QA across SSP / ad server / GAM / SpringServe
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
…and the SSAI and distribution handoffs in between.
Questions
Validation Monitors, answered.
What does Watching That validate?
Configs (dayparts, frequency caps, audience segments, partner rules), compliance constraints (alcohol, gambling, pharma, political, brand-safety), and every partner handoff (SSPs, ad servers, SSAI, distribution) — around 100 checks in the Validation Monitor library, against the rules you set.
Does it replace my ad server or SSP?
No. It's a read-only QA layer that validates what's configured across your systems; it sits across them, it doesn't touch or replace them.
How is this different from QA'ing in the ad server UI before launch?
Manual UI checks are point-in-time, one system at a time, and miss the seams between systems. Validation Monitors check every campaign against every rule across the whole stack, automatically, before ship and at every handoff.
Is it real-time?
No. The Monitors run on an automated, continuous cadence — and they validate before a campaign ships, which is the point: catch it pre-launch, not after.
What happens when something's off-spec?
You're flagged before it goes live — a daypart that won't fire, a restricted creative in the wrong slot, a partner handoff dropping impressions — while you can still fix it, so the advertiser, the regulator or the CRO isn't the first to know.
Start here Ship it clean.
Ship it clean.
Every campaign.
Caught before it’s live, not after.
No card. No sales call. Read-only API — connect in minutes, see your first flags this week.
Keep reading
Four routes.
Early warning on revenue risk
Once it's live: know the moment revenue moves, priced in dollars.
/solutions/early-warning
Answers when something breaks
When it breaks: why it moved, and which system — one verdict three teams agree on.
/solutions/answers
Visibility across your stack
The bottom line: every feed reconciled into one number.
/solutions/visibility
The whole platform
When the whole stack matters, not just one campaign — see the platform.
/platform