Why SSAI doesn't solve CTV ad measurement
When a channel moves to server-side ad insertion (SSAI), ads start playing correctly on smart TVs, set-top boxes and apps — with no dependence on client-side ad libraries or ad blockers. Hence the common but wrong conclusion: "we've put SSAI in, now everything is transparent." Delivery and measurement are different engineering problems, and SSAI solves only the first.
Once the ad is stitched into the stream server-side, the natural client-side context of the impression disappears: on-screen visibility, completion and, above all, the ability to verify independently. The SSAI server's own logs are your number, and the advertiser wants a number they trust. That gap, not delivery, is what you have to close.
The standard that does it is OMID (Open Measurement Interface Definition, the OM SDK from IAB Tech Lab). It lets you pass independent verification resources — IAS, DoubleVerify, Nielsen — into the player so viewability and impressions are counted on the client even when the ad was inserted on the server. For SSAI this is the key detail: without OMID (and without a stable device graph to resolve impressions into unique reach) you've simply moved the "black box" from the player to the server. And don't confuse OMID with SIMID — the latter is about ad interactivity, not measurement.
The practical takeaway is simple. An OTT provider should build OMID support and server-side tracking in from day one, not "sometime later." An advertiser should ask not "do you have SSAI" but "how exactly are impressions counted, and who verifies them." And a sales house should remember that an impression's video proof settles the argument about whether an ad played — but it doesn't replace a reach metric.
Newsletter
Once a month — new posts and the key takeaways. No spam.