Articles in this section

Overview of Iterable's iOS and Android SDKs

Iterable SDK

Iterable's iOS and Android mobile SDKs help you to:

Push Notification Send and track push notifications

  • The Iterable SDK will automatically track push notification sends, opens, and bounces
  • Automatically track device uninstalls
  • Maintain the most up-to-date device tokens

In App Send and track in-app messages

  • Reduce load on your system by sending a silent push to the device to efficiently pull in-apps to the device
  • Store in-apps on the device for faster load time
  • Use a mobile inbox

Save Time Save implementation time

  • Provide error handling to ensure accuracy
  • Minimize the amount of code needed to deploy your mobile app with Iterable
  • Provide tested and proven code for new Apple / Android OS updates
  • Easily update user profile and event data

Tracking Automatically track and attribute engagement events

  • Update user profile and event data for enriched triggered campaigns
  • Automatically attribute to conversion events to specific campaigns
  • Help measure effectiveness of your campaigns

NOTES

Integrating the Iterable SDK will save your team time and effort. However, it is possible to connect your mobile app to Iterable without using the SDK.

Without the Iterable SDK

Without the Iterable SDK you will lose some benefits of the platform and it will require significantly more effort, especially around:

  • Push action buttons
  • In-app message link tracking
  • Mobile Inbox

Data collected by Iterable's Mobile SDKs

The Iterable mobile SDKs can receive any user profile data (via merge parameters in templates or link UTM parameters) — all user profile data should be considered accessible to the SDKs.

Device-level data collected by the SDKs:

  • Device brand (example: Google)
  • Device manufacturer (example: Samsung)
  • Device system name (example: Toro)
  • Device system version (example: 4.0.4)
  • Device model (example: Galaxy Note)
  • Device SDK/API version (example: API level 15)
  • Device ID (example: random UUID deviceId)
  • Device app package name (example: com.verycoolapp)
  • Device app version (example: appVersion 1.2)
  • Device app build (example: appBuild 1)
  • Device Iterable SDK version (example: 3.4.0)

For a list of mobile events that the SDKs can access, see:

NOTES

  • Personally identifying user information is stored within encrypted shared preferences in Android and in iOS keychain on Apple devices.
  • In-app HTML is stored in the file system sandbox dedicated for the app.
  • Any data injected by the app from other sources should be considered visible to the Iterable SDKs.
  • Iterable's mobile SDKs do not track device IPs or Google Ad IDs.

All of Iterable's mobile SDKs are open-source, and can be viewed here:

iOS iOS Next Steps

Android Android Next Steps

Related articles