Device data

Mobile (iOS / Android)

Installation ID
API level of the SDK (on Android)
IP address (shared with Batch, but not stored on Batch side)
Bundle ID
OS version
App version
Batch SDK version

Push token
Push notifications opt-in status
MLVL (Mobile Landing Version)
Mobile carrier*: Batch collects the MNC/MCC codes and deducts the carrier name based on these IDs.
Locale (language and region)
Device time zone

💡 This list details the data collected by default by SDK V.2. If you are using an older version, we encourage you to update the SDK to the latest version (migration guide available here : iOS / Android).

If you have any questions about the default data collected by SDK V.1, feel free to reach out to us via Live Chat.

Web

Installation ID
IP address (shared with Batch, but not stored on Batch side)
Push token
Push notifications opt-in status
User-agent (web browser, OS, etc.)

Locale (language and region)
Country
Device time zone
City (see above for more details)
Batch SDK version

Batch does not set any cookies but relies on Local Storage.

App usage and campaigns data (App + Web)

First SDK start date
Last SDK start date
List of the campaigns that targeted the installation.
List of the campaigns that targeted the installation and clicked by the user.

Smart Segment
Send date of the most recent campaign that targeted the installation.
Number of push sent to the install, used for frequency capping limit.

This article belongs to Batch's FAQ. Need more help? Find insightful articles, documentation, case & market studies, guides, and even more in our website's Resources section on batch.com and our blog.

GDPR Compliance

What purpose is Batch SDK serving?

How does Batch register new installs and manage install data?

How does Batch manage data when your device is offline?

How can I migrate my website to Batch?