Adobe Launch Documentation & Audit

Paste your Adobe Launch embed code and get a complete, readable record of the property — every rule, data element, extension and line of custom code — plus an audit of what is quietly broken.

It runs entirely in your browser. Your library is never uploaded to us.

1 · Point it at your library

Paste the embed <script> tag from your Launch environment, the embed URL on its own, the contents of a launch-*.min.js file, or an exported container JSON. The tool works out which one you gave it.

Embed snippet, URL or library code

Or drop a launch-*.js / .json file here
…or click to browse.

Advanced options

Recover external custom-code files Custom code stored outside the main library is read so the full source appears in the workbook. Leave this on unless you are in a hurry. Allow relaxed parsing of older builds Some older libraries emit the container as a JavaScript object literal rather than strict JSON.

CORS proxy template (optional)

Only used if a direct download is blocked by your network. {url} is replaced with the library URL.

What the audit looks for

A built Launch library is the only complete record of what a property actually does — and it is not designed to be read. Most of what goes wrong in a mature implementation is invisible in the Launch interface, because nothing in that interface compares one rule against another.

Variables that never receive a value

An eVar aliased to itself instead of its matching prop looks correct in the UI and collects nothing. We weight these by whether any other rule sets the variable, so a genuine gap is not buried alongside a harmless duplicate.

Broken data element references

Rules referencing data elements that no longer exist, and data elements defined but referenced nowhere. Both accumulate quietly across years of releases.

Identifiers that differ only by capitalisation

Direct calls and custom events are case sensitive at runtime. Two spellings of the same name means one of them has probably never fired.

Rules that set variables but never send a beacon

Legitimate when another rule sends the hit later in the same page view. Worth confirming when nothing does.

Governance and hygiene

Console logging left in production, unguarded jQuery dependencies, insecure http references, cookies written from tag code, duplicated custom code, and extensions installed but never used.

Findings you would rather not have found?

An analytics audit goes further than a static read of the library — measurement design, governance, and what your reports are actually telling you.

Request an Audit →

Adobe Launch Documentation & Audit

1 · Point it at your library

What needs attention

Get the full documentation

Thanks — your download is ready

What the audit looks for

Findings you would rather not have found?