Glossary
Plain-English definitions for the terms you’ll see across the dashboard, the SDKs, and the docs. Each entry links to the canonical chapter for depth.A
Activity Log — Per-campaign feed of who edited what and when. Real-time, visible inside each campaign’s “Activity” tab. See activity log. Archived (campaign status) — Terminal status. The campaign no longer creates new workflow instances; existing in-flight instances complete normally. See campaigns. Auth Secret — Server-side secret used byclient.generateHashedToken(userId) to mint widget auth tokens. Never sent over the wire. See keys and environments.
B
BackendToken (auth mode) — Widget auth strategy. Your backend HMAC-signs a token per user; Notifizz recomputes the hash to verify. See backend tokens. Brand — Top-level dashboard concept (/org/:org/app/brand). Holds organisation-wide visual identity tokens reused across campaigns and channels. See brands and variables.
Bridge commands — The public list of programmatic commands the widget accepts (open, close, toggle, getState, …). See widget bridge reference.
C
Campaign — Dashboard-defined reaction to an event. Owns orchestrator code, channel configurations, status. Sometimes called “workflow” in older code paths — same thing. See campaigns. Campaign Category —Transactional or Promotional. Drives queue priority — transactional campaigns jump the queue. See campaigns.
Campaign Version — Monotonic version number stamped on each save. In-flight workflow instances run against the version they started on.
Channel — Delivery method for a notification (Notification Center widget, email, …). The campaign picks the channel; the channel processor renders + dispatches. See channels.
Codegen — AI-generated orchestrator code from the campaign description. Editable; the AI proposes, the human reviews and ships.
Connector — Built-in integration with an external source (Segment, Stripe, HubSpot, Intercom). Provides webhook ingestion + event mapping. See connector webhooks.
Correlation ID — Stable id stamped at message creation time, propagating through every queue hop and inbox write. Used for end-to-end tracing. See observability.
Custom Bell — Replacing the widget’s default bell with your own UI element. Each frontend SDK exposes a slightly different API (React: renderBell; Angular: #customBellIcon; Vanilla: setBellElement).
D
Delivery History — Top-level dashboard page (/org/:org/app/inbox). Timeline of every notification sent across all campaigns. See delivery history & stats.
Dev Task — Proactive issue surfaced by the dashboard during campaign authoring (missing event property, undefined enricher, …). The AI proposes resolutions.
Dev (campaign status) — Campaign is staged for review. Runs on dev environments only; explicitly skipped on prod. See campaigns.
Discovery (enricher) — GET ? against the customer’s enricher URL. Returns the list of registered enrichers + their JSON schemas + cache policies. See enrichers protocol.
Editing (campaign status) — Initial campaign status. Included in the runnable filter at instance creation; downstream behaviour is constrained by dev tasks and other gates.
E
Enricher — Server-side function the orchestrator calls at notification time to fetch live data. HMAC-signed webhook contract. Currently Node-SDK-only. See enrichers tutorial and enrichers protocol. Environment — Per-org sandbox. Each env has its own keys, its own campaign-runtime state, its own delivery history. Typicallydev and prod. See environments.
Environment Variable (Notifizz) — Variable scoped to a single environment, edited inline from the campaigns flow. Distinct from organisation variables (which are org-wide). See brands and variables.
Event — What your code emits with client.track(eventName, properties). The unit of input the platform reacts to. See events.
Event Properties — JSON object attached to an event. Used for recipient resolution, template substitution, orchestrator branching.
F
FAQ (page convention) — Mintlify accordion block at the bottom of every doc page. Captures the long-tail “but what about…” questions Google’s AI Overviews and competitors mine for content. Final User — Your end-user, in Notifizz’s terminology. The recipient of notifications, distinct from the dashboard user (your team). Firebase (auth mode) — Widget auth strategy that verifies a Firebase ID token against the Firebase JWKS. See Firebase auth. Front API Key — Public-by-design key embedded in your frontend bundle. Used by the widget to identify the environment. See keys and environments. Front Auth Strategy — Server-side strategy chosen per environment in the dashboard. Can beFirebase, BackendToken, None, or PubliclySignedJwt.
G
GET / discovery — See “Discovery (enricher)”.I
Idempotency Key — Caller-supplied dedupe identifier ontrack(). Retried emits with the same key short-circuit at the backend. See Event Tracking.
Integration Source — A single configured connector (e.g. one Stripe account or one Segment source). Each has its own verificationSecret. See integrations.
L
Live (campaign status) — Campaign approved for production. Runs on every environment (dev + prod).N
None (auth mode) — Widget auth strategy with no token verification. Dev-only. See no auth. Notification Center — In-app widget channel. Real-time bell + dropdown. Three SDKs: React, Angular, Vanilla. See Notification Center overview. Notification Center Config — Stored template for an NC message. Edited in the dashboard; referenced by campaigns. Sometimes called “notif” in older code.O
Offline (campaign status) — Campaign paused. Listed alongside other statuses; can be promoted back toLive.
Orchestrator — The code inside a campaign that runs server-side per matching event. Builds the recipient list. AI-generated, editable. See orchestrator.
Organisation — Top-level Notifizz tenant. Owns billing, team membership, and one or more environments.
Organisation Variable — Variable defined once per organisation and reusable across campaigns. See brands and variables.
P
PubliclySignedJwt (auth mode) — Widget auth strategy that verifies a JWT against your IDP’s JWKS endpoint. Configured server-side via dashboard, no SDK shorthand. AliasedCustomRsaJwt in backend code. See publicly-signed JWT.
R
Recipient — A user the campaign targets. Each must have at minimumid + email. Produced by the orchestrator, not by the SDK call site. See recipients.
Region — Notifizz region (EU today; US/APAC follow). Determines API hostname; environment-scoped.
Runnable statuses — The set [Editing, Dev, Live, Offline]. Statuses that pass the initial campaign-match filter when an event arrives.
S
SDK Secret — Server-side secret used as the Bearer token onPOST /v1/events/track and to look up the environment. See keys and environments.
SemVer — Semantic Versioning. Notifizz SDKs follow SemVer per package. See versioning policy.
Source (connector) — See “Integration Source”.
T
Track — The verb.client.track(eventName, properties, options) — the only event-emission API.
V
Variable Catalog — Per-template snapshot of variable definitions sent to the widget at message creation time. Lets the widget resolve{{var:<id>}} tokens without an extra API call.
Verification Secret — Per-source secret used by Notifizz to verify connector webhook signatures. Different per provider scheme (HMAC-SHA1 / SHA256 / Stripe-format).
W
Webhook Signing Secret — Server-side secret used by the Node SDK enricher subsystem to verify HMAC on inbound webhooks from the Notifizz backend. See keys and environments. Workflow — Synonym for “campaign” in older code paths and some dashboard labels. Same thing. Workflow Instance — One execution of a campaign’s orchestrator for one matching event. Carries the event payload, the campaign version, the correlation id, the recipient list. See how Notifizz works.See also
Product overview
Where each concept lives.
How Notifizz works
The technical pipeline end to end.
Backend quickstart
See the concepts in action.
Troubleshooting
Cross-cutting failure modes.