Encourage users to subscribe for your push notifications or emails
Once the project is configured and the SDK is integrated, provide users can subscribe to your push notifications and emails — otherwise, you won't be able to communicate with them.
To encourage users to opt-in for push notifications, preface the default opt-in popup of the device's OS with a custom-made in-app message. Explain the benefits that come with opting in for your push notifications – this can increase the user's willingness to subscribe to your messages.
To provide your website visitors can opt-in for push notifications, implement the custom or default Subscription Prompt on your site. The prompt triggers the native subscription request pop-up in the user's browser, which, in turn, enables or blocks web push notifications for your site.
Web users cannot be imported due to technical limitations of web platform — push providers use different payload formats as well as platform configuration, which makes import basically useless, as the user base would be either invalidated or would be receiving blank/wrong content.
Please note that the
registerEmailUserrequest does not register an email address in your userbase; it should be used only to assign User IDs to emails already registered by the
To associate your app users or site visitors with their email addresses, use the User IDs. That allows you to build cross-channel Customer Journeys and send emails based on user's actions in your app or on the website.
1. Get the User ID.
2. Assign the User ID to an email address.
3. That’s it!
The same User ID is assigned to a particular device and a specified email address. That means Pushwoosh considers both app user and email addressee the same person so you can reach out to them by pushes and emails within a cross-channel Customer Journey.