Ad Ops Impressions | Publisher Ad Operations Insights

Why Promising Revenue Ideas Get Stuck in the Ad Stack

Written by adops.com Team | November 12, 2026

 

A good revenue idea isn’t always easy to execute

You have a revenue opportunity worth pursuing: sales wants to offer a new ad product, or a programmatic partner could help monetize inventory that isn’t earning enough. As the idea takes shape, the technical questions start.

Development needs to understand what changes on the site, while legal reviews consent and the data team flags a missing connection. Everyone has a valid concern, but you still don’t have an answer to the business question: can we make this work?

For publisher leaders, that uncertainty makes it hard to decide where to invest. Moving forward starts with turning those separate concerns into a clear set of choices.

The request and the goal aren’t always the same

A request like “integrate this partner” can sound complete, even though it names the solution without explaining the reason for doing the work.

Which inventory needs more demand? What does the advertiser need from the new format? What result would make the effort worthwhile? Those answers help technical teams evaluate the request against the business need.

Those answers also create room for alternatives. With a clear goal, the team can change the proposed implementation without sending the entire opportunity back to square one.

“Publishers often come to us with an idea of how to reach their goal. Our job is to understand the need behind it and explore what it will take to make it work.”

Katrina Perigo | Sr. Director, Business & Technical Services

adops.com

A technical blocker is a business decision, too

Deciding how to respond to a technical concern means understanding its consequences for the business. It could involve more work before launch, a change to the ad product or an ongoing cost that outweighs the benefit.

For a new demand-partner integration, for example, data transparency, ad parameters, consent and page speed all affect whether it will work as intended. The commercial owner needs to understand which issues are fixable and what fixing them involves.

Three common situations show how that conversation can become more concrete:

  • Missing data connection. Identify what information the integration needs, where it comes from and what must change to make it available. The business can then weigh that prerequisite work against the opportunity.
  • Unsupported ad behavior. Ask which part of the experience matters to the advertiser. That gives the team a basis for comparing changes to the site with a simpler version of the product.
  • Heavy maintenance. Look beyond the initial build. If a customized feature takes substantial work to keep running, include that effort when judging its value.

“My advice is to customize where it makes your day easier or more effective, but never to the point where you’re investing more time maintaining that system than benefiting from it.”

Katrina Perigo | Sr. Director, Business & Technical Services

adops.com

The right answer may not be the original plan

Once the implications are clear, the business can choose whether to proceed with the required changes, adjust the implementation to preserve its value or defer the part whose cost or risk doesn’t yet make sense.

That choice can vary across an initiative, so a feature that isn’t ready does not automatically have to hold up everything else.

For one publisher launching ads through Google Ad Manager for the first time, adops.com helped develop alternatives when requests couldn’t work within the existing stack. After assessing the risks, the publisher held back certain ad products and left a few low-risk issues for after launch. Understanding the options made those decisions possible.

Katrina describes the team’s contribution as being able to “translate needs cross-department in a meaningful way, identify risks, and recommend alternative approaches.”

Connecting the dots across teams

Making those connections takes input from across the business. Sales understands the opportunity, developers understand the systems, and legal and data teams bring requirements that shape what can be built. A workable approach has to account for all of those perspectives.

adops.com helps bring that picture together, working across publisher teams and vendors to translate business needs into technical requirements, explain constraints and develop alternatives. Experience across different publisher environments helps us recognize dependencies that may be easy to miss when each team sees only its part.

The result of that conversation should be specific: what can be delivered, what needs to change and which decisions the business still needs to make.

If an ad product or integration is stuck, bring the discussion back to the outcome you need. Ask what each blocker means for that outcome, then compare the ways forward.

You don’t need a finished technical specification to start that conversation. If your team needs help connecting a revenue opportunity to a workable plan, talk to adops.com.