Iterable

Requirements

You must have the Developer or Admin role to set up a connector. If your organization uses custom roles, your role needs the Create Connectors permission. You also need access to create API keys in Iterable.

This article shows you how to connect EmailShepherd to Iterable, so you can export emails to Iterable as email templates.

You set up the connector once for each workspace. After that, anyone who can export emails can send them to Iterable without copying any code.

Get your Iterable API key

1. Sign in to Iterable.

2. Navigate to Integrations > API Keys.

   

3. Click New API Key.

4. Enter a name for the key, such as EmailShepherd.

5. In API key type, select Server-side.

   

6. Click Create.

7. Copy the API key and keep it somewhere safe until you’ve set up the connector.

You also need to know whether your Iterable project is in the US or EU data center.

Set up the connector in EmailShepherd

1. In the sidebar, click Connectors.
2. On the Export Connectors tab, click Add connector.
3. In Connector Name, enter a name, such as Iterable.
4. In Choose Integration, select Iterable.
5. In Data Center, select US Data Center or EU Data Center.
6. In API Key, paste the API key you created.
7. In Dynamic Content Profile, choose a dynamic content profile to use every time you export to Iterable. To choose one each time you export instead, leave it as None.
8. Click Create Connector.

Set up personalization for Iterable

Iterable uses Handlebars for personalization and dynamic content, such as {{firstName}}.

To export your personalization tags and conditionals in Iterable’s syntax, set them up in a dynamic content profile for Iterable, then choose it in the connector or when you export.

Export an email to Iterable

See How to export an email to your ESP.

Each locale is exported as a separate email template in Iterable, including the subject line, preheader and a plain-text version.

Caution

If a template with the same name already exists in Iterable, it will be overwritten.