The Zapier + Iterable integration makes it easy to connect your Iterable account to the other apps you use. Here are some examples of what you can do with Zapier:
- Collect Unbounce landing page submissions and automate on-boarding emails
- Forward SurveyMonkey responses to Iterable
- Add new Delighted NPS Survey responses to your contacts in Iterable
- Add GoToWebinar signups to reminder and follow-up journeys in Iterable
- Add new Facebook Lead Ad submissions to Iterable Onboarding Journeys
Zapier is a service that lets you forward activity collected in one app (the trigger) to another app (the action). Each trigger/action combo is called a "Zap." You can chain multiple actions together so that in one Zap you can (for example):
- Capture an email from your blog via Gravity Forms.
- Enrich the data with Lead Score by Zapier or Clearbit.
- Filter non-work emails
- Add only contacts with a work email to Iterable
In this article
What actions does Zapier support?
- Create/update a user
- Update an existing user
- Track a custom event
- Track cart updates
- Track purchases
Connecting Zapier to Iterable
In Iterable, create a unique API Key to use with Zapier:
Navigate to Integrations > API Keys
Click Create New API Key.
Select a Server-side API key type.
Rename the API so that you can recognize it in the future:
Scroll to the right side of the table that lists all of your API keys.
Hover over the row associated with the new API key and click Edit.
In the table's left-most column, rename the API key.
On the right-hand side of the row, click Save.
Click Make a Zap.
Zapier connects to hundreds of apps; for the sake of this example we’ll be using Typeform. You can choose any Zap you like, but we recommend using one that contains an email field since Iterable’s action steps require an email.
For the action step, select Iterable and the action you would like to perform.
If you haven’t connected to your Iterable account already, Zapier will ask you to enter the API key you generated in step 1.
We recommend using sandbox projects for testing. Zapier allows you to integrate multiple Iterable projects in your Zapier account. Make sure to rename your account in Zapier in a way you can easily recognize. Each project will have a unique set of API keys.
For this example, use the Create a User option.
Configure your Zapier template by mapping fields captured in other apps to Iterable.
Once you’re ready to test the Zap, click Continue and send a test user to Iterable. Find the user by navigating to Audience > Contact Lookup and entering their email address or their user ID (the search box will reflect the necessary field).
Once you’ve activated the Zap, Iterable will automatically capture contacts that have submitted the Typeform survey. If they’re an existing contact, their contact record will be updated with any new information in the survey submission. Iterable will use the email address to determine if the contact is the same.
The contact can then:
- Be added to dynamic lists based on data sent from Zapier.
- Have personalized messages sent to them using merge parameters.
- Change their path in a journey based on their survey submission with journey filters.
Tracking a Custom Event in Iterable through Zapier
In addition to adding and updating Iterable contacts, Zapier can also send custom events to:
- Add users to a journey.
- Segment contacts based on custom event history.
- Track campaign conversions.
- Measure which variant in an experiment resulted in the conversion.
For example, to send a reminder email and SMS to the contacts that have registered for an event:
In Zapier, click Make a Zap.
For the trigger, select your event registration app. In this case we’re using Splash That. In this example event, we are capturing the registrant’s name, email, and phone number.
For the action, select Iterable.
Select Track Event and your connected Iterable project.
In the Edit Template page, add Event Name, Email, and any additional fields (phone number and first name) into the JSON data fields.
If you are using this custom event to trigger a conversion in another campaign, you can also include the campaign ID and template ID for the campaign and the conversions and experiment results will be tracked in Iterable.
For this use case, we’ll want to create a journey in Iterable to capture these events and add the contacts into a list of registrants. We can do this by creating a simple journey that’s triggered by the custom event, adds the custom event data to the contact’s record, and adds the contact to a list:
Now the fun part: we'll create a journey in Iterable to send a reminder email and text to the registrants.
Create a new journey and set up the Start tile to use the recurring event. We’ll use the recurring event trigger to set up a scheduled one-time send on the day before the event. To ensure the trigger only fires once, we set the end date before the next scheduled recurrence.
Lastly, let’s add the action to send a reminder email at 9:30AM the day before the event then delay until 10AM on the day of the event to send a reminder SMS.
Tracking Commerce Events in Iterable through Zapier
Using Zapier, we can track customer cart updates and purchases in Iterable.
Select Track a Purchase or Update a User's Shopping Cart Items from the Action Events dropdown
Set up your action. The input of the items array must be a Zapier Line Item.
If the user does not exist, a new user will be created if an email address is supplied.
userIdalone does not result in user creation.
total- Total order amount (do not include currency symbols). Not required in update cart actions.
items- An array of commerce items
id- Item ID
name- Item name
price- Item cost
quantity- Quantity of item
Test your action to ensure compatability.
Will Send event create a user if they do not currently exist in Iterable?
Yes, the user will be added to Iterable with the email specified in the template. If data fields are passed through the event that should be stored in the contact record, we recommend creating a simple journey triggered by the custom event and an update contact fields action using merge parameters from the event properties.