A pause, menu, or overlay tag can declare OMID and still schedule linear quartiles the CTV SDK never fires.

The November 10, 2026 OM SDK expansion is already written up as an exchange problem: the player session can measure a creative the gateway rewrote before OM started. That note is OM SDK for pause and overlay CTV. This one is the tag the buyer uploads before any wrapper runs.

Pause, menu, and overlay units in the CTV Ad Portfolio are NonLinear. The events that describe them are creativeView and overlayViewDuration. A document that also lists firstQuartile, midpoint, and complete under NonLinearAds still parses. Those pixels belong on a Linear creative. The portfolio player does not schedule them for the overlay, so the endpoints stay at zero while the Impression bills.

The same tag often adds an OMID JavaScriptResource because the November 10 release named those formats. Declaring the script is not the same as learning that the SDK skipped it. verificationNotExecuted lives on the Verification node, and the tracker should carry the [REASON] macro. Leave it off and a native build that never runs the script looks like a clean session with empty quartile logs.

What the portfolio player actually schedules

The Netflix pause note is the creative shape: NonLinear width and height, creativeView, overlayViewDuration, and Duration when the asset is video rather than a still. Menu and screensaver units use the same split between a linear progress clock and an overlay dwell clock. Copying a mid-roll tracking block into the pause tag does not move the player onto the linear clock.

OMID does not move those events either. The verification script reports the session through OM SDK. Quartile URLs under NonLinearAds are a second contract the overlay path does not fire. A trafficker who pastes the mid-roll Linear events, then adds AdVerifications so the tag matches the release, ships both. Only the overlay events and the verification resource are in the path the SDK runs.

apiFramework on that resource is omid, lowercase. Vendor snippets still ship uppercase OMID, and strict parsers reject it. browserOptional true tells a native player it may skip the JavaScriptResource when an OM SDK integration is already in the app. The November 10 release points Android TV and tvOS at the native SDK builds, and Samsung and LG at the HTML5 and web video SDK. One tag sent to both will execute the script on the web-video set and may skip it on the native set.

The sample has no verificationNotExecuted tracker, so the native skip has nowhere to report a reason. The Impression still fires. firstQuartile and complete stay quiet, which looks like a player bug rather than events that were never on the overlay clock. How to validate AdVerifications is the envelope. OMID in VAST is the resource shape, including browserOptional and the [REASON] macro.

What to put on the tag instead

• Keep the still or the video in NonLinear. Do not add a Linear creative to force quartile pixels.
• Track creativeView. Track overlayViewDuration when the format has a duration to report, and include Duration on a video NonLinear so that beacon has a timeline.
• Put one Verification per vendor under AdVerifications, with an HTTPS JavaScriptResource and apiFramework omid.
• Add verificationNotExecuted with the [REASON] macro on that Verification. Do not hang it under NonLinearAds.
• Set browserOptional only when a native OM SDK integration is actually on the device. A web-video app that skips the script and has no tracker reports nothing.

Check the file the player will parse

Fetch the live URL in the VAST tag tester. If the response is still a wrapper, walk the hops in the VAST inspector. For the OMID handshake on a sample creative, the IAB-style VAST tester is an independent fork, not an IAB Tech Lab product.

vastlint checks the envelope: verification resources, the verificationNotExecuted tracker, and NonLinear shape. It does not certify an OM SDK build, and it does not execute the script. An agent that emits this tag because the release named pause ads still has to pass that check. The exchange rewrite is a separate failure, already covered in the November 11 note.