write_key and consent options, and wire up Rules that fire Zeotap Actions — load the SDK, sync identities, track events, set custom consent — when your Adobe Events match.
How it works
Adobe Tags (formerly Launch) has four building blocks:- Tags — your tag property (the container).
- Extensions — packages of JS/HTML/CSS that add functionality. Zeotap Collect is one such extension.
- Rules —
if/thenlogic combining events, conditions, and actions. - Data Elements — variables stored in your tag property that fill in values when Actions fire.
| Action Type | Purpose |
|---|---|
| Load Zeotap SDK | Stamp the Zeotap JS on the page. Required as the first action in your initialization rule. |
| Set Custom Consent | Required if you chose Custom Consent. Also used to set brand consent under any consent method. |
| Sync User Identities | Set key-value pairs for User PIIs and Custom Identities. |
| Track Event | Send a Page View, User Attributes event, or Custom Event. |
Prerequisites
- Access to a Zeotap CDP instance with an Adobe Experience Platform Tag Extension Source (provides your
write_key) - An Adobe Experience Platform Tags account and a tag property installed on your site
- Familiarity with Adobe Rules and Data Elements
Explore the docs
Quick Start
Install the extension, set up your first Rule, fire an event.
Configuration
Write key, consent method, PII hashing, country code.
API Reference
All Action Types, Event Types, and identity keys.
Examples
Rule patterns for load, identity, consent, and events.
FAQ
Validation, debugging, common gotchas.
External reference
Authoritative Adobe Launch SDK documentation.