Data Management Platforms (DMPs) have helped publishers turn audience data into revenue for more than a decade.
They solved an important challenge: collect signals, build segments, and make those audiences available to buyers. That model worked when digital advertising revolved around browser-based targeting, cookie-driven activation, and a relatively simple idea of what publisher data was supposed to do.
But those expectations have changed alongside the convenience and reliability of walled gardens and the mass adoption of AI tooling. What’s expected of publishers today is exponentially more than it used to be, and publishers need the right infrastructure to keep up.
Where Traditional DMPs Fall Short
Traditional publisher DMPs emerged to organize audience data and activate segments against demand. They collect data, associate users with signals, build segments, and pass those segments into ad servers, SSPs, DSPs, and other activation systems. For many publishers that workflow still applies, and DMPs perform well around web-based audience packaging and existing Ad Ops processes.
Audience creation is now only a part of what publishers manage. They are expected to curate niche audiences for buyers and to do it at machine speed across multiple platforms. The ecosystem they navigate has grown more complex:
- Identity across multiple frameworks and alternative IDs
- Omnichannel inventory spanning web, app, CTV, audio, and gaming
- Advertiser and retail media collaboration without exposing raw data
- Privacy-preserving data-sharing requirements
- Signal enrichment and addressability in the bidstream
- AI-assisted and agentic workflows for planning, activation, and measurement
- Faster RFP response cycles and more custom audience requests
Each of these depends on a foundation that understands how identity works across systems, partners, and channels. A DMP on its own does not meet these demands. Publishers need better identity infrastructure to satisfy buy-side expectations.
Don’t Treat Audience Tools as Identity Platforms
Identity platforms and audience tools are undeniably related, but they serve distinct functions. Audience platforms allow publishers to identify who to include in segments and where to activate their audiences. Identity platforms answer broader questions, such as:
- Who is this individual across channels and devices?
- How should different identifiers relate to each other?
- How do we collaborate with partners without exposing raw data?
- How do we support new activation paths as buyer requirements change?
- How do we give AI agents a trusted data layer to work from?
Most publisher monetization workflows depend on identity: Audience building, signal enrichment, clean room collaboration, omnichannel addressability, and AI-powered audience discovery all depend on a robust identity foundation.
Relying solely on a DMP for audience creation is becoming unsustainable. The demands for speed, accuracy, depth, value, and compatibility with agentic AI require publishers to re-evaluate their platforms and the foundation they’ve built upon.
The Publisher Workload Goes Beyond the Web
The old DMP world was built for a single-channel ecosystem. The modern publisher business is increasingly expanding to a cross-channel and omnichannel approach.
Web audience activation still matters, but it’s no longer enough.
A publisher may need to monetize authenticated readers on the web, anonymous visitors in Safari, app users, CTV viewers, podcast listeners, and gamers in environments where browser-based workflows do not work.
If each channel requires a different identity workflow, data model, and activation process, the publisher ends up dealing with more fragmentation. The result is more operational work, less consistent addressability, and a weaker first-party data story for buyers.
This is why identity needs to sit underneath the full monetization system. Publishers need a way to connect signals across surfaces, preserve the right level of context by user, household, and device, and activate that intelligence wherever the demand is flowing.
Time-To-Revenue Matters as Much as Audience Depth
DMPs were built for audiences that grow as users return and qualify. That can work for always-on behavioral segments, but it creates problems when the sales team needs to move quickly.
Consider a campaign where an advertiser sends a CRM file or a brief for a custom audience and wants to launch in two weeks. The publisher may have the right data, but if the live audience depends on visitors coming back to the site before they can be counted or activated, the campaign starts with less reach than it should.
RFPs move fast, campaign windows are short, and sales teams can’t wait for audiences to mature before they put out a proposal.
The stronger model is retrievable data from day-one: connect the data, match it to your existing identity graph, and gain enriched signals immediately ready for audience building and activation. Imported CRM data, partner data, and clean room outputs are ready for activation from day one.
Most DMPs Don't Do Signal Enrichment
A DMP helps publishers package and activate audiences, but identity infrastructure can directly improve the value of the bidstream itself through signal enrichment
When a publisher can resolve identity in real time and add addressable signals to a bid request, the publisher creates value before the impression reaches demand. That may include resolved IDs, inferred identifiers, audience membership, or other signals that improve addressability.
Signal enrichment gives the identity layer a direct line to monetization. It can be tested, measured, and tied to programmatic performance.
Most DMPs can’t fulfill this need. Signal enrichment requires server-side identity resolution, support for alternative IDs, and ways to improve coverage for unauthenticated traffic. It also needs to work inside the latency expectations of programmatic advertising.
Data Collaboration Needs Secure Identity Infrastructure
Advertisers, agencies, retailers, and publishers increasingly need to work together without exposing raw customer data. Secure clean rooms make data collaboration possible, but they’re only as useful as the identity foundation underneath them.
A limited clean room workflow may help two parties match records and create an audience, but modern collaboration often requires more: activation and insights that both sides can trust, plus enrichment, measurement, and privacy controls that hold up under legal review.
The question is whether the platform can support the collaboration workflows publishers and advertisers actually use, across partners, identifiers, and governance requirements. Clean room platforms that connect to the same identity graph used for audience building, enrichment, and activation enables accurate data exchange and reduces the adtech tax incurred to manage separate tools for new partners and use cases.
AI Exposes Weak Data Infrastructure
A useful AI workflow for publishers needs access to the publisher's data, taxonomy, traits, audience definitions, identity graph, activation destinations, and business rules. It needs to understand what can actually be built, where it can be activated, and how it maps to the buyer's brief.
Layered on top of a weak identity foundation, AI tools will only generate inaccurate, incomplete, and irresponsible outputs. Whether that’s an audience that doesn’t actually exist or a deal that doesn’t align with budget, these unreliable results stem from lacking infrastructure.
Closed AI tools inside a single vendor interface may help with basic tasks, but publishers and agencies are already standardizing on their own AI tools. The more durable approach is to make the publisher's data platform accessible to the AI clients and agentic standards teams already use.
An AI assistant that can suggest audience ideas is helpful. An AI agent like Optable’s Audience Agent that can understand campaign objectives, find relevant existing audiences, propose new ones, build them, price them, and push them toward activation is even more valuable. For AI tools across the spectrum, the right data foundation will make or break their performance.
What Publishers Should Look for Beyond the DMP
The next generation of publisher infrastructure can’t just recreate DMP workflows in a shinier interface. Updated infrastructure needs to expand and accommodate::
Publishers should look for:
- Identity resolution across web, app, CTV, audio, and other environments
- Support for user, household, device, and custom identity scopes
- Alternative ID support that is part of the platform, not a one-time activation signal
- Coverage for unauthenticated traffic
- Day-one use of imported and connected data
- Signal enrichment as a measurable revenue workflow
- Clean-room collaboration across multiple use cases
- Activation across ad servers, SSPs, DSPs, Prebid, walled gardens, and cloud destinations
- AI workflows that connect to the publisher's real data and preferred AI tools
- A commercial model that does not punish growth through unnecessary activation taxes
Publishers shouldn't just ask, "Which DMP has the best audience builder?" They should also ask, "Which platform can support the monetization workflows we need now, and the ones we will need next?"
The Identity Infrastructure for Agentic Audience Planning and Activation
DMPs helped publishers create value from their audience data. The market has now moved beyond the problem DMPs were built to solve.
Publishers still need to find and build audiences, but they also need identity resolution, signal enrichment, clean rooms, omnichannel activation, and AI-ready workflows that adapt as new standards and buyer requirements emerge.
The next phase of publisher monetization will be built on identity infrastructure. Optable helps publishers build that foundation, so you can orchestrate audience creation, signal enrichment, data collaboration, cross-platform activation, and agentic planning from a single platform.
The DMP helped publishers monetize audience segments. Optable helps publishers monetize identity in the AI era. Schedule a demo today.
.png)
.png)
