With the Iterable integration, everyone who signs up is created or updated as a user in Iterable, identified by their email address, and subscribed to the Iterable list you choose.
What you need
- An Iterable project that uses email as the user identifier, and a user with permission to manage API keys (usually an org admin or project admin).
- To know whether your Iterable project is in the US or the EU data center.
Step 1: Create an API key in Iterable
- In Iterable, go to Integrations > API Keys.
- Click New API Key.
- Name it, for example "Scratcher", and choose the type Standard (server-side).
- Click to create the key, and copy it. Iterable only shows the whole key once.
What the key is used for
A standard (server-side) key can do what Scratcher needs:
- read your lists and user fields, so you can choose them in the campaign;
- create and update users;
- subscribe users to lists.
Don't use a JavaScript, mobile or read-only key: they can't add users from a server.
Step 2: Connect Iterable to Scratcher
- In Scratcher, go to Settings > Integrations and click Iterable.
- Choose the data center (US or EU), and paste the API key.
- Click Install integration. Scratcher checks that it can read your lists.
Step 3: Turn it on in a campaign
- In the editor, go to Connect > Integrations > Iterable and click Activate.
- If you have connected more than one project, choose it under Select account.
- Under External list, choose the Iterable list. Only static lists can be chosen.
- Under Field mappings, click Add field mapping and match each Scratcher field to an Iterable user field, for example "Lead - First name" to firstName.
- Under Filter by permissions (optional), choose your marketing consent checkbox.
- Click Save, and then Test.
Field mapping
- The email address is always sent and identifies the user. You don't need to map it.
- The Destination field list shows the user fields in your project. If a field doesn't exist yet, create it in Iterable first, so it gets the right type.
- For phone numbers, use Format with + and country code, which Iterable expects for SMS.
Consent
Being on a list doesn't subscribe people to your message types by itself: Iterable uses its own subscription settings for that. Only send people who said yes, by choosing your marketing checkbox under Filter by permissions (optional). You can also map a consent's Accepted and Date fields to user fields, so you have proof of consent in Iterable.
What is sent and when
New sign-ups are sent within a minute or two, and the campaign's existing leads are sent when you activate it. When someone takes part again, the user is updated. Use the list as the start of a journey in Iterable to send a welcome message. Every delivery shows under Settings > Integrations > Delivery status.
Troubleshooting
- "All or some of the fields are invalid..." when installing: the key is wrong or not a standard key, or you chose the wrong data center.
- A field is rejected: the value doesn't fit the type of the user field in Iterable, for example text in a date field. Check the mapping.
- The list is missing: dynamic lists can't receive users. Create a static list in Iterable.