Why AdTech is getting harder to manage.

Media companies have more advertising technology at their disposal than ever before. From audience intelligence and campaign execution to measurement and AI, the options keep expanding. But managing all these technologies is becoming increasingly difficult.

In practice, it often makes the environment harder to manage. The challenge is no longer simply finding technology that can do a particular job. It is making sure those technologies can work together in a way that supports the business. That is becoming one of the central problems in AdTech, and it is why orchestration matters more than it did even a few years ago.

For media companies, the question is shifting from “What should we add?” to “How do we make what we already have work as one system?”

Complexity is becoming the default.

Modern media environments are rarely built around a single platform. They are usually a collection of systems that have evolved over time, often through new business models, acquisitions, changing consumer behaviour and successive waves of technology investment.

One system may handle content delivery. Another manages audience data. A separate platform supports ad decisioning, while others provide identity, attribution, commerce signals or analytics. AI is now being added on top of that stack, creating new possibilities but also new dependencies.

Each platform may perform well on its own. The problem appears when the business needs them to work together.

A campaign may require audience data from one environment, content metadata from another and measurement from a third. An AI agent may need to access several systems before it can take a useful action. A new commerce capability may depend on data that was never designed to move beyond the system where it was originally captured.

Even the most sophisticated platforms can create headaches when they aren’t designed to work together.

Integration is necessary, but orchestration goes further.

Integration is usually the first word that comes up when systems need to communicate. It is important, but it does not fully describe the challenge.

Two platforms may be technically integrated and still create a poor operating environment. Data may move between them, but not quickly enough. Workflows may still require manual intervention. Permissions may be inconsistent. Teams may see different versions of the same customer or campaign. A connection may exist without actually improving how the business works.

Orchestration goes further. It is about designing how systems, data and workflows behave together across the broader environment.

That means deciding what information should move, when it should move, what should trigger an action, which system is authoritative, where human approval is required, and how performance is observed across the entire workflow. It also means creating enough flexibility that new capabilities can be introduced without rebuilding everything around them.

This is not simply an integration problem. It is an architectural problem.

Fragmentation has a business cost.

Technology fragmentation is often treated as a technical inconvenience, but its impact reaches much further.

When systems do not work well together, teams spend time reconciling information, moving data manually and working around platform limitations. Decisions take longer because no one has a complete view of what is happening. New capabilities take longer to launch because each addition introduces another set of connections and dependencies.

The problem compounds over time.

A media company may have excellent advertising, data and measurement platforms, but if those environments operate in isolation, the organization can still struggle to answer basic questions quickly. Which audiences are responding? Which content is contributing to engagement? Which campaigns are producing incremental value? Where should the next dollar be spent?

The technology exists to answer many of those questions. The architecture often determines how difficult it is to get the answer.

That distinction matters because complexity can quietly become a growth constraint. What begins as  technical debt eventually affects speed, experimentation, revenue and customer experience.

AI will expose weak architecture faster.

The rise of AI makes the orchestration problem even more important.

AI systems are most valuable when they can operate in context. That usually means access to data, platforms and workflows across the organization. An agent that can only observe one isolated system may be useful, but an agent that can safely understand and act across multiple environments has much greater potential.

That potential also raises the stakes.

If underlying systems are fragmented, poorly governed or difficult to access, AI will not magically solve the problem. In many cases, it will make the limitations more obvious. A model cannot create a reliable answer from inconsistent data. An agent cannot automate a process it cannot access. A workflow cannot move faster if every action still depends on manual handoffs.

AI is therefore not only creating new capabilities. It is increasing the value of well-designed architecture.

Organizations that have already invested in interoperability, data access, permissions and observability will be better positioned to operationalize AI. Those that have not may find that their biggest AI challenge is not the model at all.

Consolidation is not the only answer.

When complexity increases, the obvious response is often to consolidate. Fewer platforms should mean fewer problems.

Sometimes that is true, but sometimes it is not.

Large media organizations often have legitimate reasons for maintaining multiple systems. Different business units may have different requirements. Best-of-breed platforms may outperform broader suites. Legacy systems may still support critical workflows. Strategic flexibility may be more valuable than standardization.

The goal should not automatically be to put everything on one platform. The more important objective is to create an environment where systems can participate in a coherent architecture.

That means interoperability becomes a design principle rather than an afterthought.

Technology decisions should consider not only what a platform can do independently, but how easily it can exchange data, participate in workflows, support governance and adapt as the environment changes. A powerful tool that creates another isolated system may solve one problem while making the broader ecosystem harder to manage.

Orchestration is becoming a competitive capability.

The organizations that manage this complexity well will have an advantage.

They will be able to introduce new advertising capabilities faster because the underlying architecture is designed to accommodate them. They will be able to use data more effectively because important signals are not trapped inside individual platforms. They will be able to operationalize AI faster because systems can provide the context and permissions those workflows require.

Most importantly, they will be able to change more quickly.

That may be the most important benefit of orchestration. In an industry where technology, audience behaviour and business models continue to evolve, architecture needs to support what the business wants to do next, not simply what it does today.

Media companies will continue adding new platforms, new data sources and new capabilities. That part is inevitable. The strategic question is whether each addition makes the overall environment stronger or simply more complicated.

Before investing in another AdTech platform, media companies should consider how it will work with their existing systems. A new tool is only as valuable as the workflows and business outcomes it supports.