Case Study: Custom JWPlayer Ad-Pod Optimization Increased Aaj Tak's Ad Revenue by 364%+

Stock JWPlayer wasn't extracting the ad revenue a high-traffic live news deployment was capable of. Custom ad-pod and waterfall logic closed that gap.

By Sunil KumarStreaming Media Engineer, 20+ years · Updated July 2026

StreamKit built custom ad-pod and waterfall optimization on top of an existing JWPlayer deployment for Aaj Tak (India Today Group), increasing ad revenue by more than 364% without a platform migration.

The Client

Aaj Tak, part of India Today Group, is one of India's largest and most-watched live news platforms. Its player stack carries significant ad inventory, which makes ad-pod efficiency — how well every ad slot in every break is actually filled and monetised — a direct revenue lever, not a minor technical detail.

The Challenge

JWPlayer is a capable, widely-used video player, but its default ad-pod and waterfall behaviour is built for broad compatibility, not tuned to any one publisher's traffic, demand sources or audience mix. On a high-traffic live news deployment, that generic configuration was leaving meaningful ad revenue on the table — slots in each ad pod weren't being sequenced or filled as effectively as the available demand could support.

The Solution

Rather than accept JWPlayer's out-of-the-box ad-pod handling as a ceiling, the fix was custom waterfall and ad-pod logic layered on top of the player — controlling which demand source is asked first for each slot in a pod, how failed or low-value responses are handled, and how pod sequencing adapts to the specifics of this traffic and ad stack, instead of relying on generic defaults.

The Result

The custom ad-pod and waterfall optimization increased ad revenue by more than 364% compared to the default JWPlayer configuration — a direct result of filling more ad slots, with better-paying demand, more consistently, on the same underlying traffic.

Why This Matters Beyond One Player

The underlying pattern isn't specific to JWPlayer or to one publisher: most default player configurations are built for compatibility across use cases, not tuned to maximise yield for a specific traffic pattern and ad stack. Ad-pod and waterfall tuning is one of the highest-leverage, lowest-visibility levers available on an existing player deployment — it doesn't require replacing the player, just auditing and rebuilding how it handles ad monetisation.

Frequently Asked Questions

An ad pod is a sequence of ads shown together in one break. Waterfall logic decides which ad demand source gets asked first, second, and so on, for each slot in that pod. Poorly tuned waterfall logic asks lower-paying sources before higher-paying ones, or fails slots that a smarter sequencing would have filled — both of which quietly cap revenue well below what the same traffic could otherwise earn.

JWPlayer's out-of-the-box ad-pod handling is built to be broadly compatible across use cases, not tuned to a specific publisher's traffic, ad stack or audience mix. Without custom waterfall sequencing and pod-filling logic layered on top, a high-traffic live deployment can end up leaving fill rate and yield on the table that a tailored configuration would capture.

Yes. Ad-pod and waterfall optimization applies to any JWPlayer (or similar player) deployment carrying meaningful ad inventory — OTT platforms, VOD libraries and live sports all have the same underlying opportunity, though the specific tuning depends on each publisher's traffic patterns and ad demand sources.

Yes — this is exactly what a player performance review covers: analyzing current ad-pod behavior, waterfall sequencing and fill-rate data to identify where a default configuration is underperforming, before implementing custom logic to close the gap.

Related Services

Think Your Player Is Leaving Ad Revenue on the Table?

Get a player performance review that looks specifically at ad-pod fill and waterfall efficiency, not just playback metrics.