User Model
Learn how to migrate from OneSignal’s device-centric model to the new user-centric APIs and SDKs for more personalized and precise customer engagement.
If you’re migrating from OneSignal’s device-centric model to our new user-centric APIs and SDKs, we strongly recommend thorough testing before deploying changes to production. For complete instructions, refer to our User Model Migration Guide.
Multi-channel messaging
Overview
The User Model empowers you to build personalized engagement journeys by targeting individual users instead of their subscribed messaging channels. This change shifts OneSignal’s paradigm from a channel-based approach to a user-centric model, improving communication effectiveness and customer satisfaction.
By syncing subscription properties up to the user level, you gain the ability to access and utilize channel-specific data (e.g., push, email, SMS) within a holistic user profile—enabling more precise messaging, segmentation, and analysis.
Migrating to the user model
To begin your migration, please follow this step-by-step guide:
User Model Migration Guide
If you use any Integrations with OneSignal, check whether they support the User Model before migrating production apps:
User Model Supported Integrations
Do not migrate if your integration is unsupported.
Users
A User represents an individual who may subscribe to one or more messaging channels for your app. This user entity replaces the previous concept of Players and becomes the foundation of your engagement strategy.
Each User includes:
- Alias IDs – e.g., external identifiers from your app or third-party services
- Subscriptions – representing the channels (Push, Email, SMS, In-App) the user is opted into
More details here: Users
Users
A User represents an individual who may subscribe to one or more messaging channels for your app. This user entity replaces the previous concept of Players and becomes the foundation of your engagement strategy.
Each User includes:
- Alias IDs – e.g., external identifiers from your app or third-party services
- Subscriptions – representing the channels (Push, Email, SMS, In-App) the user is opted into
More details here: Users
Subscriptions
A Subscription is a messaging channel that a user has opted into. Even if a user unsubscribes, the subscription record is retained and marked as unsubscribed, preserving history.
Supported channels include:
- Mobile & Web Push Notifications
- SMS
- In-App Messages
For more, visit: Subscriptions
Aliases
Aliases are custom identifiers used to link different user representations across tools and platforms (e.g., Mixpanel ID, Facebook ID).
Aliases allow OneSignal to unify subscriptions under a single user profile.
More details: Aliases & External ID
These enable key operations like login and identity merging:
onesignal_id: Auto-generated and managed by OneSignalexternal_id: (formerlyexternal_user_id) Provided by the developer using theloginmethod
These are additional user identifiers often used in integrations (e.g., marketing or analytics platforms).
Limitations of the user model release
At this time, some OneSignal features are not supported with the User Model:
- Certain Integrations
Check the current list of supported integrations here:
User Model Supported Integrations
User Model
Learn how to migrate from OneSignal’s device-centric model to the new user-centric APIs and SDKs for more personalized and precise customer engagement.
If you’re migrating from OneSignal’s device-centric model to our new user-centric APIs and SDKs, we strongly recommend thorough testing before deploying changes to production. For complete instructions, refer to our User Model Migration Guide.
Multi-channel messaging
Overview
The User Model empowers you to build personalized engagement journeys by targeting individual users instead of their subscribed messaging channels. This change shifts OneSignal’s paradigm from a channel-based approach to a user-centric model, improving communication effectiveness and customer satisfaction.
By syncing subscription properties up to the user level, you gain the ability to access and utilize channel-specific data (e.g., push, email, SMS) within a holistic user profile—enabling more precise messaging, segmentation, and analysis.
Migrating to the user model
To begin your migration, please follow this step-by-step guide:
User Model Migration Guide
If you use any Integrations with OneSignal, check whether they support the User Model before migrating production apps:
User Model Supported Integrations
Do not migrate if your integration is unsupported.
Users
A User represents an individual who may subscribe to one or more messaging channels for your app. This user entity replaces the previous concept of Players and becomes the foundation of your engagement strategy.
Each User includes:
- Alias IDs – e.g., external identifiers from your app or third-party services
- Subscriptions – representing the channels (Push, Email, SMS, In-App) the user is opted into
More details here: Users
Users
A User represents an individual who may subscribe to one or more messaging channels for your app. This user entity replaces the previous concept of Players and becomes the foundation of your engagement strategy.
Each User includes:
- Alias IDs – e.g., external identifiers from your app or third-party services
- Subscriptions – representing the channels (Push, Email, SMS, In-App) the user is opted into
More details here: Users
Subscriptions
A Subscription is a messaging channel that a user has opted into. Even if a user unsubscribes, the subscription record is retained and marked as unsubscribed, preserving history.
Supported channels include:
- Mobile & Web Push Notifications
- SMS
- In-App Messages
For more, visit: Subscriptions
Aliases
Aliases are custom identifiers used to link different user representations across tools and platforms (e.g., Mixpanel ID, Facebook ID).
Aliases allow OneSignal to unify subscriptions under a single user profile.
More details: Aliases & External ID
These enable key operations like login and identity merging:
onesignal_id: Auto-generated and managed by OneSignalexternal_id: (formerlyexternal_user_id) Provided by the developer using theloginmethod
These are additional user identifiers often used in integrations (e.g., marketing or analytics platforms).
Limitations of the user model release
At this time, some OneSignal features are not supported with the User Model:
- Certain Integrations
Check the current list of supported integrations here:
User Model Supported Integrations