Automated QA across every config you run, every compliance rule you set, every partner you connect. The drift you didn’t know you had — caught before it ships.
A partner updates a bid-floor. A trafficker edits a daypart. An SSAI template inherits a new default. Nothing looks different on the dashboard; the confidence sat in the config, and the config drifted.
An alcohol spot runs against a daytime audience. A political creative slips past a freeze. A brand-safety rule fails silently. By the time it reaches the inbox it’s already a conversation you don’t want to be having.
Your ad server agrees with itself. Their SSP agrees with itself. Reconciliation between them is where the variance hides — and where the dashboard is least equipped to help you see it.
The QA layer that catches drift before it ships — backed by the layers that diagnose it when it does, and the runtime checks that make sure it doesn’t again.
Each monitor encodes one QA check — alcohol daypart, frequency cap, audience segment, partner bid floor, every rule a trafficker used to check by hand. The rule runs every ten minutes against the live ad-server API and deep-links straight back into FreeWheel or GAM the moment it fires. Three free for life. Top-tier broadcasters run 80+.
Walk the VM library →When the rule fires — or the layer underneath breaks
When a check still fires — or when something breaks underneath the checks — these are the layers that pick it up.
Every rule, every template, every partner-facing setting — surfaced side-by-side with its history. When a Validation Monitor fires, Inspect is where the diagnosis happens: the line that changed, the hand that changed it, the campaign shipped under the old rule.
Continuous runtime checks against your ad servers, SSAI endpoints, and SSP connections. No green-dot dashboards; only fires. When a system breaks underneath the QA layer — a partner SSP changes a config, a CDN drops a request, a feed times out — Monitoring names the break and the probable cause.
Confidence is one of four needs the Operations Control Platform handles. The other three sit in the menu above.
What the QA layer covers today, with two roadmap gaps shown honestly. Coverage extends as customer requests close real operational risk surfaces.
The same confidence problem. The same QA layer. Three tenants at steady state.
On a Friday night, a Validation Monitor caught a daypart-config drift that would have run an alcohol spot against a morning audience. The regulator wasn’t the first to know.
— Ad Operations Lead
Without the Watching That platform’s technology, the A+E team would not have had the ability to easily review the data trends we wanted to analyze.
— R. Lee Barstow, VP Revenue Operations, A+E Global Media
ReadWatching 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
ReadThree meters Confidence moves.
Alcohol daypart breaches, political-creative violations, freeze-window slips — these don’t show up as anomalies. They show up as fines. Six figures in the UK. License-pulling in the US. The QA layer catches the config drift before the breach is the breach.
Brand-safety failures don’t error and don’t alert. They surface in a Slack from the CMO with a screenshot. The QA layer enforces the brand-safety rule against the live config, every ten minutes, before the screenshot exists.
A daypart drift, a frequency-cap inheritance, an audience-segment rename — these don’t break campaigns; they just spend wrong. A 3% drift on a $50M campaign is $1.5M of waste reconciliation will catch four weeks too late. The QA layer catches it on the live config.
Three meters. One QA layer. The math gets attention from finance every time.
Three tenants. One QA layer. Same confidence problem, solved once.
