This guide will walk you through all the steps to have full email integration with OneSignal.
Required unless setup for you by OneSignal.
Sending emails through OneSignal requires an account with an eligible email service provider listed below. If you do not have an account with any of these Email Providers Contact OneSignal's Sales Team and ask about Email Onboarding.
Optional but recommended if using the OneSignal SDK. Methods provided for creating new email records as they are provided to you. See Email SDK Methods to for a full list and example code.
Optional but recommended if you have a website and want to prompt users to provide their email. Use the Email & Phone Number Web Prompt to start gathering emails through a web prompt.
Optional but recommended if you already have a list of email addresses and wish to immediately start sending emails, you can import them into OneSignal.
You can import emails through our Dashboard or server API. Details and code examples are available in Import Email Addresses guide.
Required if using integrations.
Each email record in OneSignal gets a unique player_id (OneSignal's Device Id). The email player_id will be different from the push record player_id.
To map the unique email and push player_ids together under a single User Id, use the OneSignal
setExternalUserId SDK method. See External User Ids. It is recommended to call this method after the email is set.
Use Data Tags for custom user and event properties. These allow for message personalization and segmentation.
Common tags used for message personalization:
|Tag Key||Tag Value|
|user’s full real name|
|user’s first name|
|user’s last name|
|name that users give themselves; often not a real name (e.g. PokeCatcher22)|
|if you wish to refer to users by a salutation (Ms, Dr, Hon, etc)|
Send emails using OneSignal's:
You are a OneSignal Email Pro!
Updated 10 days ago