​

Overview

A subscription represents a specific channel a user can receive messages through—such as an email address, phone number, or device. OneSignal supports four types of subscriptions:

• Email – for sending email messages
• SMS – for sending text messages
• Web Push – for push notifications in web browsers
• Mobile – for push, in-app messages, and Live Activities on mobile devices

Each user can have multiple subscriptions. For example, a user may have:

• Web Push from subscribing on your site
• Mobile (Android) after installing your app
• Email after entering their address
• Later, if they install your app on iOS and provide a phone number, they’ll have Mobile (iOS) and SMS, bringing the total to five subscriptions.

​

Subscription properties

Each subscription has the following properties:

Property	Description
Channel	Type of Subscription: Email, SMS, or Push. Push can be Mobile (iOS, Android, etc.) or Web. Only Mobile Push subscriptions support in-app messages.
Subscription Status	Indicates if the subscription can receive messages. See subscription status for more details.
Last Session	Date/time of the last session with OneSignal SDK. For Email/SMS, it’s based on the most recent Push subscription.
Usage Duration	Total time (in seconds) the app or site was active with OneSignal SDK. Only tracked when session exceeds 60s.
Sessions	Count of how many times the app/site was opened. A new session starts after 30+ seconds of inactivity.
First Session	Timestamp when the first Subscription for the User was created.
IP Address	Network location when using OneSignal SDKs. Not collected in the EU. See Handling Personal Data.
Subscription ID	UUID representing the specific Subscription. Required for API messaging or updates.
OneSignal ID	UUID representing the User. See Users.
External ID	Your custom user ID. Helps link multiple subscriptions to the same user.
Email	Only set for Email subscriptions.
Phone Number	Only set for SMS subscriptions. Must be in E.164 format.
App Version	From SDK: Android versionCode, iOS CFBundleShortVersionString.
SDK Version	Version of the OneSignal SDK used. See GitHub > SDKs (select your SDK) > Releases.
Timezone ID	From the device at time of last interaction.
Country	Derived from IP address.
Location Point	Latitude/longitude if location tracking is enabled. See Location-triggered notifications.
Language Code	From the device at time of subscription creation. See Multi-language messaging.
Tags	Custom key-value metadata. See Tags.
Push Token	Platform token used for push delivery (e.g., APNS or FCM). Only for Push Subscriptions. - iOS Push APNS token format: 64 characters, hexadecimal characters only (0-9,a-f). - Android Push FCM token format: Typically 163 characters, alphanumeric characters, may contain hyphens, colons and underscore.
Rooted	Indicates if the Android device is rooted (jailbroken).

​

Subscription statuses

Generally, subscriptions can either receive messages (Subscribed) or cannot receive messages (Unsubscribed). However, there are some exceptions:

Mobile subscriptions

• Subscribed: The user has granted permission to receive push notifications.
  • If you have iOS Provisional push enabled, then all iOS mobile subscriptions are Subscribed until disabled by the user.
• Unsubscribed: The subscription cannot receive push notifications but can receive in-app messages.
  • See Handling uninstalls, unsubscribes, & invalid push tokens for more details.
• Never Subscribed – User never granted permission (unsubscribed).

Web subscriptions

• Subscribed: The user has granted permission to receive push notifications.
• Unsubscribed: The subscription cannot receive push notifications.
  • See Handling unsubscribes & invalid push tokens for more details.

Email subscriptions

• Subscribed: The user should have provided consent to receive email messages and the email address is valid.
• Unsubscribed: The user opted-out of receiving emails but can be overridden if needed.
• See Email subscriptions for more details.

SMS subscriptions

• Subscribed: The user should have provided consent to receive SMS messages and the phone number is valid.
• Unsubscribed: The user opted-out of receiving SMS messages.
• See SMS subscriptions for more details.

---

​

notification_types

Indicates the subscription’s ability to receive messages, including reasons for failures. Automatically updated via our frontend SDKs or manually via the API. Viewable via the View User API or Export CSV.

Notification Types definitions.

---

​

Mobile subscriptions

Mobile subscriptions represent iOS, Android, Huawei, or Amazon devices and support:

• Push notifications
• In-app messages
• Live Activities

They’re automatically created when a user installs and opens your app with the OneSignal SDK.

​

Updating mobile subscriptions

Use the SDK to:

• Prompt for push permissions and observe permission/subscription changes
• Login users to associate External ID and Aliases
• Add Tags
• Set Language

​

Handling uninstalls, unsubscribes, & invalid push tokens

Mobile subscriptions stop receiving push notifications if the user:

• Uninstalls the app
• Disables push in device settings and never reopens the app
• Push token expires

In these cases, the subscription status will be set to Unsubscribed when sending push notifications. See below When do push subscription statuses update? for more details.

• If the user re-installs the app on the same device or new device, a new subscription will be created and they need to re-subscribe to receive messages.
• If the user re-enables push in the device settings, the subscription status will be set to Subscribed and a push token will be updated when they open the app.
• If the push token expires, the subscription status and new push token will update when the user opens the app on the same device.

Track changes via:

• Event Streams - detect unsubscribes when sending push
• Push reports - detect unsubscribes when sending push
• Use the SDK’s subscription change listener - detect unsubscribes when user disables push in device settings then opens the app

---

​

Web push subscriptions

Web push subscriptions are tied to a specific device, browser, and browser profile. A user who subscribes on Chrome desktop will not receive push on Chrome mobile unless they also subscribe from that mobile device—creating a separate web push subscription.

New web push subscriptions are created in these scenarios:

• User subscribes via your website by clicking “Allow” on the browser’s system-level permission prompt. This generates a unique push token and Subscription ID.
• User clears browser data (history, cache, cookies, local storage) and revisits your site. This results in a new unique Subscription ID being created.

​

Updating web push subscriptions

Use the SDK to:

• Prompt for permissions and observe changes
• Login users
• Add Tags
• Set Language

​

Handling unsubscribes & invalid push tokens

Web push subscriptions stop receiving push notifications if the user:

• Clears browser data (history, cache, cookies, local storage)
• Disables push in the browser system settings
• Push token expires

In these cases, the subscription status will be set to Unsubscribed when sending push notifications. See below When do push subscription statuses update? for more details.

• If the user returns to the site after clearing browser data, a new subscription will be created and they will be automatically re-subscribed to receive messages if you have auto-resubscribe enabled.
• If the user re-enables push in the browser settings, the subscription status will be set to Subscribed when they return to the site.
• If the push token expires, the subscription status and new push token will update when the user returns to the site.

Track changes via:

• Event Streams - detect unsubscribes when sending push
• Push reports - detect unsubscribes when sending push
• Use the SDK’s subscription change listener - detect unsubscribes when user disables push then returns to the site

---

​

Email subscriptions

Email subscriptions are based on the email address and used only for email delivery.

Created via:

1. SDK addEmail or email prompt
2. Create user or Create email API
3. CSV Importer

​

Manage email subscriptions

• Use the dashboard, API, or Unsubscribe links
• Resubscribe via SDK/API without changing Subscription ID
• If a user opts-out of receiving emails, you can keep them as unsubscribed but send important emails by sending to unsubscribed emails.

---

​

SMS subscriptions

SMS subscriptions are tied to E.164 formatted phone numbers.

Created via:

1. SDK addSms or SMS prompt
2. Create user or Create SMS API
3. CSV Importer

​

Manage SMS subscriptions

• User replies with “STOP”
• Update Subscription via API

---

​

Importing or migrating subscriptions

Import push tokens, email addresses, and phone numbers from another provider using:

• Create user API
• Create subscription API

---

​

Delete subscriptions

Subscriptions can be deleted for:

• Data privacy
• Cleaning up inactive records

See Delete users for details.

---

​

FAQ

​

When do push subscription statuses update?

Push subscription statuses are updated:

1. When the user opens the app, the OneSignal SDK will check if the push token is valid and if notification permissions are granted, then update the subscription status accordingly.

• You can capture this event with our SDK Subscription Observer methods and send to your Database.

2. After sending 2+ notifications to the subscription. Use Event Streams to detect unsubscribes when sending messages.

Example:

• Message 1: Delivered. User receives on device, then user unsubscribes in device settings.
• Message 2: Delivered (but device doesn’t receive).
• Message 3: Fails (marked unsubscribed)
• Message 4: Not sent to the subscription.

​

If a user turns off notifications in their device settings and never opens the app again, what happens?

When users turn off notifications in the device settings they can no longer receive push notifications on that device.

They will be marked as unsubscribed after sending notifications to the device. See When do push subscription statuses update? for more details.

---