How to migrate Web Push Subscribers from other platforms to MoEngage

Objective

Migrate web push subscriber base from other platforms to MoEngage and target these users via campaigns created on MoEngage.

Steps to be carried out

1. Integrate MoEngage SDK with your website. Please refer to the integration document for steps to integrate the SDK.
2. Create campaigns targeting ‘All Users’ in the previous vendor platform and redirect the users onto your website. The objective of this step is to register the MoEngage Service Worker on the user’s device which is required to show WebPush Notifications from campaigns created on the MoEngage Platform. Keep targeting the user until the majority of the existing users have been registered on MoEngage. You can find the web push subscriber count on the key metrics page on MoEngage.
3. If a user has already subscribed to receive web push notifications from your website, the opt-in permission would not be shown to the user. In the backend, the following steps would occur:
   i) Registering of the MoEngage Service Worker
   ii) Generation of a push token for this user.
   iii) Capture device details such as Browser type, Browser version, and so on.
4. Users will now be able to receive Push Notifications from campaigns created on MoEngage Dashboard.

FAQs

Q: What if the subscribed users do not visit the website after integrating the MoEngage SDK? Will they be reachable via Web Push Campaigns?

Ans: If the users do not visit the website after the MoEngage SDK is integrated, the MoEngage service worker would not be registered on their device. Hence users will not receive the web push notification as the older service worker (from the previous vendor) may be following a different payload structure and it may not support the MoEngage payload structure. Even if the notification is shown to the user, MoEngage will not be able to track impressions in this case.