Data Collected by the OneSignal SDK
List of data collected by OneSignal SDK
The following are data fields that the OneSignal SDK collects automatically, manually, and/or through user permission.
These do not need to be sent via Data Tags. To see a list of recommended tags to send OneSignal for use in Segments, see Add User Data Tags.
To customize which data is collected and how to manage user consent for data collection, please read our guide on Handling Personal Data.
Most data can be exported from the Dashboard or API.
Data that can be used to target audiences by Segments:
|First Session Time||The date & time the user first used the app / visited the website.|
|Last Session Time||The date & time the user most recently used the app / visited the website.|
|Session Count||The number of times the user has used the app / visited the website.|
|Total Usage Duration||MOBILE - The number of seconds the user has ever interacted with the app, as recorded whenever the app is in the foreground.|
|Device OS||The operating system of the device / browser.|
|Device Rooted||ANDROID - Whether the user has a rooted device.|
iOS - Whether the user has a jailbroken device.
|Device Language||The language the device / browser reports.|
|Time Zone||The most recent time zone the device / browser was in.|
|Country||The most recent country the device / browser was in (ISO 3166-2 format)|
|Push Status||Whether the device / browser has push notifications enabled or disabled|
|App Version||MOBILE - The version of the app the most recent session reported the user running.|
|In App Purchases||MOBILE - Consumable Purchases made by the user in the app while our SDK was active.|
The following data the OneSignal SDK collects that is not able to be segmented:
|Google Advertising ID and Apple's IDFA & IDFV||Update - Not collected in OneSignal SDK Major Release Versions 4.0+ Android and 3.0+ iOS.|
MOBILE - The Google Ad Id and Apple IFV are used for device matching. See OneSignal Player ID for more details.
|Your Application Identifier||MOBILE - The package name of your mobile application.|
|Cellular Carrier||MOBILE - The name of the cellular carrier used by the device.|
|Device Model||The model name of the device / browser.|
|IP Address||The IP address the device / browser is visiting from. See handing IP Address Tracking for more details.|
|web_auth and web_p256||Web Push Subscription Tokens available for export from our API CSV export.|
|Push Tokens||Mobile App and Web Push Tokens added to the device by FCM or APNs.|
Data OneSignal Automatically Collects that can be disabled client side
The following data the OneSignal SDK collects if your app asks for and receives permission from users:
|Location||MOBILE - GPS coordinates of the device. Location tracking must be turned on and accepted by the user. Sending location to OneSignal can be disabled.|
Data Manually Sent to OneSignal
The following data you may manually send to OneSignal. See Handling Personal Data for more details.
|Our SDKs support sending us the user's email address if you wish to use OneSignal to deliver emails to users.|
|Tags||You can send any additional data to us about a user as a tag.|
Web SDK Browser Storage
The following are the type, purpose and lifetime of each cookie (create a new row for each):
|Identifier Name||Primary Purpose||Other Purpose||Type||Lifetime of ID|
|__cfduid||Used by Cloudflare for maximizing network resources, managing traffic and protect from malicious traffic||Details: https://support.cloudflare.com/hc/en-us/articles/200170156-Understanding-the-Cloudflare-Cookies||Cookie|
|ONE_SIGNAL_SDK_DB||Storing user preferences in connection with notification permission status.||N/A||IndexedDB dictionary, on customer’s domain.||Until cleared|
|Prompting and subscription tracking||N/A||Local Storage|
Updated about 2 years ago