...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Event | Description |
|---|---|
SEND | The notification is sent from the AppArmor Dashboard. |
PROCESSED | Our backend server receives an individual message and prepares it to be delivered. |
DELIVERED | When an email has been accepted at the receiving server, the delivered event fires. |
OPEN | The user opens the email. |
CLICK | The user clicks the link in the email, which directs them to the webpage with the full notification details. |
VIEW | A user views the alert page after clicking the link. |
BOUNCE | If a server cannot or will not deliver a message, our email server fires a bounce event. Bounces often are caused by outdated or incorrectly entered email addresses. Many times you won’t know a bounced email address until it bounces. A bounce will add the email to the suppression list. |
DEFERRED | When an email cannot immediately be delivered, but it hasn’t been completely rejected, the deferred event fires. Sometimes called a soft bounce, our email server will continue to try for 72 hours to deliver a deferred message. |
DROPPED | There are a number of reasons your email will not even be sent to a recipient for delivery. This event informs your system when an email has been dropped. Further, it provides a reason for the drop. |
SKIPPED | The AppArmor system notices that there are more than one instance of a subscriber in the sending profiles that have been sent to. The system is smart enough to send a message only once to each subscriber. An email will also be skipped if it is on the suppression list. |
SPAMREPORT | Most internet service providers provide a feedback loop, sending specific spam complaints to the email service providers. When our email server receives a notice, we fire a spam event. Spam reports place the user on the suppression list. |
UNSUBSCRBE | If a user unsubscribes, they will be placed on the suppression list. |
Alert Status
Event | Description |
|---|---|
SEND | The notification is sent from the AppArmor Dashboard. |
CLICK | A user taps the Alert Status History item. |
VIEW | A user views the alert page after tapping the Alert Status History item. |
Desktop
Event | Description |
|---|---|
SEND | The notification is sent from the AppArmor Dashboard. |
VIEW | The alert appears on the device's screen. |
Event | Description |
|---|---|
SEND | The notification is sent from the AppArmor Dashboard. |
POST | Your Facebook App attempts to post to the Facebook Page. |
RESPONSE | Logs the response from the Facebook server. |
CLICK | A user clicks the Facebook post, directing them to the website. |
VIEW | A user visits the website they are directed to by the clq.io link. |
ERROR | The Facebook post fails. Usually accompanied by details on why the post failed. |
HTTP Activation
Event | Description |
|---|---|
SEND | The notification is sent from the AppArmor Dashboard. |
GET | (GET requests only) Our server hits the specified web address. |
POST | (POST requests only) Our server attempts to post to the specified web address. |
RESPONSE | Logs the response from the server to be activated. |
Push Notification
Event | Description |
|---|---|
SEND | The notification is sent from the AppArmor Dashboard. |
TAP | A user taps the push notification from their device's lock screen or notification center. |
CLICK | A user clicks the "More Info" clq.io link in their push notification. |
VIEW | A user visits the website they are directed to by the clq.io link. |
RSS
Event | Description |
|---|---|
SEND | The notification is sent from the AppArmor Dashboard. |
SMS Text Message
Important Note: Tracking events generated by cellular carriers (QUEUED, SENT, DELIVERED) are not guaranteed. Tracking events are considered low priority by the carriers, so when cellular networks become busy the carriers may choose not to send the tracking events to AppArmor. Also, some carriers do not support tracking events at all. Keep this information in mind when reviewing tracking logs. The lack of a "DELIVERED" event does not necessarily mean the message wasn't delivered, instead the carriers might have been too busy to report the event back to AppArmor.
Event | Description |
|---|---|
SEND | The notification is sent from the AppArmor Dashboard. |
QUEUED | After a message is sent from the Dashboard, it is immediately queued to be sent across cellular lines to the subscriber. |
SENT | The SMS message is sent over cellular lines. |
DELIVERED | This tracking event is provided by the subscriber's cell phone service provider, as a confirmation that the message has been delivered. Sometimes the provider will delay the delivery of this event, even though the message has been received. |
CLICK | The user clicks the clq.io link in in their text message. |
VIEW | The user visits the website they are directed to by the clq.io link. |
UNDELIVERE | Our server has received a delivery receipt indicating that the message was not delivered. This can happen for a number of reasons including carrier content filtering, availability of the destination handset, etc |
FAILED | The message could not be sent. This can happen for various reasons including queue overflows, account suspensions, etc. |
REPLYSTOP | The user has replied "STOP" to the message. They will be added to the suppression list. |
Event | Description |
|---|---|
SEND | The notification is sent from the AppArmor Dashboard. |
CLICK | A user clicks the clq.io linkn in the Tweet. |
VIEW | A user visits the website they are directed to by the clq.io link. |
Voice Call
Important Note: Tracking events generated by telephone carriers (INITIATED, RINGING, INPROGRESS, COMPLETED) are not guaranteed. Tracking events are considered low priority by the telephone carriers, so when networks become busy the telephone carriers may choose not to send the tracking events to AppArmor. Also, some telephone carriers do not support tracking events at all. Keep this information in mind when reviewing tracking logs. The lack of a "COMPLETED" event does not necessarily mean the call wasn't completed, instead the telephone carriers might have been too busy to report the event back to AppArmor.
Event | Description |
|---|---|
SEND | The notification is sent from the AppArmor Dashboard. |
INITIATED | The call has been initiated. |
DIALEXT | If necessary, extension is dialled. |
RINGING | The phone is ringing. |
INPROGRESS | Call has connected. This means either a person or an answering machine has picked up the line. |
MSGLOOP | The call will read the following 3 times "This is a Notification from <Institution Name>" → <Event> → "Dial 1 to listen to the whole message." |
PLAYMSG | If the user pushes 1, the whole message will be read. |
COMPLETED | After an answered call ends, it has a "COMPLETED" status. Completed indicates that a connection was established and some audio was played. |
WRONGKEY | The user pushes a number other than 9. |
UNSUBSCRB | The user pushes 9 to unsubscribe from future messages. |
FAILED | The call fails to complete. |
NO-ANSWER | The call rings, but is not answered after 30 seconds. |
BUSY | A busy signal is received. |
HUNT | The call reaches one of FAILED, NO-ANSWER, or BUSY, or does not reach the PLAYMSG action. This signifies that the subscriber may not have received the call successfully. The next number in the subscriber's number list is called. This action only applies to scenarios where a subscriber contains multiple phone numbers. In the Tracking Details page, you can recognize these subscribers as they have multiple phone numbers in the "subscriber" column. |
HUNTFINISH | The hunt has finished. The subscriber has either run out of numbers (ie all numbers in the subscriber have been called), or the subscriber has received the call and pressed 1, firing the PLAYMSG event. |
...