Adobe Analytics to CJA field mapping
Migrating from Adobe Analytics to Customer Journey Analytics is a mapping exercise: every report suite, variable, event, and segment must find its expression in AEP datasets, XDM schema fields, data views, and segments - and a few Adobe Analytics concepts have no CJA equivalent at all.
The core map
| Adobe Analytics | Customer Journey Analytics |
|---|---|
| Report suite | Dataset(s) joined in a connection |
| eVar / prop | Schema field, surfaced as a data-view dimension |
| Success event | Schema field or derived metric in a data view |
| Expiration / allocation settings | Persistence and attribution set in the data view, retroactively |
| Segments | Segments (called filters in CJA until April 2025) |
| Calculated metrics | Calculated metrics (largely portable concepts) |
| Virtual report suites | Data views |
| Marketing channels processing rules | Derived fields |
| Visitor ID / ECID | Person ID chosen per connection (identity stitching) |
What has no equivalent
Hit-level processing rules that mutate data at collection have no direct CJA counterpart - their logic moves to data prep at ingestion or to derived fields at query time. Some Adobe Analytics permanences also disappear in a good way: nothing in CJA is locked at collection the way an eVar's expiration was.
The honest step everyone skips
Parallel reconciliation. Run both systems on the same traffic and force the key reports to agree within a stated tolerance before decommissioning anything. Every mapping above can be executed correctly and still produce different numbers - date handling, bot filtering, and identity choices all differ by default. The migration is finished when the deltas are explained, not when the fields are mapped.
Frequently asked questions
Can historical Adobe Analytics data be imported into CJA?
Yes - the Analytics source connector can bring existing report-suite data into AEP datasets, preserving history. What it cannot do is retroactively add identity or context that was never collected, which is why migrations quote "history preserved" with an asterisk about cross-channel stitching on old data.