Report Suites Are Gone: Rewiring Your Brain to CJA
If you spent the last decade living in Adobe Analytics, the move to Customer Journey Analytics plays a little trick on you. At first it feels like coming home. The Workspace looks the same, you drag dimensions and metrics onto a freeform table exactly like you always did, the segments and calculated metrics and visualizations are all sitting where you'd expect them.
And then, maybe twenty minutes in, something behaves in a way your muscle memory swears is wrong, and it dawns on you that the furniture is familiar but somebody rebuilt the whole house around it.
I've sat with a lot of experienced Adobe Analytics folks while they go through this, and here's the thing I've noticed: the ones who struggle aren't struggling with the tool. They know how to build a fallout in their sleep. What's tripping them up is a handful of assumptions they've carried for years that quietly stopped being true.
So I don't want to write you a feature comparison. I want to try to knock loose the two or three mental models that cause the most grief.
The Report Suite Was Everything
In Adobe Analytics, the report suite was everything. Your data flowed in through a tag, got chewed on according to that report suite's settings — its variables, its time zone, its processing rules — and then lived inside those walls forever. The report suite was both the box your data sat in and the rulebook for how that data behaved.
CJA pulls them apart, and honestly, getting your head around that split is most of the work. The cleanest way I've found to hold it is three pieces:
- Your data lives in AEP, not in CJA. CJA doesn't collect a single thing — it's an analysis layer sitting on top of data that already lives in Adobe Experience Platform. The collecting and the analyzing, which used to be one conversation, are now two different rooms.
- A Connection is your new “container.” You decide which AEP datasets to pull together — web, mobile, call center, CRM, whatever you've got — and that becomes your universe. Unlike a report suite, it was never limited to your website.
- A Data View holds the behavior. Everything you used to bake into report suite settings — attribution, time zone, how metrics calculate, which fields even show up — now lives here.
The part I always make sure people really hear is that you can hang many Data Views off a single Connection. In the old world, when two teams wanted the same data with different rules, you ended up cloning report suites and then spending the rest of your life reconciling why their numbers didn't match.
Now one Connection feeds several Data Views, each tuned for a different team, all drawing from the same underlying data. Pulling the rulebook apart from the data box sounds like plumbing, but it's genuinely one of the best things about the platform once it lands.
From Visits to People
The second rewire is quieter and, I think, deeper. Adobe Analytics was built around the visit. The whole model — hits rolling into visits rolling into visitors — was session-shaped, because it grew up in an era where “analytics” basically meant “the website.”
CJA is built around the person. The default thing you're analyzing is a human being stitched together across channels and across time, not a browser session that forgets everything the moment someone switches devices.
That sounds like a vocabulary tweak. It is not. It's a different way of thinking, and it changes what questions feel natural. Something that was a genuine pain in Adobe Analytics — “what did this specific customer actually do across web, the app, and the call center over the past two months?” — is just a normal Tuesday in CJA.
The identity that makes that possible comes out of AEP's identity resolution, built on your own identifiers like a User ID or an authenticated login, not a cookie that resets every time someone clears their browser. Which is also why the Person ID quietly becomes one of the most important decisions you'll make, because it's what determines whether those events actually stitch into one continuous story or fall apart into fragments.
The rewireIf you keep thinking in visits, you'll use this tool at maybe half its worth. The day you start asking person-level, cross-channel questions is the day it starts paying you back.
The Smaller Habits That Break
There are also a few smaller habits that just break, and it's kinder to warn you now than let you discover them mid-analysis:
- eVars and props are gone. Those were report-suite constructs. In CJA everything is simply a field in your XDM schema, defined by your data model rather than a numbered slot — and after the initial disorientation, it's freeing to stop hunting for “eVar14.”
- Processing rules and vars aren't where you fix things anymore. Most of that shaping now happens either upstream in AEP or in CJA's Derived Fields, which are worth learning early because they're more capable than the old tools.
- Real-time is no longer the expectation. Adobe Analytics spoiled all of us with near-instant data. CJA is mostly batch, so numbers usually land a few hours later. Fine for journey work — but if you walk in expecting live dashboards you'll be annoyed for entirely the wrong reason.
The reassuring part
Your analytical craft still transfers.
Everything you actually learned about analysis still holds. Segmentation logic, reading a fallout, building a metric that isn't lying to you, telling a story with a freeform table — all of that craft transfers untouched.
What changed is the ground underneath it: where the data lives, what defines its behavior, and what you're fundamentally counting. So the switch to CJA was never really about relearning Workspace. It's about letting go of the report suite as the center of gravity in your head and replacing it with something cleaner — data in AEP, behavior in Data Views, people as the unit of analysis.
Give it a few weeks and the old model starts to feel cramped. You won't miss eVar14. I promise.