GTM vs Adobe Launch: Which to Pick and How to Migrate

Olamide Sule, founder of Dolphin Analytics: a digital analytics expert based in London delivering solutions for agency and in-house clients.

We set up and fix Google Tag Manager for agency and in-house teams most weeks, and teams on the Adobe stack ask us the same thing before any rebuild: should we stay on Adobe Launch, or move to GTM? This is the side-by-side we walk them through, with the costs, the concept mapping and the migration order that keeps data flowing while you switch.

What are GTM and Adobe Launch?

Google Tag Manager and Adobe Launch are both tag management systems: one container snippet on your site loads and controls every analytics and marketing tag. GTM is Google’s free tool. Adobe Launch is Adobe’s equivalent, now renamed Adobe Tags. It sits inside Adobe Experience Platform Data Collection and comes bundled with Adobe Experience Cloud.

If “tag”, “trigger” and “container” are new terms, start with our plain-English guide to tag management systems, then come back here.

What happened to Adobe DTM? Adobe Dynamic Tag Management (DTM) was the tag manager before Launch. Adobe retired it, and its old documentation now redirects to the Adobe Tags docs. A site still loading a DTM library is running unsupported code, so the question isn’t whether to change, only what to change to.

How do GTM and Adobe Launch compare side by side?

GTM wins on cost, ecosystem and how easy it is to hire for. Adobe Tags wins on built-in publishing approvals and on fit with Adobe Analytics, Target and the Adobe Web SDK. Both can fire any vendor’s tags, so the choice follows your analytics platform more than the tag manager itself.

	Google Tag Manager	Adobe Launch (Adobe Tags)
Cost	Free; paid Tag Manager 360 tier	Included with Adobe Experience Cloud
Building blocks	Tags, triggers, variables	Rules (events, conditions, actions), data elements, extensions
Publishing	Workspaces, versions, one-click publish	Libraries moved through development, staging and production
Approvals	Built into Tag Manager 360	Separate Develop, Approve and Publish rights
Server-side	Server container on Google Cloud Run or your own hosting	Event forwarding, a paid add-on needing the Web SDK
Data layer	dataLayer array	Adobe Client Data Layer or a custom object
Ecosystem	Templates for most ad and analytics vendors	Extension catalogue, strongest for Adobe products
Hiring	GTM skills are common	Adobe Tags skills are rarer

How do the building blocks map from Adobe Launch to GTM?

Every Adobe Tags concept has a GTM equivalent, but the grouping differs. An Adobe rule bundles the “when” and the “what” together; GTM splits them into a trigger and a tag, so one Adobe rule often becomes one trigger plus several tags.

Adobe Tags	GTM equivalent	Note
Property	Container	One per site or app
Rule event	Trigger	Page load, click, custom event
Rule condition	Trigger filter or exception	”Some events” conditions in GTM
Rule action	Tag	One tag per action
Data element	Variable	Data Layer Variable for most
Extension	Tag template	Community Template Gallery
_satellite.track() direct call	dataLayer.push({event: ...})	Needs a site code change
Library and environments	Workspace, version and GTM environments

The _satellite.track() row is the one that catches teams out. Direct call rules live in the site’s own code, not in Adobe Tags, so a migration touches the website as well as the tag manager.

Which tag manager handles governance better?

Adobe Tags has stricter governance out of the box. Its publishing flow moves each library from Development to Submitted, Approved and Published, and Develop, Approve and Publish are separate user rights, so one person can’t push an untested change live unless an admin grants all three.

The free version of GTM is looser. Anyone with Publish permission can ship a change, and Google’s workspace documentation caps the standard product at 3 concurrent workspaces, while Tag Manager 360 allows unlimited workspaces and adds approval workflows. For a small team that’s fine. For a large organisation with several agencies in one container, the gap is real, and it’s a reason Adobe Tags survives in regulated businesses.

In our experience the governance gap matters less than who owns the container. A GTM container with one named owner and a change log stays cleaner than an Adobe property where approval has become a rubber stamp.

What about server-side tracking?

Both tools support server-side tracking, but the cost model differs. GTM’s server-side tagging runs a server container in your own Google Cloud project or another environment you choose, so you pay hosting, not a licence.

Adobe’s equivalent is event forwarding, which sends data from the Adobe Edge Network to other endpoints. It requires the Adobe Web SDK and is a paid feature included only in certain Real-Time CDP packages. If server-side tracking is part of the reason you’re weighing a switch, our server-side tracking guide covers the GTM route in detail.

Which should you pick: GTM or Adobe Launch?

Pick the tag manager that matches your analytics platform. Tag management is rarely the expensive decision; the analytics contract is. If you’re still choosing between the platforms themselves, read our GA4 vs Adobe Analytics comparison first.

Your situation	Pick
GA4 and Google Ads are your main tools	GTM
Adobe Analytics, Target or Customer Journey Analytics run the stack	Adobe Tags
Leaving Adobe Analytics for GA4	GTM, migrated in the same project
Still loading an old DTM library	Rebuild now, on whichever matches your analytics
Several agencies editing one container, strict sign-off rules	Adobe Tags, or Tag Manager 360
Agency managing tags across many clients	GTM
You need a customer data platform, not a tag manager	Neither; see GTM vs Segment

Running both tools on one site for the long term is the option we’d steer you away from. Two containers means two places to check when a number looks wrong.

How do you migrate from Adobe Launch to GTM?

Migrating from Adobe Launch to GTM is a rebuild: there is no import tool, so you inventory what Adobe Tags does, recreate it in GTM, run both in parallel, then cut over. The steps below are the order we’d follow.

1. Inventory the Adobe property. In Adobe Tags, open your property and go to Rules, then Data Elements, then Extensions. Record every rule’s events, conditions and actions. On large properties, the Reactor API returns rules and data elements as JSON, which is faster than clicking through.

2. Decide what not to move. Drop rules for vendors you no longer pay, and decide whether Adobe Analytics itself is staying. If it is, note that GTM has no Google-built Adobe Analytics tag, so Adobe’s library loads through a Custom HTML tag or a Community Template Gallery template. You lose the Adobe Analytics extension’s interface on that route, so write clear documentation of the setup for whoever maintains it next.

3. Bridge the data layer. If the site uses the Adobe Client Data Layer, keep it and forward its events into GTM’s dataLayer with a script that loads before the GTM container:

   <script>
     window.dataLayer = window.dataLayer || [];
     window.adobeDataLayer = window.adobeDataLayer || [];
     window.adobeDataLayer.push(function (dl) {
       dl.addEventListener("adobeDataLayer:event", function (event) {
         window.dataLayer.push(event);
       });
       dl.addEventListener("adobeDataLayer:change", function (change) {
         if (!change.event) {
           window.dataLayer.push(change);
         }
       });
     });
   </script>

   The first listener forwards named events. The second forwards data-only pushes such as adobeDataLayer.push({ page: {...} }), which the Adobe Client Data Layer reports as a change, not an event. Skip it and the variables you build in step 4 can come back undefined.

   Then replace every _satellite.track("name") call in the site code with window.dataLayer.push({ event: "name" }).

4. Recreate data elements as variables. In GTM, go to Variables > User-Defined Variables > New > Data Layer Variable and enter the same key path the Adobe data element read, for example page.pageInfo.pageName.

5. Recreate rules as triggers and tags. Go to Triggers > New > Custom Event and set Event name to the event the rule listened for. Then go to Tags > New, choose the tag type (for example Google Analytics: GA4 Event) and attach that trigger. Repeat for each action in the rule.

6. Run both in parallel. Publish the GTM container, then check each event in Preview and in the destination tool’s own debug view. Make sure each vendor fires from only one tool: if Adobe Tags and GTM both send the same purchase to GA4 or Meta, every sale counts twice.

7. Cut over. Once the numbers match, remove the Adobe Tags embed code from the page <head>, confirm the GTM snippet is in place, and publish a named container version so you can roll back.

Our GTM setup guide covers the container setup around steps 4 and 5 if you’re starting from an empty account.

What breaks when you migrate from Adobe Launch to GTM?

Three faults show up in migrations more than any others, and none of them announce themselves.

• Double counting during the parallel run. A vendor tag left live in Adobe Tags while its replacement fires from GTM inflates conversions until someone compares totals.
• Missed direct call rules. A _satellite.track() call nobody replaced stops sending its event the day the Adobe embed code comes out.
• Consent wiring. Adobe Tags rules often check a consent condition inside the rule. GTM needs consent mode or trigger conditions set up again from scratch, or tags fire before a visitor agrees.

The fault we watch hardest for is the first. Double counting looks like good news in a report, so nobody questions it.

How we handle a move to GTM

A tag manager migration is tracking work, and tracking work is what we do. We rebuild GTM setups for agency and in-house clients, map the data layer, and check every event against the destination tool before the old container comes out. For Illumicrate, we rebuilt the tracking across its UK and US stores, including waitlist tracking. See how we approach tracking or our Google Tag Manager consultant page for how that work runs.

Not sure what your site loads right now? Sonar, our free external scanner, shows the tags, pixels and consent setup it can prove from outside, in one click at Sonar, with no account access. If you’re planning a move off Adobe Tags and want a person’s view first, tell us what’s broken, or book a call.