Adobe Experience Platform Tags

Tags — still called Launch by most practitioners — models deployment as rules: an event, optional conditions and exceptions combined with if/then logic, and actions that execute in the order you set. Data elements abstract your data layer behind named references, and extensions package vendor integrations as bundles of JavaScript, HTML, and CSS, with the Adobe set (Analytics, Target, the Experience Platform Web SDK) as first-class citizens. Builds are genuinely modular: if a resource is not used, it is not compiled into your library, and the runtime avoids document.write() so most code loads asynchronously.

The publishing workflow is the enterprise differentiator. Every property gets development, staging, and production environments at creation (you can add more development environments), and changes move through libraries with distinct Develop, Approve, and Publish permission rights, so submitting a change and approving it can be separated by role. Libraries in flight inherit upstream resources as a baseline, which keeps parallel workstreams from clobbering each other. Everything is scriptable through the Reactor API for CI-style automation.

Implementation notes worth knowing before you commit. Hosting is either Managed by Adobe — builds delivered to Adobe’s contracted CDN (currently Akamai) under assets.adobedtm.com — or your own SFTP server; an archive option also packages builds as a zip for manual deployment or code review. Adobe’s own docs note that some browsers block the assets.adobedtm.com domain under strict privacy settings, which is a concrete argument for self-hosting the library on your own domain. And each environment has its own embed code: change the host or the archive setting and the embed code regenerates, forcing a manual update in your site’s HTML.

Server-side needs route to Event Forwarding, which is a separately purchased capability, not a free add-on — it is bundled with Real-Time CDP Connections, Prime, or Ultimate. It lives in separate properties in the same UI, requires the Experience Platform Web or Mobile SDK feeding the Edge Network, and has its own dialect: {{name}} tokens instead of the %name% syntax client-side Tags uses, sequential rule actions, and a 30-second processing budget per event. Budget migration time if your team assumes GTM-server-style parity.

Outside the Adobe ecosystem the calculus changes. The extension catalog is thinner than GTM’s community gallery, third-party vendor support arrives later, and the practitioner hiring pool is smaller. Use it when you run Adobe Analytics, Target, or the AEP Web SDK and want a governed release process for tags with self-hosted delivery as an option. Look past it when you are not an Adobe shop — you would be adopting an enterprise workflow without the ecosystem that justifies it.