> For the complete documentation index, see [llms.txt](https://docs.dinmo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dinmo.io/integrations/destination-platforms/iterable/send-events.md).

# Send events

## Overview

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 you start

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 event activation

1. Create an activation from an event model or segment.
2. Select your Iterable destination.
3. Select the **Send events** service.
4. Configure the event fields and scheduling.
5. Preview the data, then save and run the activation.

## Configure event fields

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.

## Schedule the activation

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.

## Use events in Iterable

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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dinmo.io/integrations/destination-platforms/iterable/send-events.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.