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.
Broadcast — Campaign whose trigger is a launch — manual or scheduled — instead of an event. The audience is a CRM segment resolved live at launch and frozen there. Closed beta, off by default. See broadcasts.
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 renders the template and delivers. 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.
Conversion — One credit for a recipient who received a campaign and then triggered its objective. Deduped: the same recipient never counts twice on the same campaign. See objectives and conversions.
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), labelled Outbox in the interface. Timeline of every notification sent across all campaigns. See delivery history & stats.
Discovery (enricher) — GET ? against the customer’s enricher URL. Returns the list of registered enrichers + their JSON schemas + cache policies. See enrichers protocol.
E
Editing (campaign status) — Initial campaign status: the campaign is being authored. It matches incoming events but its runs are cancelled before anything is sent — to try it, use the dashboard’s rehearsal. See campaigns. Enricher — Server-side function the orchestrator calls at notification time to fetch live data. HMAC-signed webhook contract. Available in the Node, Java, and PHP SDKs. 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
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.
Implementation (campaign status) — Campaign whose orchestrator has been reconciled against your events and enrichers; any implementation tasks it raised are waiting on a developer. Dropped at match on production, and cancelled mid-run elsewhere: a real event never produces a send. Rehearse it from the dashboard. Displayed as Dev before July 2026. See campaigns.
Implementation Task — Issue raised by the AI orchestrator when it reconciles a campaign against your codebase (missing event property, undefined enricher, missing enricher field). Executable from your IDE over MCP. Called a dev task before July 2026.
Integration Source — A single configured connector (e.g. one Stripe account or one Segment source). Each has its own verificationSecret. See integrations.
L
Link Route — Per-message redirect wrapped around a clickable link in a notification: Notifizz records the click, then sends the user to your destination URL. See link routes. Live (campaign status) — Campaign approved for production. Runs on every environment, but only a production environment turns that run into a real delivery — elsewhere it reaches sandbox testers. The only status that accrues statistics.M
MCP — Model Context Protocol. Notifizz runs an MCP server your IDE’s AI assistant connects to: it reads campaign status and implementation tasks, and can drive the campaign journey without leaving your editor. See connect your AI tool and the tool reference.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
Objective — The event that decides whether a campaign worked:Click, Read, or any custom event from your catalog. Set per campaign. See objectives and conversions.
Offline (campaign status) — Campaign paused. Still passes the runnable filter, but delivers nothing — not even to sandbox testers. Can be promoted back to Live.
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.
Outbox — The dashboard label for Delivery History. Two tabs: every workflow run, and every objective evaluation — click a row for the payload behind it. See delivery history & stats.
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. 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.
Review (campaign status) — Campaign complete and waiting for a human to approve it. The only non-Live status that delivers from a real event, and only outside production, to sandbox testers; on production it is dropped at match. See campaigns.
Runnable statuses — The set [Editing, Implementation, Review, Live, Offline]. Statuses that pass the initial campaign-match filter when an event arrives; Archived is the only one hard-excluded. Passing the filter is not the same as delivering — see send scope.
S
Sandbox testers — Your own team’s verified test inboxes and opted-in browsers. Anything that is not aLive campaign fired from production lands here instead of reaching real recipients. See send scope.
SDK Secret — Server-side secret used as the Bearer token on POST /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”.
Synthetic Event — Event Notifizz generates for you instead of your code — scheduled, grouped, reminder, or milestone. It travels the same pipeline as a tracked event and carries a _synthetic marker in its properties. See synthetic events.
T
Team — Named group of people in your organisation. Owns views and appears in the sidebar; you only see the teams you belong to. See teams and views. 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).
View — Saved, filtered lens on your campaigns, owned by a team and shared with it. Filters on status, event, user flow and AARRR objective. Subscribing to one is personal: subscribers are notified when a campaign enters or leaves it. See teams and views.
W
Web Push — Browser push notifications delivered under your own VAPID identity, even when your product’s tab is closed. Carried by the Notification Center widget; the opt-in is always the user’s. Closed beta. See web push. Webhook Signing Secret — Server-side secret used by the SDK enricher subsystem (Node, Java, PHP) to verify HMAC on inbound webhooks from Notifizz. 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.