NY Post’s revenue-operations team needed to find, fix, and solve revenue-impacting issues across their video advertising in real time — across GAM, eight SSPs, and partner deals. They run Watching That for diagnostics, troubleshooting, and reporting — and protect 2M+ daily impressions.
“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. And their rich business grade reporting means everyone is always in the know about where we are, what needs to be done and how to go about it.”
Before programmatic-first publishers stand up an independent reconciliation, every programmatic conversation starts with a disagreement about the numbers. The team spends its judgement on reconciling — not on deciding what to do about what the numbers meant.
Each supply partner reports against its own definition of a served impression. GAM reports against its own. Reconciling them takes a weekly spreadsheet pull, a call with each rep, and an apologetic note to finance about which number to trust.
On programmatic-first publishers managing video + display supply, partner-level fill rate can degrade for a fortnight before anyone notices, because the dashboard that rolls everything up averages the loss into invisibility. By the time it shows, the PMP renewal is already in motion.
When the monthly variance lands, each SSP’s rep has a different story. Without an independent log of what the page actually rendered, the publisher’s team is negotiating against five narratives with no evidence of its own.
Illustrative timeline. The first month a reconciliation is live across all eight SSPs, one partner’s reported impressions can diverge sharply from the independent log. The beats below show what the audit looks like next.
Inspect, Analysis, and Report run against the same live data layer the Post’s revenue-operations team works in — so an issue that touches GAM, an SSP, and a partner deal surfaces as one root cause, not three escalations.
NY Post’s revenue-operations team uses Inspect for log-level event access — the diagnostics surface for revenue-impacting issues across GAM, eight SSPs, and partner deals.
The Analysis module correlates the delivered-vs-expected signal across the supply chain — so an issue that touches GAM, an SSP, and a partner deal surfaces as one root cause, not three escalations.
Reports rendered against the same live data layer the operators work in — so the CRO view and the trafficker view match, every time.
