Device data

Mobile (iOS / Android)

  • Installation ID

  • Advertising ID*

  • Identifier for Vendor (IDFV), on iOS.

  • 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)

  • Transaction tracked

  • Device's brand*

  • Device's model*

  • Mobile carrier*: Batch collects the MNC/MCC codes and deducts the carrier name based on these IDs.

  • Locale (language and region)

  • Device time zone

  • Country: Batch deducts the country based on the IP address. If the IP address cannot be used, Batch will use the country set in the device settings.

  • City: Batch uses IP geolocation to find the city of your users. This feature works when the user is on a Wi-Fi network, not on a cellular network.

* The collection of this data can be deactivated: iOS / Android.

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 install.

  • List of the campaigns that targeted the install and clicked by the user.

  • Smart Segment

  • Send date of the most recent campaign that targeted the install.

  • Number of push sent to the install, used for frequency capping limit.

Did this answer your question?