Update to User Model

Update the OneSignal SDK to v5+ to start utilizing our User Model APIs.

📘

Check out the new version of our documentation (V11.6)

The documentation you are currently viewing covers an older version of OneSignal that utilises our device-centric SDKs and only contains SDK reference guides. To see a full and up-to-date version of our documentation that outlines our new user-centric approach, please click here.

About the User Model

The new User Model enables you to create personalized engagement journeys for individual users rather than targeting users based on the channels to which they subscribe. This shift from channel-based to individualized targeting enables you to communicate more effectively and precisely with users through their applications, resulting in increased customer satisfaction and engagement. The User Model helps you optimize your strategies and improve your overall customer experience by providing greater flexibility and precision in customer engagement.

With the shift to a user-centric approach, there are many additional benefits. We are now syncing properties (more on that below) from subscriptions up to a user level, allowing you to leverage channel-specific data at an individual level from a messaging and segment-building standpoint.

Using the device-centric model

For now, you can continue to use our older SDKs that run on our device centric model, though we strongly advise you to migrate to the user model as soon as possible in order to take advantage of our latest features and releases, many of which are not supported properly in the device-centric model.

The device-centric model is planned to be deprecated in 2025, and we will warn anyone who is still utilizing our older SDKs about this deprecation when an official deprecation date has been announced.

Migration

To migrate to the user model, please see our User Model Migration Guide in our user model documentation.