OneSignal will automatically remove duplicates and combine associated tags. If the email record is marked as unsubscribed, it will continue to be marked unsubscribed unless manually updated.
Email records will have a separate device record (Player ID) than push notification subscribers. This is to manage cases of the user opting-out of one channel, you can still message them on the other.
Within Audience > All Users, you can import a CSV list of email addresses or add email addresses directly.
CSV Email Upload
- Must have
- Limited to UTF-8 Encoding
- Columns must be unique
- 10 columns max
- Commas only
- No quotes
Select Actions > Import/Update Users
Next to "Import Emails", select Upload CSV
Make sure you have an
Click Actions > Manually Add Emails to open a new modal where you can add an individual user's email and tag data.
In addition to adding a user's email, you may also add/update Data Tags to the user record. The Manually Add Users modal supports adding up to 10 tags.
If the email address you enter is not found in your OneSignal user list, a new user will be created. However, if the email address is found, the user will be updated with any tags that you add here. If a user already has a tag with a particular key (e.g.
levels_completed), any value you add here will replace the value the user record previously had.
A benefit of using OneSignal for email is the ability to control both a user's Push and Email subscriptions together in one place.
Using the Server API Add a device endpoint, you can import your Email Addresses into OneSignal.
This creates a new unique Email Record Player ID in OneSignal. To associate the OneSignal Player ID Records across Email, Push, and SMS together to the same User, set the
external_user_id parameter to be your unique User ID from your databases.
If you are storing the OneSignal Push Record Player IDs in your database, you can also link this to the Email Record Player ID using the
See the following for example code:
Each OneSignal SDK has a
setEmail method which should be called when the user provides their email.
This creates a new Email Player ID record and associates it with the Push Player ID record for that user by calling this method.
setEmail multiple times with the same email will not create duplicate records inside OneSignal.
Websites should use
setEmail upon the user providing the email for the first time and upon authentication into the site to make sure it is tied to the Push Player ID if this changes (like upon clearing cache).
Once you've imported your emails, go back to Email Quickstart to determine if you have any steps left.
Updated about a month ago