Adobe Analytics

Adobe Analytics is the incumbent enterprise alternative to GA4. Its data model is hit-based and variable-slotted rather than free-form: you map meaning onto numbered custom dimensions — up to 250 eVars and 75 props per report suite, contract depending — plus custom events, and everything is processed server-side at collection time. eVars persist beyond the hit they are set on (expiring by default at the end of the visit, with last-touch allocation, both configurable), while props do not persist; that persistence model is what powers Adobe’s attribution but also what makes a solution design document non-negotiable. Every variable needs an owner and a spec, because renaming or repurposing a slot rewrites the meaning of historical data.

Its analytical strength is Analysis Workspace — drag-and-drop segmentation, calculated metrics, and attribution panels that remain more capable than most competitors’ UIs — alongside Report Builder, the Analytics 2.0 APIs, Activity Map, virtual report suites, and classifications for enriching collected values after the fact.

On implementation: Adobe’s recommended path for new customers is the Experience Platform Web SDK extension deployed through its tag manager, with manual Web SDK, the older Analytics extension, and legacy AppMeasurement.js as the other client-side routes. Server-side collection runs through the Edge Network API or the Data Insertion API, and mobile goes through the Mobile SDK extension. Teams still on AppMeasurement should treat any new work as a reason to move to the Web SDK, since that is also the collection layer Customer Journey Analytics builds on.

Raw-data access exists but takes engineering. Data Feeds deliver hit-level data in hourly or daily compressed batches to Amazon S3, Google Cloud, or Azure (legacy FTP/SFTP is deprecated), and you must reconcile raw pre/post columns — persisted eVar values live in post_ columns — before the output matches what Workspace reports. Data Warehouse covers bulk report exports.

The migration question hangs over every evaluation. Customer Journey Analytics, Adobe’s successor built on Experience Platform datasets, drops eVars, props, and events entirely in favor of schema-defined dimensions and metrics, replaces visitors/visits/hits with persons/sessions/events, moves processing from collection time to report time (making settings retroactive), and adds cross-channel identity stitching that classic Adobe Analytics does not have. Teams adopting Adobe today are really choosing that trajectory, and net-new builds should be scoped with CJA in mind.

Use it when you already sit inside an Adobe Experience Cloud contract, need Workspace-grade ad hoc segmentation, or have governance requirements that justify dedicated admin resources. Look past it when you lack enterprise budget and staffing, or when you want raw event-level ownership in your own warehouse without a multi-year contract.