Video news publishers
Pre-roll and mid-roll ads on news clips. Demand waterfall ensures fill while consent gating keeps personalized demand competing for opted-in users.
A branded IMA video player with consent gating, demand waterfall, viewable-only refresh, and an outbound-data inspector. Built for publishers running their own video catalog.
This is the real player. Accept consent, press play — a sample VAST creative renders, then content plays. The beacon stream surfaces every event in real time.
The IMA SDK wrapped in branded chrome. Every event surfaced. Every config tunable from your dashboard.
Consent is a hard gate. Rejected — no ad request fires. Accepted — signals pass through cleanly.
Instream video is built for publishers who host their own video content and want a player that respects content as much as ads. The IMA SDK core gives demand parity with the largest player vendors.
Pre-roll and mid-roll ads on news clips. Demand waterfall ensures fill while consent gating keeps personalized demand competing for opted-in users.
Long-form content with ad pods. The player supports multiple ad breaks per session with frequency capping per pod.
Live and near-live video with consent-gated pre-roll and viewability-aware mid-roll. The outbound data inspector helps demand teams troubleshoot bid-level issues in real time.
Tutorial videos with conservative ad frequency. Refresh is viewability-only, so ads pause when readers leave the tab.
Short-form video catalogs benefit from the player's content-aware ad scheduling — ads insert at logical breakpoints, not at fixed timestamps.
Companies hosting product videos and webinars use the player as a unified delivery surface, with revenue from pre-roll where the publisher chooses to monetize.
The Pub Clarity instream player is a thin shell around the Google IMA SDK — the same engine that powers Google's own video ad delivery across YouTube and partner networks. We do not re-implement VAST parsing, ad scheduling, or VPAID handling; we use the canonical, well-tested SDK and focus on the parts that vendors typically get wrong: consent, refresh discipline, demand waterfall, and reporting.
Consent is enforced at the IAB TCF v2 layer. The player reads the TCF consent string at load time. If the user has rejected purposes 1 or 2, no personalized ad request fires; the waterfall falls through to non-personalized demand sources. The Outbound Data Inspector panel surfaces the exact ad-request URL on every auction so demand teams can verify what signals are being sent.
Refresh discipline is viewability-gated and tab-aware. The viewability counter pauses when the player is less than 50% on screen or when the browser tab is inactive. This matches Google's policy minimum and keeps inventory off Made-for-Advertising flags.
The demand waterfall is configured per-publisher in the dashboard. Each demand source has a floor CPM and a tag URL or simulation flag; the waterfall walks sources highest-floor-first and stops at the first fill. Reconciliation pulls actual revenue from each demand partner's reporting API every three hours, so the dashboard shows ground truth — not estimates.
Indicative ranges for instream video on Pub Clarity. Numbers vary with content length, demand mix, and audience composition.
Benchmark ranges reflect Pub Clarity's South & Southeast Asia publisher cohort. Individual publisher results vary with traffic source, vertical, and demand mix.
The questions video publishers ask before adopting the player.
Yes. The demand waterfall is publisher-configurable. Add your existing VAST endpoints with a floor CPM; the player will include them in the waterfall sequence. Direct deals, GAM video line items, and SSP video tags all integrate.
VPAID 2.0 is supported via the IMA SDK. The player respects publisher-side VPAID restrictions if you have disabled VPAID in your demand chain.
The player supports ad scheduling at any timestamp, but we recommend skipping mid-roll on content under 3 minutes. Reader tolerance for mid-roll scales with content length; data from our cohort supports this guideline.
Yes. Live and near-live content with periodic ad breaks is supported. Ad breaks fire at publisher-configured intervals; the player resumes content cleanly after each ad pod.
The Pub Clarity dashboard's Reports section includes a video metrics group: starts, quartile rates, completion rate, view-through rate. Reconciled revenue is per video and per ad break.
Theme colors, control visibility, and brand accents are publisher-configurable. The IMA SDK's native controls remain for ad playback (Google policy); content controls are themable.
Apply for the SSP, register your video site, embed by siteKey.
Apply as a publisher →