1. Home
  2. Docs
  3. Developer Docs
  4. Transactional messages

Transactional messages

Transactional messages to specific recipients

Push notifications are excellent for so-called transactional notifications. Transactional notifications are also called triggered messages, as they are triggered by a concrete action or event and are sent specifically to individual recipients. They are usually generated automatically by the shop or CRM system, such as registration confirmations, order or booking confirmations, appointment reminders, dispatch notifications, error messages, birthday greetings and follow-up purchase offers. The high opening rates of these types of messages can be explained by the fact that they are expected by the user and contain important information.

Sending these messages via web and mobile push offers several advantages. Compared to e-mail, the advantage is that the message appears directly on the recipient’s screen and is not in danger of drowning in the mailbox. This is particularly important for very time-critical information such as delay alerts. In addition, the push dispatch is usually much cheaper than SMS and also reaches desktop users.

If the sending is to be triggered by a specific user activity on the website, the corresponding automatism can be created directly in Signalize. If the trigger information is found in another system, such as the CRM or ERP system, the sending of the transactional notification can be triggered from there and transferred to Signalize via an interface.

Note: Push notifications cannot be used for sending messages back and forth. However, they can be used for messages such as “You have a new message in your inbox”.

This is how the sending of transactional pushes via third-party systems is working

1. Matching of the recipients

In Signalize, each recipient is assigned an individual pseudonymous recipient ID. The recipient ID corresponds to the Signalize or etracker cookie ID et_coid. To read this, the JavaScript function et_signalize.getClientId() is available.

The function can now be stored in the CRM system, for example, to send push notifications to individual recipients using this Signalize recipient ID.

2. Sending the message

To send a message to a specific recipient, the Signalize API provides a corresponding call. The Signalize API can be directly connected to the desired system to send the notification. Alternatively, the connection can be made via the Zapier plug-in, provided that a connection of the third-party solution to Zapier exists.

The technical description of the interface for sending messages including transactional notifications can be found here: https://docs.signalize.com/