Skip to content

Connect Iterable

JustAI sends journey messages through your own Iterable project. JustAI decides what each person receives and prepares the message. Iterable sends it from your sender and reports the result back to JustAI. You connect each Iterable project once, then add a sending profile for each sender your journeys use.

Your dataCDP, warehouse, or backend
JustAIBuilds each person's message
IterableSends from your sending profile
Your customersReceive and engage
Sends, opens, and clicks return to JustAI through the system webhook
Your data source sends customer profiles and events to JustAI. JustAI asks Iterable to send each message and supplies the content. Iterable delivers the email from your sending profile. Sends, opens, and clicks return to JustAI through the system webhook.

An Iterable connection has four parts. You set up the first three once for each Iterable project. You repeat the fourth for each sender.

Part What it does Where you set it up
API key Lets JustAI create templates and campaigns, set up the system webhook, and trigger sends in your Iterable project. Create it in Iterable, then save it in JustAI.
Content data feed An Iterable data feed that points at JustAI. Iterable uses it to fetch each prepared message when it sends. A feed token that JustAI generates protects it. Create it in Iterable with the URL and feed token from JustAI.
System webhook An Iterable webhook that reports sends, skipped sends, bounces, opens, clicks, and unsubscribes to JustAI. Create it in Iterable with the endpoint from JustAI. JustAI then adds its own authentication header.
Sending profiles A sender that journeys send through, for email, SMS, or push. JustAI creates a campaign and a template in Iterable for each one. Create them in JustAI, then verify each one with a test message.

When a journey sends an email through Iterable:

  1. JustAI prepares the subject, preheader, and body for the person.
  2. JustAI triggers the sending profile’s campaign in Iterable for the person’s email address.
  3. Iterable fetches the prepared message from JustAI through the content data feed and sends it.
  4. Iterable reports the send and the person’s engagement to JustAI through the system webhook. The results appear in the journey’s analytics.
  • An Iterable project in Iterable’s US data center. JustAI works only with projects in the US data center, and the connection has no region setting. If your project is in Iterable’s EU data center, talk to your JustAI team before you start.
  • A project that identifies users by email. JustAI finds each recipient in Iterable by email address, so use an email-based or hybrid project. See Recipient identity.
  • An Iterable admin. Your Iterable admin does this setup and needs permission to manage API keys, data feeds, system webhooks, campaigns, and templates in the Iterable project.
  • JustAI access. You need a JustAI account in your organization. An organization admin must also add your company’s mailing address in Settings > Delivery before your first test email.
  • The right environment. Each connection belongs to one JustAI environment. Open the account menu at the bottom of the left sidebar. Under your name, it shows your organization and environment. If it is not the environment that will send, select Environment in the menu, then select Switch next to the environment that will send.

In JustAI, open the account menu at the bottom of the left sidebar and select Settings. Settings opens on Integrations, which lists every connection in the current environment. Select a connection to open its setup steps.

In Settings > Integrations, each Iterable connection shows one of two labels.

Label Meaning
Need Setup At least one connection step is unfinished: the API key, the content data feed ID and feed token, or the system webhook.
Configured The API key is saved, the content data feed ID is saved, a feed token exists, and JustAI has set up the system webhook.

The list label does not show whether the system webhook is enabled in Iterable. Open the connection and check its steps. Each finished step shows a check mark and a short summary, such as “Key saved”, Data feed #<id>, or Webhook #<id>. The Sending profiles step unlocks only when all three steps are finished.

Each connection holds one Iterable API key, so each connection belongs to one Iterable project. To use several projects, for example a production project and a test project, add a connection for each one.

  • Give each connection a unique Account name.
  • Connect each Iterable project to only one JustAI connection, in one environment. A second connection to the same project finds the first connection’s system webhook. When you select Set header on the second connection, it takes over that webhook, and the first connection stops receiving events.
  • To test in a non-production environment, connect a separate Iterable project to it.
  • Copy URLs only from the connection you are setting up. The content data feed URL and the system webhook endpoint are different for each connection and environment.
  • API key. You can replace the key at any time. After the connection has sending profiles, JustAI accepts only a key from the same Iterable project. See Rotate the API key.
  • Content data feed. After the connection has sending profiles, its feed ID can’t change. Keep JustAI content feed in place in Iterable. See Keep the content data feed in place.
  • Removal. You can’t remove a connection that has verified sending profiles.

Set up the connection by completing these pages in order. Each step on the connection unlocks the next.