FAQs
Frequently Asked Questions about Web Push Notification.
Last updated
Frequently Asked Questions about Web Push Notification.
Last updated
Q1. What creates a difference between the number of web push notifications successfully sent and the impressions?
This can be attributed to the following factors.
1) The user waited until the notification's expiration to log on.
2) The user's device doesn't have a running browser
3) Failure of the FCM-Browser-OS communication
4) The user has disabled notifications on their device
Q2. What are the browsers and versions supported by Lemnisk?
Chrome versions 42 and above.
Mozilla Firefox versions 44 and above.
Opera versions 25 and above.
Q3. Can we track the subscribed user who does not visit the website after integrating Lemnisk SDK?
The service worker won't be registered on the users' devices if they don't visit the website after Lemnisk SDK is integrated. Because the older service provider may use a different payload structure or may not support the Lemnisk payload structure, users won't receive the web push notification. Lemnisk won't be able to track impressions even if the user sees the notification in this situation.
Q4. Why did Web Push Notification not get delivered?
There are several reasons for which you may not be able to deliver your Web Push Notifications:
Frequency Caps: This failure occurs when the frequency cap limit is exhausted. It depends on parameters that are measured daily, weekly, monthly, or over a lifetime. Users whose frequency cap value is >0 will receive your engagement. To learn more about Frequency Caps, click .
Personalization Failure: This failure indicates that the engagement failed to send while replacing the personalizing parameters with the actual value stored in the users' profile. Use Case: Suppose there is a user in a segment with no premium amount registered. You create engagement for that segment of users using a premium amount macro with an expiration date. The user with no registered amount will not receive the engagement as that parameter does not exist in his/her stored profile.
FCM Failure: The number of notifications meant to be delivered successfully by Lemnisk, but failed due to FCM (Firebase Cloud Messaging) failure.
FCM/APNS Configuration Issue: This error arises when web configuration is disabled for push notifications, the APNS certificate is not generated or the FCM configuration is incorrect.
Unsubscribed: This indicates that the user has unsubscribed from receiving push notifications from your website.
Others: This includes all the other reasons for which the WPN was not delivered such as system failure, server crash, campaign failure, etc.