Iterable (Actions) Destination
Iterable is a cross-channel marketing platform that powers unified customer experiences and empowers you to create, optimize and measure every interaction across the entire customer journey.
This destination is maintained by Iterable. For any issues with the destination, contact the Iterable Support team.
Success!
This page is about the Actions-framework Iterable Segment destination. There's also a page about the non-Actions Iterable destination. Both of these destinations receive data from Segment.
Iterable (Actions) provides the following benefit over Iterable Classic:
Transparent data mapping: The Classic Iterable destination receives data from Segment and converts Segment events to Iterable's format using hard coded mappings that are unable to be adjusted. The Iterable (Actions) destination allows clients to fully define their own mappings of Segment events, ensuring they receive data structured specifically for their needs.
For information about the differences between the Iterable (Actions) and Iterable Classic destinations, see the Important differences from the classic Iterable destination
Follow these steps to connect the Iterable (Actions) destination to your Segment sources:
- Access the Segment web app and click on Catalog.
- In the Catalog, use the search function to find "Iterable". Select the Iterable (Actions) destination from the results, and choose which of your sources to connect the destination to.
- From the Segment web app, navigate to Connections > Catalog > Destinations.
- Click the Destination Actions category item in the left navigation.
- Search for Iterable (Actions) and select it.
- Click Configure Iterable (Actions).
- Select an existing Source to connect to Iterable (Actions).
- Complete the Destination Settings as listed below.
To obtain the API Key, go to the Iterable app and naviate to Integrations > API Keys. Create a new API Key with the 'Server-Side' type.
Optional
The location where your Iterable data is hosted.
Iterable (Actions) has the following presets
| Preset Name | Trigger | Default Action |
|---|---|---|
| Order Completed Calls | Event type = "track" and event = "Order Completed" | Track Purchase |
| Update Cart Calls | Event type = "track" and event = "Cart Updated" | Cart Updates |
| Track Calls | Event type = "track" and event != "Order Completed" and event != "Cart Updated" | Custom Event |
| Identify Calls | Event type = "identify" | Upsert User |
Build your own Mappings. Combine supported triggers with the following Iterable-supported actions:
Mapping limits per destination
Track a custom event to a user profile
Custom Event is a Cloud action. The default Trigger is type = "track" and event != "Order Completed" and event != "Cart Updated"
Optional
An email address that identifies a user profile in Iterable.
Optional
A user ID that identifies a user profile in Iterable.
Name of the event
Optional
Additional event properties.
Optional
A unique ID. If an event exists with that id, the event will be updated
Optional
Time the event took place.
Optional
Iterable campaign the event can be attributed to.
Optional
Iterable template the event can be attributed to.
Optional
When enabled, Segment will send data to Iterable in batches of up to 1001
Updates the shoppingCartItems field on the user profile.
Cart Updates is a Cloud action. The default Trigger is type = "track" and event == "Cart Updated"
Updates user data or adds a user if none exists
Individual items in the cart. Each item must contain id, name, price, and quantity. Extra values are added to dataFields.
Tracks a purchase to Iterable
Track Purchase is a Cloud action. The default Trigger is type = "track" and event == "Order Completed"
Optional
Similar to Event ID in custom events. Iterable recommends mapping order_id or messageId. If a purchase exists with that id, the purchase will be updated. If none is specified, a new id will automatically be generated by Iterable
Updates user data or adds a user if none exists
Optional
Additional event properties.
Individual items in the cart. Each item must contain id, name, price, and quantity. Extra values are added to dataFields.
Total order amount.
Optional
Time the event took place.
Optional
Iterable campaign the event can be attributed to.
Optional
Iterable template the event can be attributed to.
Creates or updates a user
Upsert User is a Cloud action. The default Trigger is type = "identify"
Optional
An email address that identifies a user profile in Iterable.
Optional
A user ID that identifies a user profile in Iterable.
Optional
Data to store on the user profile.
Optional
User phone number. Must be a valid phone number including country code. e.g. +14158675309
Optional
If you'd like to merge (rather than overwrite) a user profile's top-level objects with the values provided for them in the request body, set mergeNestedObjects to true.
Optional
When enabled, Segment will send data to Iterable in batches of up to 1001
Since the release of Iterable's Classic Segment destination, Iterable has expanded its support for multiple project types. To determine the appropriate identifier for your project type, please refer to the list of available project types and their respective identifiers found in Iterable's documentation: Project Types and Unique Identifiers.
The method by which you identify users depends on the project type you use:
In email-based projects, it is necessary to include the email to successfully create a user in Iterable. Once both the email and userId have been set in Iterable, the userId can be utilized for any future user updates.
For userID-based projects, a unique userId is required for creating a user in Iterable. While it is optional to add an email to a userID-based user profile, all subsequent user updates must be performed using the userId.
In hybrid projects, you have the flexibility to choose between using a unique email or a userId to create a user in Iterable.
In Iterable's previous classic destination, when making Identify calls, certain context fields were automatically mapped to user profiles. However, this behavior has been changed. Please note that the following context fields are no longer automatically mapped to Iterable user profiles during Identify calls:
- app
- device
- ip
- locale
- page
- timezone
To include these fields in user profiles, pass them as traits with Identify calls. This change offers more control and customization options for managing user data within Iterable.
Additionally, the integration has been updated to support explicit mappings for updating the phoneNumber user profile field, as well as support of the mergeNestedObject boolean field in user update calls.
In UserID and Hybrid projects, when a passed userId doesn't match an existing user, Iterable creates a new user automatically. In email-based projects, tracking a custom event for an unidentified user will not create a user profile.
To ensure proper user profile creation in email-based projects:
- Call the Identify method with both a
userIdand anemailto create a user profile. - After you create the user profile, proceed with tracking the custom event for that user.
If you follow this approach, you can guarantee the creation of user profiles and accurately track custom events within Iterable for email-based projects.
In the classic destination of Iterable, cart updates were associated with Segment's Product Added and Product Removed events. However, in the Action destination, there have been updates to the default mappings. Now, custom events titled Cart Updated are routed to Iterable's Update Cart API.