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:

DataDescription
First Session TimeThe date & time the user first used the app / visited the website.
Last Session TimeThe date & time the user most recently used the app / visited the website.
Session CountThe number of times the user has used the app / visited the website.
Total Usage DurationMOBILE - The number of seconds the user has ever interacted with the app, as recorded whenever the app is in the foreground.
Device OSThe operating system of the device / browser.
Device RootedANDROID - Whether the user has a rooted device.
iOS - Whether the user has a jailbroken device.
Device LanguageThe language the device / browser reports.
Time ZoneThe most recent time zone the device / browser was in.
CountryThe most recent country the device / browser was in (ISO 3166-2 format)
Push StatusWhether the device / browser has push notifications enabled or disabled
App VersionMOBILE - The version of the app the most recent session reported the user running.
In App PurchasesMOBILE - 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:

DataDescription
Google Advertising ID and Apple's IDFA & IDFVUpdate - 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 IdentifierMOBILE - The package name of your mobile application.
Cellular CarrierMOBILE - The name of the cellular carrier used by the device.
Device ModelThe model name of the device / browser.
IP AddressThe IP address the device / browser is visiting from. See handing IP Address Tracking for more details.
web_auth and web_p256Web Push Subscription Tokens available for export from our API CSV export.
Push TokensMobile 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:

DataDescription
LocationMOBILE - 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.

DataDescription
EmailOur SDKs support sending us the user's email address if you wish to use OneSignal to deliver emails to users.
TagsYou 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 NamePrimary PurposeOther PurposeTypeLifetime of ID
__cfduidUsed by Cloudflare for maximizing network resources, managing traffic and protect from malicious trafficDetails: https://support.cloudflare.com/hc/en-us/articles/200170156-Understanding-the-Cloudflare-CookiesCookie
ONE_SIGNAL_SDK_DBStoring user preferences in connection with notification permission status.N/AIndexedDB dictionary, on customer’s domain.Until cleared
os_pageViews,
isOptedOut,
isPushNotificationsEnabled
Prompting and subscription trackingN/ALocal Storage
onesignal-pageview-count,
ONESIGNAL_HTTP_PROMPT_SHOWN
PromptingN/ASession Storage

What’s Next