Adobe Environment Switcher

The Adobe Environment Switcher lets you redirect Adobe Launch/Tags library requests between development, acceptance, and production environments without changing any code on the page.

How it works

TagDragon uses Chrome’s declarativeNetRequest API to perform network-level URL redirection. When you select an environment, TagDragon creates a redirect rule that intercepts matching script requests and rewrites the URL to point to the selected environment’s build.

This happens at the network level — the page doesn’t know the URL was changed, so your testing environment behaves exactly like production would.

Usage

1. Open TagDragon DevTools panel on a page that loads Adobe Launch
2. Click the Adobe Environment Switcher button in the toolbar (or find it in the panel header)
3. TagDragon detects the loaded Adobe Launch library and displays its available environments
4. Select the desired environment:
   • DEV — Development environment
   • ACC — Acceptance/staging environment
   • PROD — Production environment (default)
5. The redirect applies immediately — reload the page to see the new environment’s code running

Persistence

The redirect persists across page navigations and browser restarts. Configuration is stored per hostname, so different sites can have different environment selections.

This means you can:

• Navigate between pages on the same domain without re-selecting
• Close and reopen the browser and keep your selection
• Have different environments active on different sites simultaneously

Removing a redirect

To remove a redirect:

• Select None from the environment dropdown
• Or select PROD (the original environment) to restore normal behavior
• You can also clear all redirects from the extension’s Settings panel

Requirements

The Environment Switcher requires:

• Adobe Launch (Tags) container loaded on the page
• Library configured with multiple environments (DEV, ACC, PROD)
• Access to at least one non-production environment in the Launch property

Note: The switcher works with Adobe Launch containers only. It does not support legacy DTM containers.