Welcome to Encatch Docs
Data syncBetaConnectorsEngagement and marketing

Iterable

Send Encatch survey events to Iterable - where to find the details in Iterable and how to set up the connection

Beta. This connector is built from Iterable's public API documentation and is waiting for its first confirmation on a live Iterable account. The steps below are a high-level guide: menu names in Iterable may differ slightly. Use Test connection and Logs to confirm your set-up, and tell us what you find.

Overview

The Iterable connector sends survey events to an Iterable project as custom events on the user, ready to trigger journeys.

What it getsSurvey events as custom events
EventsSurvey shown, started, submitted, partially submitted and dismissed
Anonymous respondentsNot sent: identified users only
User profileNot updated yet: events only
StatusBeta

What You'll Need

Before you start, make sure you have:

  • An Iterable project — and where it is hosted (United States or Europe)
  • A Server-side API key (Step 1)
  • The project type — how the project identifies users: by user ID, by email, or hybrid

Step 1: Create a Server-side API key in Iterable

  1. In Iterable, open Integrations → API Keys and click New API key.
  2. Choose the type Server-side, create the key and copy it.
  3. Open Settings → Project settings and note how the project identifies users: UserID-based, Email-based or Hybrid.

Step 2: Add the connection in Encatch

  1. In Encatch, open Data sync → Survey events and click Add connection.
  2. Choose Iterable.
  3. Enter a Name you'll recognise in the list and in Logs.
  4. Fill in the Iterable settings:
FieldWhat to enter
Data centerUnited States (default) or Europe.
Project typeUserID-based (default), Email-based or Hybrid, as in Project settings.
Server-side API keyThe Server-side API key.
  1. Press Test connection. Encatch shows what Iterable answered.

Encatch keeps the keys encrypted and never shows them again. To change one later, press Replace.


Step 3: Choose what to send

  1. Under Surveys, choose All surveys or Only these surveys.
  2. Under What is sent, tick the events to send. A new connection starts with Survey shown, started, submitted and dismissed ticked. Survey partially submitted is off until you tick it.
  3. Rename an event if you want another name in Iterable. The defaults are encatch_survey_shown, encatch_survey_started, encatch_survey_submitted, encatch_survey_partial and encatch_survey_dismissed.
  4. Open Advanced options to choose how users are identified, whether answers are sent and the rate limit.

Every option is explained in Connection settings.


Step 4: Save and start sending

Click Save. Saving does not start sending: press Start sending when you are ready. From then on events go out as they happen, and every delivery is listed in Logs.


Check it in Iterable

After Test connection, look for the event encatch_test_event in Iterable, for example on a user's event history.


Good to know

  • Project type decides the identifier. User ID-based and hybrid projects get the user ID. An email-based project gets the user's email, and an event for a user with no email is not sent: it shows as Skipped in Logs.
  • Events only. Iterable gets the events; Encatch does not set user fields in Iterable yet, so Update the user's profile is shown off.
  • Rate limit. Iterable takes 2,000 requests a second per project, so a limit is rarely needed.

Was this page helpful?