Adobe Summit 2026: What Data and Martech Leaders Should Know

3 days ago
4 min read

I was in Las Vegas earlier this week for Adobe Summit 2026. I attended the keynote, many different sessions and also had the chance to speak directly with a few Adobe reps on the sidelines. Being there in person gives you a different read on things. You pick up on what Adobe is genuinely excited about versus what's getting polished messaging for the main stage.

The dominant theme across almost everything was agentic AI. But a lot of the coverage coming out of Summit has focused on the creative and customer experience story. This post is a filter pass for analytics and martech leaders - what was actually announced, and what it means practically for data teams.

Adobe CX Enterprise: A New Platform, Not Just a Rebrand

The headline announcement was Adobe CX Enterprise, a replacement for the Experience Cloud brand and a significant restructuring of how Adobe's product portfolio fits together. The platform is organized around three pillars:

Brand Visibility
Customer Engagement
Content Supply Chain.

Underneath all three sits a new Adobe AI Platform with two intelligence systems. The one most relevant to data leaders is the CX Engagement Intelligence System which is the decisioning and optimization layer on top of AEP that connects audience signals, journey analytics, and real time event data to experience decisions.

For teams that own AEP implementations or feed data into Customer Journey Analytics, this is worth understanding. The intelligence layer acts on your data. That means the quality of your schema governance, event taxonomy, and data pipelines has a direct and visible impact on what CX Enterprise can actually do.

One notable positioning choice: CX Enterprise is designed to integrate with AWS, Anthropic, Google Cloud, IBM, Microsoft, NVIDIA, and OpenAI. Adobe is not asking enterprises to standardize exclusively on Adobe tooling, a meaningful shift from previous Summit messaging, and relevant for teams managing multiple vendor stacks.

The CX Enterprise Coworker: Orchestration With Human Oversight

Within CX Enterprise, Adobe introduced the CX Enterprise Coworker which is an orchestration layer that sits above the individual point solution agents Adobe has been building over the past two years. It monitors signals, recommends next best actions, and coordinates execution across channels, with humans staying in the approval loop.

Adobe has built two distinct levels of human oversight into the product: a practical acknowledgment that enterprise organizations aren't ready for fully autonomous AI decision making, particularly in customer facing workflows.

From a data perspective, the Coworker's output quality depends entirely on what it's working with. Inconsistent audience segments, attribution gaps, or unreliable journey data will surface quickly in an orchestration layer that acts on those inputs in real time. It's a useful forcing function for teams that have deprioritized data governance work.

AI Traffic and the Channel Attribution Problem

Adobe shared a notable data point on stage -- AI traffic to U.S. retail sites grew 269% year-over-year in March 2026. AI powered browsers, chatbots, and agents are increasingly becoming an intermediary between brands and their customers, and most analytics implementations weren't built to account for this.

Adobe's response is a Brand Visibility layer within Adobe Experience Manager and a new tool called Adobe LLM Optimizer, designed to help brands understand and optimize how they appear across AI driven discovery surfaces.

For analytics teams, the practical concern is measurement accuracy. Bot filtering rules built for traditional crawlers don't map cleanly to LLM-driven browsing behavior. If AI agent traffic is growing at this rate and isn't being identified or segmented correctly, channel attribution models are becoming less reliable over time. It's worth assessing how your current implementation handles this before it becomes a reporting credibility issue.

Credit Based Pricing: What to Clarify

More than 10 AI agents previewed at Summit 2025 are now in production and these cover data insights, audience creation, journey orchestration, site optimization, and experimentation. Adobe reports that many of their customers are already entitled to use them through a new credit based pricing model.

For any team heading into an Adobe renewal or evaluating AEP and the Adobe stack against alternatives, this is worth a specific conversation with Adobe. I don't think that usage patterns that were more predictable under legacy Analytics or CJA licensing would translate directly into credit based consumption. Understanding how agents are metered at your event volume before signing is important.

MCP: The Infrastructure Story Underneath the Announcements

Model Context Protocol received little attention in the keynote highlights but appeared throughout Adobe's technical announcements. I was in fact in a hands on lab session with a focus on building MCPs for CJA. CX Enterprise connects its agents, tools, and data sources through MCP endpoints under a shared governance layer.

MCP is becoming a standard mechanism for how AI agents communicate with external systems. The implication for analytics teams is that the data they produce i.e. event streams, audience segments, journey data will increasingly be consumed by agents programmatically rather than by analysts pulling reports.

This raises the bar for data layer clarity. Clean naming conventions, documented schemas, and governed pipelines matter not just for reporting accuracy, but because agents need semantically coherent data to act on reliably. It's a practical argument for investing in implementation governance work that can otherwise be difficult to prioritize.

Summary

Adobe Summit 2026 made one thing clear: analytics data is becoming operational infrastructure, not just a reporting input. The value of clean, well governed data foundations is becoming more visible and more consequential as agentic tools begin to act on that data in real time.

For analytics and martech leaders, the near term priorities are straightforward:

understand how AI agent traffic is affecting your measurement
clarify pricing implications before any Adobe contract decisions
get ahead of attribution fragmentation before it becomes a problem your team is asked to explain.