Why DOOH publishers are running two systems, and what it’s costing them

If you run a DOOH network on a modern ad server, there’s a good chance your programmatic demand lives inside the platform and your direct IO campaigns live somewhere else entirely.

A spreadsheet. An email chain. A separate booking system your ops team built around a process that predates the platform you’re using today.

It works. Until you look at what it’s actually costing you.

The split that became standard

Direct IO has always been the backbone of DOOH revenue. Guaranteed plays, fixed creative, scheduled delivery, buyers who want a commitment and networks that can make one. That buying pattern didn’t disappear when programmatic arrived. It stayed, because the certainty it offers isn’t something an auction model replicates.

What happened instead is that publishers ended up managing two separate demand streams with two separate processes. Programmatic inside the platform, optimised and reported in real time. Direct outside it, tracked manually, reported separately, and operationally disconnected from everything else the network runs.

For many publishers, this split is so embedded it’s stopped feeling like a problem. It’s just how DOOH operations work.

But consider what it actually means in practice. A buyer asks how their guaranteed campaign is pacing alongside their programmatic activity on your network. You pull data from two places. A new direct IO campaign comes in. Someone on your team creates a booking outside the ad server, sets up manual tracking, and manages delivery separately from everything else. A campaign ends. Reconciliation happens across systems that were never designed to talk to each other.

Every one of those moments is operational overhead that a unified workflow would eliminate.

The demand you’re not capturing in one place

The split workflow is a symptom. The underlying issue is that the majority of DOOH demand, the 75–80% of budgets still booked direct, has never been accessible through the same infrastructure publishers use for everything else.

That’s not because buyers don’t want a platform experience. It’s because platforms haven’t offered the delivery model that direct IO buyers require: guaranteed plays, fixed creative, predictable spend, and the ability to commit to a schedule. Without that, publishers have had no choice but to manage direct demand outside the system.

The result is a platform that handles a fraction of available revenue, with the rest living in processes that don’t scale, don’t integrate, and don’t give publishers or their buyers a unified view of performance.

Direct campaigns, now in your ad server

Share of Voice (SOV) by Perion is built for publishers who are already on Perion One and want to stop running two systems.

It’s a new campaign purchase type inside the platform that lets publishers bring their direct IO campaigns into the ad server with minimal workflow change. The same platform used to manage programmatic demand now handles guaranteed delivery: fixed share-of-voice, fixed creative, scheduled plays, managed and reported in one place.

Two delivery modes fit how different networks operate. Fixed SOV for clean, predictable share-of-voice. Per-Screen Catchup for guaranteed plays per screen, with automatic catch-up if plays are missed, a stronger commitment for buyers who need screen-level accountability.

No new infrastructure. No new booking system. No parallel process to maintain. Direct campaigns move into the workflow publishers already run.

What one integration changes

For publishers already on Perion One, SOV means the direct campaigns that have always lived outside the platform can now live inside it. Unified reporting. Unified inventory management. One view of how your network is performing across every demand type.

For DOOH networks evaluating a platform for the first time, it means not having to choose between a system that handles programmatic and a separate process for direct. One integration covers both from day one.

The operational overhead of the split doesn’t have to be permanent. It was always a workaround for a capability the platform didn’t have.

Now it does.

Already on Perion One? Talk to your publisher team about activating SOV for your network.

Connect with us.