imagino » Resources » CDP vs. CCMH: Why Forrester’s Two 2026 Reports Describe One Problem
CDP vs. CCMH: Why Forrester’s Two 2026 Reports Describe One Problem
Twice this year, Forrester looked at the B2C marketing stack and reached an uncomfortable conclusion from two different angles. In Q1, it was the B2C CDP Landscape: most teams’ data foundation is expensive to justify and hard to prove out as 72% of senior marketing decision-makers say their CDP is moderately or significantly expensive to implement and maintain over three years. In Q2, it’s the Cross-Channel Marketing Hubs Landscape: most teams’ orchestration layer is deployed in parallel to their enterprise AI strategy, not as part of it.
Most brands treat these as two separate purchases: two vendor evaluations, two budget lines, two roadmaps that rarely talk to each other. Read together, Forrester’s own research suggests that’s the wrong frame. The two reports aren’t describing two problems. They’re describing one problem, viewed from opposite ends of the stack.
What the CDP Landscape report actually found
Forrester’s B2C CDP Landscape, Q1 2026 provided an overview of 23 vendors and landed on three findings worth remembering. Cost is the headline, that 72% figure, but the more interesting finding is why the cost is hard to justify: most CDPs are still primarily data-transit layers. They collect, unify, and store customer data well. What they don’t do is act on it. Forrester identifies the market’s shift toward decisioning and orchestration capabilities as the defining trend, and names agentic AI as the disruptor that will separate the vendors who make that shift from the ones who stall.
imagino was named among the 23 vendors included. But the finding that matters more than the recognition is the diagnosis: a CDP that stays in the data-transit lane hits a value plateau. All the unified profiles in the world don’t generate ROI if nothing downstream can act on them in real time.
The Cross-Channel Marketing Hubs Landscape, Q2 2026 picks up exactly where that leaves off. Forrester defines a CCMH as “Enterprise marketing technology that supports customer data management; analytics; segmentation; and workflow tools for designing, executing, and measuring marketing engagement across digital and offline channels.” In plain terms: it’s the layer that’s supposed to act on the data a CDP unifies, providing an overview of 28 vendors this time, including imagino. Three findings from the report stand out: “Cross-channel marketing hubs is an established market.” Second, Forrester flags a specific gap: most CCMHs are deployed in parallel to the enterprise AI strategy rather than as part of it, so marketing owns the hub while IT and data teams own the AI strategy — and the two rarely share a governance model. It’s the same disconnect the CDP report describes from the other side of the stack, and it’s the thread the rest of this piece pulls on. “Agentic AI enables CCMH buyers to innovate marketing with autonomous real-time customer engagement.”
That’s the top disruptor Forrester identifies for the category with the shift from assistive AI that makes campaigns more efficient to always-on intelligence that senses, decides, and acts across channels in real time.
imagino is recognized among the 28 vendors included, for and self-reported the extended use cases of: contextually relevant customer experiences, individualized customer understanding, and unified customer journey orchestration as the top three for which clients select them.
Core work vs. real orchestration
One of the more useful things in the CCMH report isn’t a finding, it’s rather a framework. Forrester splits CCMH functionality into core use cases and extended use cases. Core is table stakes: campaign planning and development, customer data and profile management, personalized promotional campaigns, segmentation and audience building. Every vendor in the report can do this; it’s the minimum bar to be considered a CCMH at all.
Extended use cases are where the differentiation actually lives: brand and customer experience design, contextually relevant customer experiences, individualized customer understanding, marketing measurement and optimization, personalized offers and recommendations, and unified customer journey orchestration. This is the list that separates a hub that executes campaigns from one that orchestrates a genuinely connected customer experience, and it’s a useful lens for evaluating any vendor, imagino included: which of these six is the vendor actually built for, versus bolting on to check a box?
The same wall, hit from two different directions
Put the two reports side by side and the pattern is hard to miss. A CDP that never leaves the data-transit lane hits a value plateau, plenty of unified data, no way to act on it. A CCMH that runs in parallel to the enterprise AI strategy hits the same wall from the other side, plenty of orchestration tooling, but disconnected from the governed AI actually making decisions elsewhere in the business.
Whichever end of the stack a team starts from, the failure mode is identical: two systems, two AI strategies, and no shared brain between them. Fixing one side without the other just moves the disconnect, it doesn’t close it.
What “unified” actually requires
From our point of view, Forrester isn’t arguing for a single monolithic suite, quite the opposite. Its own research notes that today’s CCMH buyers prioritize ecosystem flexibility, modular packaging, and strong integrations over vendor lock-in. Unification isn’t about buying everything from one company. It’s about one governance model for decisioning, whoever builds the individual pieces.
That’s the distinction worth sitting with: a data foundation and an orchestration layer governed by the same AI framework won’t duplicate, or contradict, decisioning logic between them. One that isn’t will, no matter how good either half is on its own. It’s the architecture imagino was built around: an embedded CDP feeding a single orchestration layer, governed end-to-end by Imogen, imagino’s AI framework, across discovery, design, activation, and amplification, with governance built in throughout rather than bolted on afterward.
What to actually evaluate
If you’re in the middle of a CDP or CCMH evaluation, or about to start one, three questions cut through most vendor pitches faster than a feature comparison:
Is your data foundation and your orchestration layer governed by the same AI framework, or two different ones that don’t talk to each other?
When you evaluate a CCMH, are you scoring vendors on core use cases alone, campaign execution, data management, or on the extended ones, like unified journey orchestration, that Forrester says actually differentiate the category?
Where does agentic AI sit in the roadmap, a bolt-on feature, or a native part of how the platform makes decisions?
For us, these two reports are worth reading together, not separately, the full picture only shows up when you do. The B2C CDP Landscape, Q1 2026 report is now available to you to read.
If you’re in the middle of either evaluation, we’d welcome the conversation, no pitch deck required.
Forrester does not endorse any company, product, brand, or service included in its research publications and does not advise any person to select the products or services of any company or brand based on the ratings included in such publications. Information is based on the best available resources. Opinions reflect judgment at the time and are subject to change. This report is part of a broader collection of Forrester resources, including interactive models, frameworks, tools, data, and access to analyst guidance. For more information, read about Forrester’s objectivity here .
EN
FR
EN (US)