When a user logs out of their account (Event is fired to indicate that the user is no longer reachable on the device-browser). When the server returns the error, token not present/ Token updates (Event is fired at end-user’s service-worker file for older tokens that get unsubscribed) (Event is fired at end-user’s service-worker file) When a user revokes Web Push permission for your site through their browser settings. Event originates from the end-user’s service-worker file and can be fired if the end-user is on the webpage or from the service-worker running in the background. Main purpose is to map a reachable subscription token to a valid LUID / CUID. When Session Starts / User Logins / User Logouts / Session Resets: Since in all these cases, the LUID changes and the WebSDK reloads, the event is fired to map the latest LUID with a valid subscription token. When a user subscribes to your Web Push Notifications by clicking Allow on the native browser prompt When a user clicks on a link embedded in the email. When a user subscribes again to receive emails from you. When a user or an inbox provider like Gmail complains about the email (in case of phishing etc.). When the email is successfully received by a user, as reported by the ESP. When an email is bounced back from the user's inbox, as reported by the ESP. Subsequently, the message may or may not get delivered. When an ESP sends the email to your user. When an ESP receives the email sent by WebEngage for delivery to the customer. When an ESP rejects the email sent by WebEngage for delivery to the customer. When an ESP accepts the email sent by WebEngage for delivery to the customer. When an Email is Queued for delivery by WebEngage to an ESP. When an SSP reports delivery failure for an SMS sent to a user. When an SSP send the message to your user's network provider for delivery. When an SSP rejects the SMS sent by WebEngage for delivery to the customer. When an SSP accepts the SMS sent by WebEngage for delivery to the customer. When an SMS is Queued for delivery by WebEngage to an SSP. When a user submits Feedback through the widget. When a user closes the On-site Feedback Widget. When a user views the On-site Feedback Widget. When a user clicks on an On-site Notification or an In-app Notification. When a user closes an On-site Notification or an In-app Notification. When a user views an On-site Notification or an In-app Notification. Notification (On-site & In-app) Impression When a user views the images of a Carousel-style Push Notification. When a user submits a rating for a Rating-style Push Notification. When a user clicks a Mobile Push Notification or Web Push Notification. When our system renders a Mobile Push Notification or Web Push Notification. When a user dismisses a Mobile Push Notification or Web Push Notification. When a device successfully receives a Mobile Push Notification. OR When a Web Push Notification is rejected by our VAPID server. When a Mobile Push Notification is rejected by FCM. When a Web Push Notification is sent to our VAPID server for delivery by WebEngage. OR When a Web Push Notification is Queued for delivery to our VAPID server. When a Mobile Push Notification is Queued for delivery by WebEngage to FCM. When a Push Notification is sent to FCM for delivery by WebEngage. When an iOS device fails to get registered for receiving Push Notifications. When a device is registered successfully to receive Push Notifications. When a user performs the Conversion Event defined for a campaign/journey. (Here's what a session means in WebEngage) Whenever a new session is started by your user. Whenever you call the login function on user login, signup etc. When the app is installed and launched for the first time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |