Integration using Iterable

This document serves as a guideline for developers on the Publisher backend, facilitating the integration of Zendrive webhook with Iterable.

Publishers have an account in Iterable which gives them the access to the required API keys.
The webhook sent by the Zendrive backend contains driver_id. This unique identifier should also uniquely identify the users in Iterable. (referred as userId in Iterable)
The user information like email and device information is added in Iterable which ensures that email and push notifications are being sent.
Publishers are required to create email/push notification templates in Iterable for all the different types of webhooks sent by Zendrive.
Publishers are required to associate these templates with a journey which triggers the notifications whenever a specific webhook is triggered.

Log in to Iterable to send the engagement communications based on the user's journey.
Add user and event data: There are two ways to populate the user and event data in Iterable. a. Send data from your backend server to Iterable using their API. For more information, see Iterable API. b. Configure any customer data platform like Segment to send data to Iterable.
To populate data using Segment: a. Invoke the identify function using one of Segment’s sources. Internally, Segment triggers Iterable’s update user endpoint, incorporating data for the specific user. b. Trigger the track function using one of Segment’s sources. Segment communicates with Iterable by calling the track API endpoint, sending event properties as the data fields within the request.
To configure email, set up email services in your account. For more information, see Iterable email support.
To configure push notifications, set up push notifications in your account. For more information, see iOS push notifications or Android push notifications.
To configure a campaign for email and push notifications. For more information, see Campaigns.
Set up a journey flow that configures how the users are communicated once the event is triggered for the particular user. For more information, see Journeys.