Adobe Launch Extension
The Adobe Launch (Adobe Experience Platform Tags) extension deploys the Zeotap Browser SDK through Adobe’s tag manager instead of a hand-placed <script> snippet. Marketers install the extension once, configure it with a write key, and wire rules that call the SDK — no page-side JavaScript required.
It’s one of three ways to run the browser SDK: the snippet (embed directly in your page), Adobe Launch (this page), or Google Tag Manager. All three send the same Segment-compatible events to the same ingest API.
Install
The extension is distributed as a private extension scoped to your organization — it appears in your property’s extension catalog, not the public Adobe Exchange (a public Exchange listing is planned).
- In Adobe Data Collection (Tags), open your property → Extensions → Catalog.
- Toggle the catalog to show development extensions if needed, find Zeotap Composable CDP, and click Install.
- Fill in the configuration (below), then wire your rules and publish a library.
Configure
The install-time configuration is deliberately minimal — just the settings that belong to you. Infrastructure endpoints are not exposed; the extension targets production automatically.
| Field | Type | Default | Description |
|---|---|---|---|
writeKey | string (required) | — | Your workspace source write key, from Streams → Event Sources. Supports %dataElement% tokens. |
consentMechanism | default | tcf | custom | default | How consent gates event collection (see Consent). |
piiHashingMode | hashOnClient | preHashed | hashOnClient | Whether the SDK hashes PII identities in the browser, or you pass already-hashed values. |
debug | boolean | false | Enable verbose SDK console logging. |
autoPage | boolean | true | Record a page view automatically when the SDK loads. |
flushAt | integer | 10 | Flush the event queue after this many events accumulate. |
flushInterval | integer | 5000 | Flush the event queue at this interval, in milliseconds. |
Rules and actions
You drive the SDK by binding the extension’s actions to Adobe Launch rules. The extension exposes these actions:
| Action | Purpose | Inputs |
|---|---|---|
| Load SDK | Loads the SDK and initializes it with your configuration. Run this first. | — |
| Track Event | Records a named event. | Event name, properties |
| Page View | Records a page view. | Category, name, properties |
| Identify | Associates a user ID and traits. | User ID, traits |
| Set User Identities | Sets PII identities (email, phone, etc.), hashed per piiHashingMode. | Identity key/value pairs |
| Set Consent | Sets the user’s consent state. | Consent value (parsed categories, TCF string, or US Privacy string) |
| Reset | Clears identity and queued state (call on logout). | — |
| Set Configuration | Advanced: apply a JSON override of SDK load options before Load SDK runs, so new options need no extension update. | JSON |
Every action works before and after the bundle finishes loading — calls made early are queued and replayed once the SDK is ready, exactly like the snippet.
Worked example
A typical property has one bootstrap rule plus one rule per interaction:
- Rule: Load on page top — Event: Core → Library Loaded (Page Top) → Action: Load SDK.
- Rule: Track add-to-cart — Event: Core → Click (or a Direct Call) → Action: Track Event with name
Product Addedand properties mapped from data elements (%product.id%,%product.price%). - Rule: Identify on login — Event: your login trigger → Actions: Identify (user ID + traits) and Set User Identities (email/phone).
Publish the rules into a Launch library and assign it to an environment to activate them on your site.
Consent
The consentMechanism setting maps to the SDK’s consent behavior:
default— no gating. Events flow immediately; call Set Consent whenever you want to attach consent state to events.tcf— opt-in gating with automatic IAB TCF v2 CMP detection. The SDK reads__tcfapi, waits for the CMP, and only sends events once the required purposes are granted.custom— opt-in gating where you resolve consent yourself: events are held until a Set Consent action fires with the resolved state.
See Consent Management for how consent categories gate downstream forwarding and land in the warehouse.
Validate
After publishing a development library and loading your page:
- Use the Adobe Experience Platform Debugger browser extension to confirm the Launch library loaded, your rules fired, and the extension’s actions ran.
- Open the Network tab and confirm each action results in a
POST /v1/batchreturning200. - Watch events arrive in real time on the platform’s Live Event Stream (Streams → Overview → Live Stream), and verify counts under the events overview. See Debugging.
For internal and staging testing, Zeotap-owned properties can point the extension at a non-production ingest by defining the data elements zeotapApiHost and zeotapSdkUrl. These are read by the extension but are never exposed as customer configuration — customer properties always use production.
Next Steps
- Browser SDK — the underlying SDK API the extension drives
- Event sources — create and manage write keys
- Consent management — configure consent categories
- Event forwarding — route events to destinations and warehouses
- Debugging — verify events are arriving