Action Types
Available under Rules → Actions → Extension: Zeotap Collect → Action Type.| Action Type | Description | Web JS method invoked |
|---|---|---|
| Load Zeotap SDK | Stamps the Zeotap JS on the page. Required as the first action in your initialization rule. | (SDK bootstrap) |
| Set Custom Consent | Sets primary or brand consent. Required if Consent Method is Custom. Also used for brand consent under any method. | setConsent(...) |
| Sync User Identities | Sets key-value pairs for User PIIs and Custom Identities. | setUserIdentities(...) |
| Track Event | Sends an event. Pick Event Type: Page View, User Attributes, or Custom Event. | setEventProperties / setPageProperties / setUserProperties |
Track Event — Event Types
When you select Track Event as the Action Type, pick one of three Event Types.Page View
Sends a page-view event. Set key-value pairs that describe the page (name, category, etc.). Invokes:setPageProperties({ name, category, ... })
When this rule is triggered, the configured key-value pairs are merged with any event attributes passed as a second argument to _satellite.track(directCall).
User Attributes
Attaches user-level attributes to the currentzi and identities. Set key-value pairs for age, gender, plan tier, etc. You can add unlimited keys.
Invokes: setUserProperties({ ... })
country and city are blacklisted for ingestion — Zeotap derives these from the IP address. See blacklisted fields.Custom Event
Sends a named event with arbitrary properties.- Name — the event name.
- Key-value pairs — properties attached to this event.
setEventProperties(eventName, { ... })
Sync User Identities — accepted keys
Raw PII (with PII Hashing: “raw and hashed by Zeotap” or “raw and consumed as is”)
| Key | Description |
|---|---|
fpuid | First-party ID (CRM ID, DB ID). |
email | User’s raw email address. |
cellno | Cell number without country code. |
cellno_cc | Cell number with country code. |
loginid | User’s login ID. |
Pre-hashed PII (with PII Hashing: “hashed by the customer”)
Email:email_{sha256,sha1,md5}_{lowercase,uppercase}
cellno_without_country_code_{sha256,sha1,md5}
cellno_with_country_code_{sha256,sha1,md5}
cellno_e164_{sha256,sha1,md5}
loginid_{sha256,sha1,md5}_{lowercase,uppercase}
Custom identities
Any first-party identifier outside the reserved PII keys —crmID, ECID, visitorID, etc. Sent as-is. PII hashing flags don’t apply.
See hashing guidelines for expected preprocessing.
Set Custom Consent — fields
| Field | Description |
|---|---|
track | Allow event tracking. (Custom mode only) |
identify | Allow user identification / ID+. (Custom mode only) |
cookieSync | Allow partner cookie sync. (Custom mode only) |
<brandConsent> | Any brand-specific consent key (e.g. zeotapVendorConsent, xyzVendorConsent). Honored under any consent method. |
Cookie sync request — payload reference
When the extension fires a cookie sync, the request looks like:| Query parameter | Description |
|---|---|
optin | Whether the SDK has consent for any action. |
track | Consent to track event or user data. |
identify | Consent to identify the user via ID+ 1P cookie. |
cookieSync | Consent to sync cookies with partners. |
cmp | 1 if consent was resolved via TCF API; 0 otherwise. |
gdpr_consent | TCF v2 consent string (TCF mode). |
| Query parameter | Description |
|---|---|
w_k | Encoded write_key of the Source. |
payload | Encoded identities passed to Zeotap JS — User PIIs, custom identities, default 1P cookies. |