Running AEP or CJA across multiple brands: what agencies get wrong
One Adobe Experience Platform instance, several client brands, one team. It works, but only if you get schema and governance right before anyone starts building.
Sam Daniel
Founder, Aanya Ari Consulting · June 2026
Agencies managing multiple client brands increasingly want one Adobe Experience Platform setup to serve all of them, instead of standing up a separate instance per client. It's a reasonable instinct: shared infrastructure, shared expertise, lower overhead. It's also where most of the governance mistakes we see actually start.
The core tension
AEP rewards a unified schema: one clear model for who a profile is and what an event means. Multi-brand agency work rewards isolation: client A's data should never leak into client B's segments, reporting, or activation. Those two goals pull in opposite directions, and most of the problems we see come from resolving that tension too late — after brands are already live on the platform.
Where it breaks in practice
- —Shared XDM schemas built for one client's business get reused for the next client without adjustment, and the field structure quietly stops matching that client's actual data model.
- —Identity stitching rules that make sense in isolation start merging profiles across brands when a shared field (like a common email domain) is present in more than one client's data.
- —Access permissions default to platform-wide instead of sandbox- or brand-scoped, so a segment built for one client is visible, and editable, by someone working on another.
- —Governance decisions get made by whoever onboarded the first client, and never get revisited as brand two, three, and four are added.
What to set up before the second brand goes live
Decide sandbox strategy first: separate sandboxes per client brand where compliance or competitive separation requires it, shared sandboxes with strict access controls where it doesn't. Document identity resolution rules explicitly, in writing, before the second brand's data starts flowing — not after profiles have already started merging incorrectly. And assign schema ownership: one person who reviews and approves any schema change across all brands, so brand-specific fields don't quietly become platform-wide assumptions.
The AI governance layer
As agencies start layering AI-driven segmentation and personalization on top of AEP and CJA, this governance problem gets sharper, not smaller. An AI model trained on cross-brand data, even accidentally, can produce recommendations or segments that violate a client's data agreement without anyone realizing it happened. The fix isn't slowing down AI adoption. It's making sure the underlying platform governance is solid before you add a layer that can amplify a governance mistake at scale.
If your agency is standing up AEP or CJA across multiple client brands and wants a second set of eyes on governance before the second brand goes live, that's exactly the kind of engagement we do. Better to catch this in week two than after profiles have already merged.
Frequently asked
Should each client brand get its own AEP sandbox?
It depends on compliance requirements and how competitively sensitive the data is. When in doubt, default to separate sandboxes; consolidating later is easier than untangling merged data.
What's the biggest governance risk in a multi-brand AEP setup?
Identity stitching rules that unintentionally merge profiles across brands, usually through a shared field like an email domain that wasn't scoped to a single client.
How does AI complicate multi-brand governance?
AI-driven segmentation can act on cross-brand data even when a human wouldn't, because the model doesn't know the client boundary was supposed to be there. Solid platform governance has to exist before AI is layered on top.
Related service
Adobe Experience Platform
Work with us
Ready to put this into practice?
We work with enterprise, agency, and growing teams on AI strategy, MarTech implementation, and the messy gap between the two.
Get in touch