Skip to main content

​
How Notifizz works

Notifizz follows a straightforward event-driven model. Your backend tells Notifizz that something happened, Notifizz figures out who should be notified and how, and your frontend widget displays the result — all in real time.

​
The notification lifecycle

1

Track an event

When something noteworthy happens in your application (a user signs up, an invoice is paid, a task is assigned), your backend SDK calls client.track(). You specify an event name, properties (key-value data), one or more workflows, and the recipients.
2

Notifizz processes the event

Notifizz receives the event, matches it against the specified workflow(s), and resolves the notification content. This includes applying any dynamic properties you passed to personalize the message.
3

Real-time delivery

The notification is pushed in real time to all connected frontend widgets belonging to the targeted recipients. There is no polling — the widget receives updates instantly via a persistent connection.
4

Display in the Notification Center

The frontend widget automatically updates the unread badge count and adds the new notification to the list. No code changes needed on the frontend — the widget handles rendering, read/unread state, and UI updates.

​
What you control

From the backend, you control what happens: which events are tracked, who receives notifications, and what data is attached. From the frontend, you control how it looks: where the bell is positioned, whether to use the default UI or a custom one, and how your app reacts to state changes (e.g. updating a page title with the unread count). From the Notifizz dashboard, you configure workflows, notification templates, and campaign settings without deploying code.

​
Next steps

Events and workflows

Understand the building blocks: events, workflows, properties, and recipients.

Authentication

Choose the right auth strategy for your app.