Data used for audience segmentation
The following data can target audiences by Segments:| Data | Description |
|---|---|
| First Session Time | The date and time you first used the app or visited the website (UTC). |
| Last Session Time | The date and time you most recently used the app or visited the website (UTC). |
| Session Count | The number of times you have used the app or visited the website. |
| Total Usage Duration | The total seconds you have interacted with the app, recorded whenever the app is in the foreground. |
| Device OS | The operating system of the device or browser. |
| Device Language | The language the device or browser reports. Can also be set with the SDK language methods. |
| Timezone | The most recent timezone of the device or browser, in IANA TZ format. |
| Country | The most recent country of the device or browser, in ISO 3166-2 format. |
| Push Permission Status | Whether the device or browser has push notifications enabled or disabled. |
| App Version | Mobile only — The app version reported by the most recent session. |
| Location | Mobile only — GPS coordinates of the device. Must be enabled and accepted by the user. |
Data not available for segmentation
The OneSignal SDK also collects the following data, which cannot be used in segments:| Data | Description |
|---|---|
| Application Identifier | Mobile only — The package name of your mobile application. |
| Cellular Carrier | Mobile only — The name of the cellular carrier used by the device. |
| Device Model | The model name of the device or browser. |
| IP Address | The IP address the device or browser is visiting from. Not stored on OneSignal servers for EU users. See handling IP address tracking. |
web_auth and web_p256 | Web push subscription tokens available for export from the API CSV export. |
| Push Tokens | Mobile app and web push tokens added to the device by FCM or APNs. |
Data you manually send to OneSignal
You can optionally send the following data to OneSignal. See Handling Personal Data for details.| Data | Description |
|---|---|
| The user’s email address, if you want to use OneSignal to deliver emails. | |
| Phone Number | The user’s phone number, if you want to use OneSignal to deliver SMS. |
| Tags | Any additional data about a user, stored as key-value pairs for segmentation and personalization. |
| Custom Events | Any additional data about a user, stored as key-value pairs for segmentation and personalization. |
Web SDK browser storage
Identifiers, purpose, and type of browser storage used by the Web SDK:| Identifier Name | Purpose | Type |
|---|---|---|
ONE_SIGNAL_SDK_DB | Storing user preferences in connection with notification permission status. | IndexedDB dictionary, on customer’s domain. |
os_pageViews,isOptedOut,isPushNotificationsEnabled | Prompting and subscription tracking. | Local Storage |
onesignal-pageview-count,ONESIGNAL_HTTP_PROMPT_SHOWN | Prompting. | Session Storage |
FAQ
Can I disable all automatic data collection?
Yes for some data. You can customize which data the SDK collects and manage user consent through the Handling Personal Data guide, which covers disabling location sharing, IP address collection, and more.Does OneSignal store IP addresses for EU users?
No. OneSignal does not store IP addresses on its servers for users located in the EU. See handling IP address tracking for configuration details.What browser storage does the Web SDK use?
The Web SDK uses IndexedDB, Local Storage, and Session Storage to manage notification permission status, prompting, and subscription tracking. See the Web SDK browser storage section above for the full list of identifiers.Handling personal data
Manage user consent and customize which data the OneSignal SDK collects.
Exporting data
Export user and device data from the OneSignal dashboard or API.