Adobe Dynamic Tag Management (DTM) no longer exists. Adobe shut it down in April 2021 and replaced it with Adobe Experience Platform Launch, which it renamed Adobe Tags a few months later. If you see assets.adobedtm.com in your network requests today, it is almost always Adobe Tags, not DTM: the domain outlived the product as the CDN that serves Adobe’s tag libraries.
That leaves three practical questions. What was DTM, what is that domain doing on your site, and is anything on your pages still running the old library? This post answers them in that order, then covers the move to Tags and the _satellite object both products share.
What Adobe DTM was
DTM was Adobe’s tag management system. Like Google Tag Manager, it let teams load Adobe Analytics, Target and third-party tags from one container, with rules that decided when each tag fired and data elements that read values from the page. Marketing could change a tag without waiting for a code release, which was the whole point.
“Dynamic tag management” is also the generic name for that idea: one script on the page, and a server-side interface where you decide which tags load, when, and with which values. Adobe used the phrase as a product name, so searches for it mix the category with the retired product.
DTM’s JavaScript object, _satellite, is still around. Adobe Tags kept the name, which is one reason the two get confused.
From DTM to Launch to Tags
| When | What happened |
|---|---|
| July 9, 2019 | No new DTM properties could be created (Adobe, DTM sunset plan) |
| February 22, 2021 | DTM became read-only: no more changes or publishing (Adobe, milestone 2) |
| April 20, 2021 | The DTM interface and servers were shut down; libraries already published stayed on the CDN |
| July 28, 2021 | Launch was renamed: the client-side part became Tags, the server-side part Event forwarding, inside the Data Collection interface (Adobe release notes, July 2021) |
Adobe announced the plan in October 2018 and moved the last two dates during the countdown. Its sunset post is explicit about what happened to published files: DTM libraries already on the CDN “will remain available at their current location”, and pages that reference them keep working. They just can’t be edited.
So “Adobe Launch”, “Experience Platform Launch” and “Adobe Tags” are the same product at different moments, and DTM is its predecessor. Adobe Experience Manager followed the same path: its 6.5 release notes list the DTM integration as deprecated and say to switch to Launch (Adobe’s Experience League).
What adobedtm.com is
assets.adobedtm.com is the domain of the files Adobe hosts for you on Akamai, its CDN. Adobe’s own documentation says that files hosted on Akamai “have a domain of assets.adobedtm.com” (Adobe-managed hosts). DTM used it, Launch kept it, and Tags still uses it unless you self-host the library.
So a request to it means the site loads an Adobe tag library. It is not malware, and it is not, by itself, a tracker: it is the container. What it then loads and sends depends on the rules inside it. Some browsers and blockers block the domain for privacy reasons, which Adobe lists as one reason to self-host the library.
How to tell if a site still loads DTM
The domain doesn’t tell you, and neither does _satellite: both exist with DTM and with Tags. The file name does.
DTM: //assets.adobedtm.com/<id>/satelliteLib-<hash>.js
Adobe Tags: //assets.adobedtm.com/<id>/<id>/launch-<hash>.min.js
Three ways to check:
- Network panel. Open your browser’s developer tools, filter requests by
adobedtmand reload. AsatelliteLibfile is DTM; alaunch-file is Tags. - Page source. Search the HTML for
satelliteLib. Old embed codes sit in templates nobody has opened in years: a checkout, a microsite, a CMS layout. - Every template, not one page. A site can load Tags on the home page and DTM on a forgotten section. Crawl the site or sample one URL per template.
If you self-host, the domain changes to yours but the file names stay the same, so the same check works.
A satelliteLib file is a DTM leftover. It may still load and still fire tags, but DTM has not been editable since February 2021: whatever that file does, nobody on your team can change it. If it sends data, that data follows the rules of 2021, with the consent logic of 2021.
The _satellite object, then and now
_satellite is the global object the library puts on the page. In Tags, Adobe documents a short list of supported entry points (Adobe’s Experience League):
| Method | What it does |
|---|---|
_satellite.track('id') | Triggers a direct call rule with that identifier |
_satellite.getVar() / setVar() | Read a data element, or set a temporary value for the page |
_satellite.setDebug(true) | Turns on debugging in the console |
_satellite.logger | Writes to the console, only when debugging is on |
Two details matter for old code. notify(), common in DTM-era scripts, is deprecated in favor of _satellite.logger. And Adobe now calls _satellite.track() a “legacy implementation method”: still supported, with the Adobe Client Data Layer recommended for new work (Adobe’s track() reference).
Adobe also asks you to guard every call from site code, so the page doesn’t break when the library is missing or blocked:
if (window._satellite?.track) {
_satellite.track('example');
}
Moving from DTM to Adobe Tags
With DTM switched off, there is nothing left to upgrade in place. The work is a rebuild:
- Inventory what the old file sends. You can’t open DTM’s interface any more, so list the hits the
satelliteLibfile produces on each template: page views, custom links, eVars, props and events. - Rebuild in Tags. Create the property in the Data Collection interface, add the Adobe Analytics extension, and recreate data elements and rules. Adobe Tags in practice covers rules, data elements, extensions and publishing.
- Swap the embed code. Replace the
satelliteLibreference with the Tags embed code on every template, and remove the old one in the same release. - Compare the hits, not the configuration. Run the same journeys before and after and diff what reaches Adobe.
What to compare:
- Same events on the same pages. Every page view and every custom link that DTM sent should still arrive from Tags.
- Same variables with the same values. eVars, props and events populated as before, with the same formats. A data element that used to read the page and now reads the dataLayer can change a value without anyone noticing.
- No duplicates. Running both containers during the switch is the classic way to count every page view twice.
- Consent still respected. Rules rebuilt in Tags must keep the consent conditions DTM had, or better ones.
Checking this by hand means replaying journeys in a debugger before and after. Trackingplan reads the hits your real visitors send to Adobe Analytics and the rest of your stack, learns what normal looks like, and flags missing events, broken triggers and regressions between releases, with links to the affected hits. A migration is one big release, which makes it the moment to watch them most closely.
FAQ
Does Adobe DTM still exist?
No. DTM became read-only on February 22, 2021 and its interface was shut down on April 20, 2021. Its replacement is Adobe Tags, formerly Adobe Experience Platform Launch.
Why is my browser calling assets.adobedtm.com?
Because the site you are on loads its Adobe tag library from Adobe’s CDN. The domain belongs to Adobe, and today it serves Adobe Tags libraries. Only a file named satelliteLib points to DTM.
Is Adobe Launch the same as Adobe Tags?
Yes. Adobe renamed Experience Platform Launch on July 28, 2021: the client-side product is now Tags, the server-side one is Event forwarding, and both live in the Data Collection interface.
What is dynamic tag management?
It is the generic name for a tag management system: one container on the page that loads analytics and marketing tags according to rules, so they change without editing the site’s code. Adobe Dynamic Tag Management was Adobe’s product of that kind until 2021.
Do I need to migrate off Adobe DTM?
If a page still references a satelliteLib file, yes. That library may still run, but nobody can edit it, so whatever it sends is frozen as it was in 2021. Rebuild the rules in Adobe Tags and compare the hits before and after.