Skip to main content
All CollectionsNotifications
What is the purpose of the notification state system?
What is the purpose of the notification state system?

Find out about the benefits of using our notification states.

Updated over a year ago

The state system has been designed to enable you to drive any workflows you wish to happen off the back of receiving a notification.

This we believe, combined with the ability to supply instructions as part of all of our analytics configurations, should assist in providing your users with the ability to know how to analyse, use and escalate any notifications received.

What states are there?

  • New

    • Notifications first arrive in the system with this state.

    • This state drives the count that is shown beside the "bell" icon in the web app header, and for native client notification badges.

  • Action Required

    • This state is intended to act as a signpost that a notification has been accepted and requires further investigation or actions.

  • Closed

    • Once any actions required have been completed, this state is intended to reflect this.

  • Rejected

    • A special state that is intended for customers to signal that a notification that has arrived can be discarded.

      • We recommend using this state to review unnecessary notifications, allowing you to use this to consider if your analytics configurations are optimised.

Did this answer your question?