Event

Iterable makes consumer growth marketing and user engagement simple. With Iterable, marketers send the right message, to the right device, at the right time.

Iterable is a multi-channel growth marketing and user engagement platform that powers marketing, transactional, and lifecycle campaigns on email, web and mobile. Iterable requires your application to be collecting email addresses. This can be done by calling the setUserIdentity SDK method.

In order to support Iterable’s features such as deeplinking, push notifications, in-app notifications, and more, you must also include the Iterable Kit as part of your mParticle SDK installation. See Iterable Kit Integration for the Kit’s full feature list and installation instructions.

The Iterable integration supports Android, iOS and Web data. All event data is forwarded server-side, even if the Iterable Kit is installed.

Data Processing Notes

Iterable will not accept data more than 24 hours old.

Prerequisites

In order to forward events to Iterable, you must have an account with Iterable. You can sign into your Iterable account at https://app.iterable.com/login/

Create a Mobile API Key

Create a dedicated Mobile (client-side) API key for the Iterable Event integration:

1. In Iterable, navigate to Integrations > API Keys.
2. Click New API Key.
3. Provide a descriptive name such as mparticle-event-integration.
4. For the API key type, select Mobile (client-side).
5. Click Create.
6. Save the value of the key created. You will not be able to view it again. This value is needed to configure the Iterable Event Integration in mParticle.

Create Push Integrations

If you will be sending push registration events, you will need to provide the Iterable Push Integration names as part of the mParticle configuration. This can be done from Iterable:

• Setting up iOS Push Notifications
• Setting up Android Push Notifications

User Identities

mParticle will forward the following identifiers to Iterable where available:

• Email
• Customer ID
• Apple Vendor ID (IDFV)
• Google Advertising ID (GAID)
• Android ID
• mParticle ID

User Attributes

The Iterable integration will automatically map the following mParticle user attributes to corresponding Iterable user attributes:

Events

Supported Event Types

The Iterable integration supports the following event types:

• Custom Event
• Product Action
• Push Subscription
• Push Message Receipt
• Push Message Open
• User Identity Change

Tracking Commerce Events

Iterable will map mParticle purchase events to Iterable’s track purchase api call.

An add to cart event is mapped to Iterable’s updateCart commerce event. Iterable does not aggregate partial cart updates. As a result, each outgoing add to cart event from mParticle overwrites a user’s cart contents, so the cart contents in Iterable will only reflect the most recent add to cart event’s product(s).

Subscription Preferences

You can map a custom event to Iterable’s Update User Subscriptions api call. See the Platform Guide for general help with Custom Mappings. The ‘Update Subscriptions’ event takes the following attributes, all optional.

Iterable Kit Integration

Iterable’s client-side mParticle Kit enables the following features:

• User registration with email, Customer ID or MPID
• Push notifications
• Rich push notifications (media and action buttons)
• Client-side event tracking
• Deeplinking
• In-app messages
• Mobile Inbox

The Kit automatically handles user registration, push notifications, basic in-app messaging, and deeplinking by mapping mParticle’s APIs to analogous Iterable APIs. To learn more about these API mappings, you can review the source code:

• iOS
• Android

Adding the Kit to Your App

iOS

To install the Iterable Kit for iOS:

• For CocoaPods, add the following dependency to your Podfile:

# Sample Podfile

pod 'mParticle-Iterable', '~> 8.1.0'

• For Carthage, add the following dependency to your Cartfile:

# Sample Cartfile

github "Iterable/mparticle-apple-integration-iterable" ~> 8.0.2

Android

To install the Iterable Kit for Android, add the Kit dependency to your build.gradle file:

// Sample build.gradle

dependencies {
    compile 'com.mparticle:android-iterable-kit:5.14.+'
}

To learn more about mParticle Kits and how to incorporate them when setting up mParticle’s SDK, please review the mParticle Kit documentation:

• iOS
• Android

Push Notifications

If your app includes the Iterable mParticle Kit, mParticle passes Iterable push notifications to the Kit for display. However, for this to work, you must first set up a mobile app and push integration (with associated push credentials) in Iterable.

See mParticle’s Push Notification documentation for more details:

• iOS
• Android

Additional setup:

• For iOS, pass UNUserNotificationCenterDelegate calls to mParticle
• For Android, add mParticle’s InstanceIdService, MPReceiver, MPService to AndroidManifest.xml

Rich Push Notifications

For rich push notification support on iOS, you need to set up a Notification Service Extension. Please refer to the Iterable support documentation on Advanced iOS Push Notifications.

On Android, rich push notifications are automatically supported with the Iterable Kit installed.

In-App Notifications

In-app notifications are handled automatically by the bundled Iterable SDK. For more details and customization options, please refer to the Iterable documentation:

• In-App Messages on iOS
• In-App Messages on Android

Additional Configuration

To handle deeplinks and custom actions from push notifications and in-app messages, you may need to define a urlDelegate (on iOS) or a urlHandler (on Android) on the IterableConfig object.

Whenever you need to pass custom configuration for the Iterable SDK, use the Kit API:

iOS

    let config = IterableConfig()
    config.urlDelegate = self
    MPKitIterable.setCustomConfig(config)

Android

    IterableConfig.Builder configBuilder = new IterableConfig.Builder()
        .setUrlHandler(this);
    IterableKit.setCustomConfig(configBuilder.build());

Configuration Settings

Connection Settings