Zapier + Iterable Integration

The Zapier + Iterable integration makes it easy to connect your Iterable account to 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

1. In Iterable, create a server-side API Key to use with Zapier.

2. Create a Zapier account and sign in.

3. Click Make a Zap.

4. Zapier connects to hundreds of apps (Typeform, for example). 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.

5. For the action step, select Iterable and the action you'd like to perform.

6. If you haven’t connected to your Iterable account already, Zapier will ask you to enter the API key you generated in step 1.

   NOTE

   For testing, use sandbox projects. 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.

7. For this example, use the Create a User option.

8. Configure your Zapier template by mapping fields captured in other apps to Iterable.

9. 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).

If you've connected Typeform to Iterable, for example, Iterable can automatically capture contacts submitted through the Typeform survey. New contacts are created, and existing contacts (based on email address) are updated.

These 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 Iterable. You can use these custom events to:

• Add users to a journey.
• Segment contacts based on custom event history.
• Track campaign conversions.
• Measure which experiment variant resulted in a conversion.

For example, to send a reminder email and SMS to the contacts that have registered for an event:

1. Configure your Iterable project to track the custom event you're interested in. To learn how, read Managing Custom Events.

   TIP

   For more information about events in general, read Events Overview.

2. In Zapier, click Make a Zap.

3. For the trigger, select your event registration app, and capture fields like name, email, and phone number.

4. For the action, select Iterable.

5. Select Track Event and your connected Iterable project.

6. On the Edit Template page, specify an Event Name, Email, and any additional fields (phone number and first name) into the JSON data fields.

   IMPORTANT

   For Event Name, enter the exact name of the event you configured your Iterable project to track in step 1, above.

7. 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.

8. For this use case, create a journey in Iterable to capture these events and add the contacts into a list of registrants. To do this, create 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.

   Next, create a journey in Iterable to send a reminder email and text to the registrants.

9. Create a new journey and set up the Start tile to use the recurring event. 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, set the end date before the next scheduled recurrence.

10. Lastly, add an 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.

1. Select Track a Purchase or Update a User's Shopping Cart Items from the Action Events dropdown

2. Set up your action. The input of the items array must be a Zapier Line Item.

   Required fields:

   • email (email address) or userId (user ID)

     NOTE

     If the user does not exist, a new user will be created if an email address is supplied. userId alone 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

3. Test your action to ensure compatability.

# FAQs

# Will send event create users who not already 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.