Adobe Analytics, 2018-2026: everything that changed
If your Adobe Analytics implementation was built in 2018 and hasn't been rearchitected since, it is now three platform generations behind - not because it stopped working, but because everything around it moved. This is the timeline of what actually changed, written for teams deciding what to do about it in 2026.
2018 - the last year of the old world
Launch (later renamed Adobe Experience Platform Tags) became the anointed successor to DTM, and Adobe announced the Experience Platform vision: data in datasets, schemas over variables, one identity. Most implementations, reasonably, changed nothing.
2019-2020 - the successor products arrive
Adobe Experience Platform went GA, the AEP Web SDK (alloy.js) appeared as a single library to replace AppMeasurement, visitorAPI, and at.js - and Customer Journey Analytics launched: Analysis Workspace pointed at cross-channel AEP data instead of report suites. DTM stopped accepting new properties on its way to retirement. The writing was on the wall, in Adobe's own handwriting.
2021 - the forced move
Adobe made DTM properties read-only on 22 February 2021 and decommissioned the product on 20 April 2021; libraries already published to the CDN kept serving. Every implementation still on it had to migrate - the first time in years that measurement teams were required to touch working setups. Many took the smallest possible step (DTM to Launch, same variables, same beacons), which is precisely why so many 2026 implementations are structurally 2014 implementations running in a newer tag manager.
2022-2023 - CJA grows up, the old UI retires
CJA accumulated the capabilities that made it usable as a daily driver, and Adobe retired the legacy Reports & Analytics interface - Analysis Workspace became the only Adobe Analytics surface that matters. Meanwhile new Adobe deals increasingly led with AEP and CJA rather than traditional Analytics.
2024-2026 - maintenance mode in all but name
Adobe has not end-of-lifed Adobe Analytics, and no date exists as of this writing. But the direction stopped being ambiguous: new capability ships on the AEP side, CJA is sold as the successor, and in 2026 Adobe introduced CX Analytics, an AI-forward evolution of the CJA line. Teams on traditional Adobe Analytics are not facing a deadline; they are facing a widening capability gap and a shrinking pool of tooling attention.
What this means if you are still on the 2018 stack
Three findings from the timeline. First, nothing forces you to move today - and that is exactly why unplanned migrations happen at the worst time; the forcing events (DTM, R&A) arrived with deadlines before. Second, the migration is bigger than a library swap: Web SDK changes payloads and debugging, CJA changes the data model, identity becomes a design decision. Third, the history you preserve is only as good as the identity and context you collected - the earlier the schema is designed, the more of the past remains usable. The rational move in 2026 is a planned, reconciled migration on your own timeline. That is a scoping exercise, and it starts with an audit of what your current implementation actually collects.