How CRM campaigns and backend events become timely, actionable messages in the player experience
Swivel has two notification types. They use different triggers and content rules, but both create the same per-player notification record and appear in the same notification drawer.
A reusable content resource selected by a CRM campaign and awarded to a targeted player.
A template tied to a known backend event, rendered with values from that event for one player.
Once either source requests delivery, the same asynchronous pipeline handles persistence, duplicate protection, live updates, and the player UI.
Every delivery request carries an idempotency key. That key is unique on the per-player record, preventing the same campaign award or system event from creating the same notification twice.
If the template has an expiration duration, expiresAt is calculated when the player receives the
notification. Expired items are excluded from the drawer and unread count.
CRM notifications are content resources. Creating one does not send it; a campaign or CRM callback must award it to a player.
Configure title, message, optional expiration, image and call to action. Swivel stores it as type
crm.
For Optimove, a worker creates a notification channel template and saves its external template ID. For Smartico, active CRM notifications are exposed through the CRM database view.
Optimove maps its channel template ID back to the Swivel resource. Smartico can attach a notification template ID to a bonus, package or tournament award.
The CRM supplies the player, resource and delivery identity. Prescheduled Optimove campaigns may delay the queue job until the campaign schedule time; real-time awards are queued immediately.
Archiving removes a CRM notification from the active Admin view and Smartico's active notification view, but the delivery worker does not apply a universal archive check to CRM awards. Stop or update active CRM campaigns as well, especially when awards may already be scheduled.
A system template is selected by kind. The backend supplies only the values listed for
that kind.
| Kind | When it fires | Available placeholders |
|---|---|---|
Deposit completeddepositCompleted |
After a player's deposit invoice completes | {{amount}} {{currency}} |
Payout completedpayoutCompleted |
After a player's payout completes | {{amount}} {{currency}} |
Level uplevelUp |
When experience gain moves a player to another level | {{levelName}} |
Tournament prize awardedtournamentPrizeAwarded |
When finished-tournament prizes are awarded | {{tournamentName}} {{rank}} |
Expiry confiscation noticeexpiryConfiscationNotice |
When the balance-expiry notice process contacts affected players | {{currency}} |
Both title and message are rendered by replacing tokens such as {{amount}}. The rendered values
are saved on the player's record, so later template edits do not rewrite notifications already delivered.
If the selected kind has no active template, the worker creates no player notification. Archiving a system template therefore disables future delivery for that kind without disabling the underlying platform event.
The Admin form shows the valid tokens for the selected kind. Unknown or misspelled tokens are left unchanged and can appear literally to players.
Required: title and message.
Optional: expiration, image, CTA text and CTA link. The Admin image control requires at least 282 × 110 px. A CTA can open an internal Swivel path or an external URL; if CTA text is omitted, the player UI uses its default “Learn more” label.
A live delivery updates the unread count and displays a four-second toast. Opening the notification drawer loads newest-first cards with the message, optional image and CTA.
Players can mark one or all notifications as read, and delete one or all. Deletion is soft deletion of that player's record, not deletion of the shared template.
CRM deliveries use the shared template title and text when read. Editing that CRM copy can therefore change the text shown on existing, non-expired player notifications.
System deliveries store their rendered title and message. Template edits affect only future events; existing player notifications keep the wording and values rendered at delivery time.
These are the backend route groups used by the Admin and player applications.
/notifications/List and filter/system/unused-kindsAvailable kinds/crmCreate CRM resource/crm/:idEdit or archive CRM/systemCreate system template/system/:idEdit or archive system/user-notifications/Active notifications/:idMark one as read/Mark all as read/:idDelete one/Delete all