Send events
Send behavioral events from DinMo to Iterable.
Last updated
⌘Ctrlk
Send behavioral events from DinMo to Iterable.
Use the Iterable events service to send behavioral events from DinMo to Iterable.
Events help you trigger Iterable workflows and personalize campaigns with current first-party behavior from your warehouse.
Before creating an event activation, make sure that:
An Iterable destination is configured in DinMo.
The Iterable API key has server-side access.
Your source model or segment contains one row per event.
You have an identifier that can link each event to an Iterable user.
Create an activation from an event model or segment.
Select your Iterable destination.
Select the Send events service.
Configure the event fields and scheduling.
Preview the data, then save and run the activation.
Map the identifier that Iterable uses to associate the event with an existing user. Depending on your Iterable configuration, this can be an email address, a phone number, or another user identifier.
Then define the event name and map the fields to include in the event payload.
Use event properties to send the context needed by your Iterable workflows. For example, a purchase event can include the order ID, amount, currency, product category, or store.
Choose how often DinMo should send new events to Iterable.
Use a schedule that matches the urgency of your use case. For example, use a frequent schedule for post-purchase journeys or cart-related events, and a less frequent schedule for reporting-oriented events.
Once events are available in Iterable, you can use them to:
Trigger journeys and campaigns.
Personalize messages with event properties.
Build audiences based on recent customer behavior.
Keep behavioral workflows connected to warehouse data.
Last updated