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 the Google Tag Manager template. 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 Agentic 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. |
sessionTracking | boolean | true | Group activity into sessions (visits) and carry the session id plus its rollup on every event. Zeotap emits a session_end event when a visit goes quiet — see Sessions. |
sessionTimeoutMinutes | integer | 30 | Inactivity before the next event starts a new session. Clamped to between 5 seconds and 30 minutes. Shown only when sessionTracking is enabled. |
firstPartyCookies | boolean | false | Persist the visitor’s anonymous ID as a server-set, HttpOnly first-party cookie — survives Safari ITP’s 7-day cap on script-written storage. Requires firstPartyEndpoint. |
siteKey | string | — | Site key (personalization): the public key of a Site, psk_…. A key turns personalization on — see Personalization. Supports %dataElement% tokens. |
personalizationEndpoint | string | — | Serving endpoint (optional): shown only beside a Site key. Leave empty unless your events go through a first-party proxy and you are given a value. |
firstPartyEndpoint | string | — | Where your first-party proxy is mounted: a path on your site (e.g. /cdp) or an https:// URL on a subdomain you operate. Shown and required only when firstPartyCookies is enabled. |
First-party persistent cookie
Enabling First-party persistent cookie routes SDK traffic through a proxy on your own domain and lets the events endpoint stamp the visitor ID as a durable first-party cookie. Set up the proxy first — see First-Party Domain Setup — then enter its mount point as the first-party endpoint. The extension derives the right request mode automatically: a path (/cdp) sends same-origin requests; a subdomain URL sends credentialed cross-origin requests.
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). | — |
| Refresh Personalization | Reads the visitor’s Site again now — see Personalization. | Reason (optional) |
| 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.
Personalization
The extension can also receive. With a Site key in its configuration, the same Load SDK action turns personalization on, and Launch rules can use what the Site shares for the visitor — the audiences it labels, its realtime attributes and its profile fields. Where the answer is delivered on the page, what makes the page read again and the consent it needs are set on the Site, not in Launch. Personalization needs version 0.4.0 or later of the extension.
Set it up
-
Configure. In Extensions → Zeotap Agentic CDP → Configure, paste the Site key (
psk_…, from the Site’s Install dialog) beside the write key. Leave Serving endpoint empty. Keep your Load SDK rule as it is. -
Data elements. Add data elements of extension type Zeotap Agentic CDP, each with one setting, the Label the Site shares the item under:
Data element Returns Personalization: Label Membership trueorfalsefor an audience labelPersonalization: Attribute Value The realtime attribute’s value Personalization: Profile Field The profile field’s value They read the visitor’s current answer from the SDK, not from the data layer, so they work whichever places your Site delivers to. Set their Storage Duration to None so they are read fresh every time.
-
Event: Personalization Ready. Use it as the event of any rule that decides something from these data elements. It fires when the visitor’s answer arrives and again every time it is refreshed — a trigger the Site lists, a sign-in, or the action below. The answer is also on the event:
%event.detail.audiences%,%event.detail.attributes%,%event.detail.profile%. -
Action: Refresh Personalization reads again now from any rule, for example on an add to cart, with an optional reason for the debug output. Reads closer together than the Site’s minimum interval are combined, and each new answer fires Personalization Ready again.
Why rules use the event, not Library Loaded
The answer arrives over the network after the page starts, and Launch evaluates data elements synchronously. So before the first answer every personalization data element returns no value (undefined, which lets Launch apply the element’s default) — never false — and a rule on Library Loaded would see that. A rule on Personalization Ready runs with the answer in hand. A part of the answer that could not be read this time also returns no value, so your default applies rather than a confident “no”.
See On your website for the whole of what the page receives, when it reads again, and consent.
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
- On your website — what a page receives from a Site
- 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