If you’ve ever been in a kickoff meeting for a new Adobe Real-Time CDP engagement, the scenario I’m about to describe will likely sound familiar.
A senior marketing leader walks the team through the use cases they want to ship: cross-device personalization, omnichannel orchestration, look-alike modeling, real-time triggered journeys through Adobe Journey Optimizer. Everyone nods along. The roadmap looks great on the slide.
What almost never gets asked, at least not early enough, is the harder question underneath all of it: was the brand's identity architecture ever built to support this? By treating identity as a variable worth planning for, rather than table stakes the implementation team will handle along the way, you can get more value from your Adobe Real-Time CDP investment sooner and build a roadmap that holds up at every step.
In this article, I’ll walk through a simple ladder showing how identity capability builds step by step, with separate versions for B2C and B2B. Then I’ll show you an easy way to match your use cases to the step you're actually standing on.
Identity architecture is what makes an ambitious use case roadmap actually deliver, instead of just looking good on the slide. Getting identity decisions right in the first weeks of an Adobe Real-Time CDP implementation pays off well past go-live.
Think about decisions like how you set up namespaces, structure your identity graph, and choose which data sources feed identity. If you build a deliberate stitching strategy from the start, every new customer profile you add to Real-Time CDP makes your data easier to work with, which means faster reporting, cleaner segments, and less manual cleanup as your customer base grows.
The framework that follows is a way to make identity sequencing explicit, visible to non-technical stakeholders, and defensible against the pressure to skip “rungs.” It’s informed by work across multiple enterprise Adobe implementations where we kept seeing the same pattern: use case roadmaps colliding with identity gaps that had been quietly accepted as “we’ll get to that later.”
Picture identity capability as a ladder that builds one rung at a time, with each rung depending on the one below it. A brand sitting at Rung 2 can't reliably launch a Rung 5 use case, no matter how much budget gets thrown at it, because the data that use case needs simply doesn't exist yet. Here's what that climb looks like for B2C and B2B brands, rung by rung:
B2C and B2B follow parallel structures, but they solve different problems.
The B2C ladder is about progressive deduplication. Each rung reconciles more fragmented identifiers belonging to the same person, until the brand has a unified view across sessions, devices, and channels.
The B2B ladder is about progressive entity enrichment. Each rung layers a richer business entity, account, buying group, opportunity, onto identified persons, until the brand has a unified view of the revenue motion. Let’s take a look at each in more detail.
Whether you’re a B2B or a B2C organization, if you skip a rung on the ladder, you usually end up with a use case that looks ready to ship, built on an identity foundation that isn't.
B2C brands typically try to jump from rung 2 to rung 5. They have authenticated users, email subscribers, and an Adobe Journey Optimizer license, so coordinating experiences across channels looks achievable. It's not, at least not yet. Without rung 3's anon-to-known stitching in place first, a logged-in user can't reliably connect back to their pre-login behavior, and every omnichannel journey has to start from scratch.
B2B brands hit a similar wall one rung earlier. Buying group orchestration, rung 4, looks within reach once a brand has identified persons flowing in from Marketo or a similar platform. But without rung 3's person-to-account linkage solid first, those buying groups get built on shaky ground, tying the wrong people to the wrong accounts often enough that the orchestration built on top of them loses the field team's trust fast.
Once you know where a brand sits on the ladder, every candidate use case falls into one of four quadrants. Note that this particular matrix is an example, so your own version should reflect your brand's specific use cases and priorities.
One axis is identity readiness: does the brand already have the rungs that use case needs? The other is business value: will it actually move the needle on revenue, customer experience, or efficiency?
Let’s walk through each of the quadrants in more detail:
Bias the first 90 days toward quick wins. They move to configuration fast and build the ROI evidence and stakeholder momentum that fund the harder foundation work later.
These two examples are composites drawn from real engagements, with names and figures adjusted to protect client details. Both brands came in with a use case already picked as their big year-one swing. In both cases, the ladder told a different story about where to start.
This brand, with strong ecommerce, a growing mobile app, and a large but fragmented offline channel, had marketing leadership pushing cross-device personalization as the marquee year-one deliverable.
The scorecard told a different story. Rung 3 (anon-to-known stitching) sat at roughly 40% match, meaning a cross-device graph built on top of it would connect devices to anonymous fragments about as often as to known profiles. Sequencing Rung 3 first preserved the cross-device ambition while fixing the match rate underneath it, and moved three quick wins forward in the meantime, generating the ROI evidence needed to defend the longer foundation work to executive sponsors.
With a Marketo, Salesforce, Demandbase, and Adobe Experience Platform B2B stack already in place, this brand's leadership wanted buying group orchestration as the flagship year-one deliverable.
The scorecard showed person-to-account accuracy at roughly 70% via email domain, breaking on personal email addresses, meaning buying groups built on that linkage would be wrong roughly one time in three. Fixing Rung 3 first cost less, shipped the use case sooner, and made the eventual buying group work defensible. The reordering also unlocked three quick wins in the first quarter, sales alerts, opportunity acceleration content, and customer expansion, that built credibility with the revenue organization before the harder identity work began.
No two brands' identity realities look the same. Legacy systems, channel mix, data governance, and customer base all shape what the right sequence looks like, so the ladders and matrix here are a starting point for thinking it through, not a substitute for mapping your specific landscape and sequencing investments around real business value.
Brands that come out of year one in good shape are the ones that built an identity foundation honest enough to support the use cases they eventually want to run. If you want a second set of eyes on where your own rungs stand, we'd love to talk through your Adobe Real-Time CDP roadmap.