Adobe Launch (AEP Tags): What Is It and How Does It Work? 2025 Guide

Adobe Launch, now officially called Adobe Experience Platform Tags (AEP Tags), is Adobe's tag management system for deploying marketing and analytics tags on websites and mobile apps. Think of it as Adobe's answer to Google Tag Manager: a visual interface where you manage tracking codes, pixels, and scripts without editing your site's source code directly.

Here's what catches most people off guard: Adobe Launch has been free since 2018. Adobe made it available at no extra cost to any Adobe Experience Cloud customer. That decision changed the tag management landscape overnight, since it removed one of GTM's biggest advantages — the price tag.

If you work with Adobe Analytics, Adobe Target, or any part of the Experience Cloud, Adobe Launch is already included in your contract. And if you're a GTM user wondering whether to switch, or a team evaluating tag management for the first time, this guide will give you a clear picture of what Adobe Launch does, how it compares to GTM, and when it makes sense to use one over the other.

What Is Adobe Launch? Understanding the Name Changes

Let's clear up the naming confusion first, because Adobe hasn't made this easy.

2018: Adobe acquires Satellite (from Search Discovery) and relaunches it as Adobe Experience Platform Launch, or just "Launch" for short. It replaces the older Dynamic Tag Manager (DTM).

2020: Adobe rebrands it to Adobe Experience Platform Data Collection, as part of a broader platform consolidation.

2023–2025: The official name is now Adobe Experience Platform Tags (AEP Tags), but almost everyone in the industry still calls it "Adobe Launch" or just "Launch."

In this guide, we'll use "Adobe Launch" because that's what people search for and what practitioners actually say in conversation. When you see "AEP Tags" in Adobe documentation, it's the same product.

Already familiar with tag management through GTM? Our guide on common GTM mistakes covers principles that apply to any TMS, including Launch.

How Adobe Launch Works: Extensions, Data Elements, and Rules

Adobe Launch organizes everything into three core building blocks. If you know GTM, these will feel familiar — but with different names.

Extensions

Every Launch property starts with the Core Extension, which provides basic triggers (page load, click, timer, custom event) and conditions (path, query string, device type). From there, you add extensions for each tool you want to deploy:

• Adobe Analytics Extension — configures your Analytics implementation with a visual interface. No need to manually set up AppMeasurement.js.
• Adobe Target Extension — deploys A/B testing and personalization.
• Adobe Experience Platform Web SDK Extension — sends data to the Edge Network for the modern AEP architecture.
• Third-party extensions — cover tools like Google Analytics, Facebook Pixel, Hotjar, and hundreds more from the extension catalog.

When Jan, a marketing technologist at a Polish e-commerce company, switched from GTM to Adobe Launch in February 2025, the extensions model was what sold him. "In GTM, setting up Adobe Analytics required a custom HTML tag with 40 lines of JavaScript," he explained. "In Launch, I installed the Adobe Analytics extension, filled in my report suite ID, and had basic tracking running in 15 minutes. The extension handles all the library loading, variable mapping, and link tracking automatically."

Data Elements

Common data element types:

• JavaScript Variable — grabs a value from your data layer or any JS object (like digitalData.page.pageName)
• DOM Attribute — reads values directly from HTML elements
• Cookie — reads browser cookie values
• Local Storage — reads from the browser's local storage
• Custom Code — runs JavaScript to compute a value on the fly

Data Elements have one key advantage over GTM Variables: built-in persistence. You can configure a Data Element to retain its value for the page view, session, or visitor lifetime. In GTM, you'd need to write custom code or use cookies to achieve the same thing.

Rules

A Rule has three parts:

1. Events (when should this fire?) — equivalent to GTM Triggers. Examples: page load, click, custom event, timer.
2. Conditions (should it fire now?) — let you add if/then logic. Examples: only on specific URL paths, only if a data element has a value, only on mobile devices.
3. Actions (what should happen?) — equivalent to GTM Tags. Examples: send a beacon to Adobe Analytics, fire a Facebook pixel, set a cookie, run custom code.

One Rule can have multiple Events, multiple Conditions, and multiple Actions. This is more flexible than GTM, where each Tag gets one Trigger (though you can use Trigger Groups for complex logic).

Want to see how tag management principles apply across platforms? Understanding how GA4 collects event data helps you make better implementation decisions in any TMS.

Adobe Launch vs Google Tag Manager: Honest Comparison

This is the comparison everyone wants. Here's where each tool genuinely excels.

When GTM Is the Better Choice

You're a Google-stack shop. If your analytics is GA4, your ads are Google Ads, and your CMS is WordPress, GTM is the natural fit. Native integrations work seamlessly, and you'll find a YouTube tutorial for every use case imaginable.

Budget is zero. GTM is truly free, no strings attached. Adobe Launch is "free" but only if you're already paying for Adobe Experience Cloud, which starts at significant five-figure contracts.

Your team knows GTM. The GTM talent pool is 10x larger than the Launch talent pool. Finding someone who can manage your GTM container is easy. Finding a Launch specialist might require a recruitment effort.

You need community support. Stuck on a GTM problem at 2 AM? Stack Overflow, Simo Ahava's blog, and dozens of Slack communities have your answer. Launch questions often go unanswered outside of Adobe's official forums.

When Adobe Launch Is the Better Choice

You're an Adobe-stack shop. If you run Adobe Analytics, Adobe Target, and AEM, Launch is dramatically easier to implement and maintain. The native extensions eliminate hundreds of lines of custom code.

You need robust publishing workflows. Launch's environment system (Development, Staging, Production) with approval workflows is genuinely superior to GTM's simpler publish model. For enterprise teams with QA requirements, this matters.

You need built-in persistence for variables. Data Element persistence across sessions and visitors is built-in. In GTM, you'd need cookies or custom code.

You're deploying to mobile apps. The Adobe Experience Platform Mobile SDK integrates natively with Launch. While GTM works with Firebase, the Adobe SDK + Launch combination is more tightly integrated for Adobe product use cases.

Sofia, a senior analytics engineer at a multinational retailer, managed both GTM and Launch across different brand websites. "GTM is faster to set up and easier to hire for," she said. "But for our Adobe Analytics implementations, Launch saves us probably 20 hours per month in maintenance. The extensions handle library updates, variable mapping, and link tracking automatically. In GTM, every Adobe Analytics update meant manual custom code changes."

The Publishing Workflow: Development, Staging, Production

One area where Adobe Launch genuinely outshines GTM is its publishing workflow. Here's how it works.

Libraries and Environments

In GTM, you have one container and one "Submit" + "Publish" flow. Whatever you publish goes live immediately.

In Adobe Launch, you work with Libraries (bundles of changes) that move through Environments:

1. Development. You build and test changes here. You can have multiple development environments for different team members working simultaneously.
2. Staging. Once development is done, you promote the library to staging for QA review. This environment runs the exact production code on a test site.
3. Production. After QA approval, you promote to production. The changes go live.

Each environment has its own embed code. Your development site loads the development library, your staging site loads the staging library, and your production site loads the production library. This means you can test changes on a real site without affecting live users.

Why This Matters

For a small website managed by one person, GTM's simple publish flow is perfect. But for enterprise teams where a bad tag deployment can cost thousands in lost revenue or break consent compliance, Launch's environment system provides a safety net that GTM doesn't offer out of the box.

Setting Up Adobe Launch: What to Expect

Prerequisites

Before you start, you need:

• An Adobe Experience Cloud contract (Launch is included)
• Access to Adobe Admin Console to assign user permissions
• A data layer implemented on your website (recommended but not required)
• The Adobe Experience Platform Debugger browser extension for testing

Step-by-Step Setup

Step 1: Create a Property. In the Launch UI, create a new property for your website. Give it a name, select "Web" as the platform, and enter your domain.

Step 2: Install Extensions. Add the extensions you need. At minimum, you'll want the Core extension (included by default) and the Adobe Analytics extension (if using Analytics).

Step 3: Create Data Elements. Map your data layer variables to Launch Data Elements. For example, create a "Page Name" data element that reads from digitalData.page.pageName.

Step 4: Build Rules. Create rules that fire tags based on events and conditions. A basic page load rule might have: Event = "Library Loaded (Page Top)", Condition = none, Action = "Send Beacon" (Adobe Analytics).

Step 5: Build a Library. Add your new resources (extensions, data elements, rules) to a Development library and build it.

Step 6: Install the Embed Code. Copy the Development embed code from Launch and add it to your site's <head>. This is a single <script> tag, similar to GTM's container snippet.

Step 7: Test. Use the Adobe Experience Platform Debugger to verify tags are firing correctly and data is flowing to Adobe Analytics.

Step 8: Promote to Production. Once testing is complete, promote through Staging and then to Production.

The entire process takes 1–3 days for a basic implementation, compared to a few hours for a basic GTM setup. The extra time comes from the more structured workflow, not from added complexity.

Common Adobe Launch Mistakes to Avoid

Mistake 1: Treating Launch Like GTM

The biggest mistake GTM users make when switching to Launch is trying to replicate their GTM setup 1:1. Launch has different strengths. Use extensions instead of custom HTML. Use Data Element persistence instead of cookie-based workarounds. Use the environment workflow instead of fighting it.

Mistake 2: Ignoring the Extension Catalog

Writing custom code for something an extension already handles is a waste of time and creates maintenance debt. Before writing custom JavaScript, check the extension catalog. There are extensions for consent management, data layer validation, A/B testing platforms, and most major marketing tools.

Mistake 3: Skipping the Data Layer

Launch can scrape values directly from the DOM, but this creates brittle implementations that break whenever the site design changes. Invest in a proper data layer. Launch's Data Elements work best when they read from a structured data object, not from CSS selectors.

Mistake 4: Not Using Environments Properly

Some teams deploy everything directly to Production, bypassing Staging entirely. This defeats the purpose of Launch's best feature. Set up the three-environment flow and use it consistently.

These mistakes aren't unique to Launch. Many of the same principles apply when working with GTM. See our guide on 5 GTM mistakes costing you conversions for the Google side of the same coin.

FAQ: Frequently Asked Questions About Adobe Launch

Is Adobe Launch free?

Adobe Launch (AEP Tags) is included at no additional cost with any Adobe Experience Cloud license. However, you need an active Experience Cloud contract to access it. If you don't use any Adobe products, you can't use Launch as a standalone free tool — which is different from GTM, which is free for anyone.

Can I use Adobe Launch with Google Analytics?

Yes. There's a Google Analytics 4 extension available in the Launch extension catalog. You can deploy GA4 tags through Launch just like you would through GTM. Many organizations that use Adobe Analytics as their primary tool also deploy GA4 through Launch for secondary reporting or Google Ads integration.

Is Adobe Launch replacing Dynamic Tag Manager (DTM)?

DTM was officially sunset in 2021. Adobe Launch (now AEP Tags) is its successor. If you're still running DTM, you need to migrate. Adobe provides migration tools and documentation, but the architectures are different enough that it's essentially a rebuild.

How long does it take to learn Adobe Launch?

For someone already proficient in GTM, the core concepts transfer quickly. Expect 2–4 weeks to become comfortable with the Launch interface, extension model, and publishing workflow. The underlying logic of tag management (triggers, variables, tags) is the same across both platforms.

Can I run Adobe Launch and GTM on the same site?

Technically yes, but it's not recommended for production. Running two tag management systems creates performance overhead, potential conflicts, and maintenance complexity. If you're migrating from GTM to Launch, run both temporarily during the transition period, then remove GTM once Launch is handling everything.

What's the difference between Adobe Launch and Adobe Experience Platform Event Forwarding?

Adobe Launch runs client-side (in the browser). Event Forwarding runs server-side (on Adobe's Edge Network). Event Forwarding is Adobe's equivalent of GTM Server-Side. It receives data from the Web SDK and forwards it to third-party endpoints without sending additional client-side requests. This improves page performance and data control. Event Forwarding is a separate product with its own pricing.

Conclusion: Should You Use Adobe Launch?

Adobe Launch is a mature, capable tag management system that excels in Adobe-centric environments. Its extension model, data element persistence, and enterprise publishing workflow make it the right choice for organizations deeply invested in the Adobe ecosystem.

For everyone else, GTM remains the more practical option. It's truly free, has a massive community, and integrates natively with the Google stack that most businesses rely on.

Here's the decision simplified:

1. Adobe Analytics + Adobe Target? Use Adobe Launch
2. GA4 + Google Ads? Use GTM
3. Mixed stack? Use whichever TMS matches your primary analytics platform
4. Starting fresh, no preference? Start with GTM (easier to hire for, more community resources)

The tag management system itself is rarely the bottleneck. What matters is having a clean data layer, well-structured rules, and a team that understands what they're tracking and why.

Need help with tag management implementation or migration? Whether you're setting up GTM, migrating to Launch, or troubleshooting tag conflicts, let's talk about your tracking setup.