Publisher monetization in 2026: why strategy sets the ceiling and ad ops sets the floor.

Chris Quinn of ProOps Consulting and I are both independent ad ops and monetization consultants, and we come at publisher work from different sides. Chris lives in end-to-end ad ops execution and process. I work on revenue strategy, TV & streaming, media strategy, and the executive conversations that go with them. We collaborate on engagements because the problems publishers bring us almost never sit cleanly in one lane.

We wrote this for publishers, monetization leads, and ad ops teams, not for other consultants. Five questions here, five more in part two.

What does healthy monetization look like for a publisher in 2026?

Chris: After 19 years in ad operations, my definition has gotten less glamorous and more straightforward: healthy monetization is boring. Campaigns deliver at 95% or better, invoices go out with numbers finance doesn't have to question, and nobody discovers a problem three weeks after it started costing money. The publishers in trouble aren't usually missing a clever strategy. They're missing the operational discipline to execute the strategy they already have. Direct-sold delivering on time, programmatic set up so it isn't quietly leaking yield, and a team that spends its day optimizing instead of firefighting. When the operations are healthy, revenue conversations get to be about growth instead of about what went wrong. It took me about a decade to appreciate how rare "boring" actually is.

Aaron: More than ever, healthy monetization requires diversification. Every traditional angle of publisher monetization is being squeezed for additional margin by the platforms and the buyers, so moving away from a strictly pageview-driven strategy matters. It's no longer just about how many page views you can drive. It's about what influence those page views have. The most successful publishers in 2026 monetize in a variety of ways beyond the traditional ad impression: events, subscriptions, merchandise. We've been talking about these for years, and now you can actually see a more holistic view of monetization take shape.

That said, every one of those channels still has a media portion, and as Chris says, that needs to be locked down and dead on. A functional ad ecosystem that is set up properly and makes you available where the buyers are will dramatically improve your monetization, and it's what lets you activate on those other channels at all.

What is the most common gap you see when you start working with a publisher's ad ops or revenue team?

Chris: Nobody owns the end-to-end. Specialization has done great things for depth and unfortunate things for visibility. One person knows the ad server, another knows programmatic, someone in finance knows what actually got billed, and the full picture from pre-sales to invoicing lives nowhere. So problems fall into the gaps between roles, and everyone is technically doing their job while revenue quietly walks out the door. The second most common gap is documented process, by which I mean any process that exists somewhere other than in one senior person's head. I've spent a lot of my career being that senior person, so I say this with love: that person will eventually take a vacation.

Aaron: The biggest gaps I see are knowledge and resources. Ad tech is a complicated beast, and there still aren't many people in the industry who understand both the technical foundations and the business side. Getting that full breadth of understanding typically takes a team, so publishers are doing the best they can with limited resources. I've worked with ad ops teams that had no idea what the sales process was, and sales teams who couldn't set up a campaign to save their lives. No one can see the full path from start to finish.

Why should a publisher care which collaboration model their consultant operates in?

Consulting collaborations come in different forms: institutional models, referral networks, collectives of independents teaming up on larger projects.

Chris: Because it tells you what happens when your problem stops matching their expertise, which it will, usually within the first month. A solo consultant who works alone will either stretch beyond their lane or quietly narrow your problem to fit what they know. An agency will solve it with whoever is on the bench that quarter. A consultant with a real collaboration network does something different: they keep the relationship, bring in the right specialist, and you get senior people on both sides of the problem instead of one expert improvising. Publishers rarely ask about this during evaluation, which is a shame, because "who do you call when this isn't your thing?" is one of the most revealing questions you can ask a consultant. The answer should have actual names in it.

Aaron: Each model has its use cases. For a massive project, an institutional model may make sense. In the spaces I play in, being a solo consultant lets me collaborate with other solo consultants who have a more specialized skill set than I do. Chris, for example, can go deeper on ad ops than I can. It doesn't make sense for me or my clients to waste time while I figure something out when Chris might already know the answer.

As a solo consultant, your job is to be self-aware enough to know what's legitimately within your scope and what's outside it. For the things outside your scope, the response shouldn't be to narrow the problem. It should be to find the best result for your client. Publishers often view the consultant as the source of all the answers, when the more realistic view is someone who will find you the answer. It's okay not to know everything. Anyone claiming they do is trying to sell you something.

What does a publisher get from two collaborating consultants that they wouldn't get from one?

Chris: Coverage without the markup, mostly. Aaron and I overlap enough to speak the same language and differ enough to catch each other's blind spots. I'll find the delivery issue in the ad server; he'll ask why the channel strategy made that inventory a priority in the first place. One of those questions without the other gets you half a fix. The publisher gets two senior perspectives, one engagement, and no junior team learning on their dime, which is the thing you're quietly paying for at a larger firm. There's also an honesty benefit that's underrated: when there are two of us, someone is always positioned to say "that recommendation benefits the consultant more than the client" out loud. Keeps us both honest. Mildly annoying, extremely useful.

Aaron: You obviously get the experience of both consultants and the specific skill sets they bring, which widens the coverage on your problems. But there's something else that's underrated: true collaboration. Having someone with the level of knowledge required to bounce questions, thoughts, and theories off makes for a better engagement. Problems get solved quicker, resolution comes faster, and it's easier because you're not one solo consultant trying to fix everything. A client can give context, but another experienced consultant in the room with their own perspective is what moves things forward.

I have a certain view on how things should be set up from a business perspective. Chris may have reasons why that's a good or bad idea. There's real value in having someone in the room who can counter my perspective.

What does a revenue strategy and CTV lens catch that a day-to-day ad ops lens can miss, and vice versa?

Aaron: This one's easy. Strategy is useless unless it's backed up by ad ops. The fastest way to find out whether a strategy is real is to open the ad server. I've walked into engagements holding a genuinely good CTV expansion plan and found there were no content signals being passed. I've found a macro passing a placeholder string more times than I can count. One particularly horrifying time, the publisher had set up a separate ad server just to serve GAM display tags. None of those show up in a strategy conversation. All of them cap what the strategy can earn.

Strategy sets the ceiling. Operations sets the floor, and I've watched far more publishers lose money to the floor.

Chris: I'll make the case for Aaron's lens, since he's contractually obligated to make the case for mine. Operational data tells you what's happening with impressive precision and no opinion about whether it should be happening. I can tell you a line item is pacing at 87% and exactly why. What the ops lens doesn't tell you is whether that campaign, that channel, or that whole revenue line deserves the effort. That's a strategy question, and it needs someone looking at market position, channel mix, and where the business is trying to go. The reverse is just as true, and I've seen it more times than I'd like: a genuinely smart strategy built on top of an ad server setup that could not deliver it. Strategy decks don't check trafficking templates. Someone should.