Iterable Source

RudderStack’s Cloud Extract (ETL) product will be sunset on December 1, 2025. See this release note for more details.

Iterable is a popular growth marketing platform that lets you maximize customer interaction and improve your customers’ overall LTV (Life Time Value).

This document guides you in setting up Iterable as a source in RudderStack. Once configured, RudderStack automatically ingests your Iterable data and routes it to your specified data warehouse destination.

Note that:

• For sending real-time events from Iterable to RudderStack via webhook, refer to the Iterable Webhook documentation.
• All the Cloud Extract sources support sending data only to a data warehouse destination.

Getting started

To set up Iterable as a source in RudderStack, follow these steps:

1. Log into your RudderStack dashboard.
2. Go to Sources > New source > Cloud Extract and select Iterable from the list of sources.
3. Assign a name to your source and click Next.

Connection settings

Next, configure the following dashboard settings:

• Start Date: Enter the date from which RudderStack should ingest the Iterable data. RudderStack will not replicate any data before this date.
• API Key: Enter your Iterable project’s API key by going to Integrations > API Keys.

Destination settings

The following settings specify how RudderStack sends the data ingested from Iterable to the connected warehouse destination:

• Table prefix: RudderStack uses this prefix to create a table in your data warehouse and loads all your Iterable data into it.

Note that RudderStack does not add special characters like - or _ to the prefix by default. Hence, you need to specify it while setting the prefix.

• Schedule Settings: RudderStack gives you three options to ingest the data from Iterable:
  • Basic: Runs the syncs at the specified time interval.
  • CRON: Runs the syncs based on the user-defined CRON expression.
  • Manual: You are required to run the syncs manually.

For more information on the schedule types, refer to the Common Settings guide.

Selecting the data to import

You can choose the Iterable data that you want to ingest by selecting the required resources.

The below table mentions the sync types supported by the Iterable resources while syncing data to your warehouse destination:

For more information on the Full Refresh and Incremental sync modes, refer to the Common Settings guide.

Iterable is now configured as a source. RudderStack will start ingesting data from Iterable as per your specified schedule and frequency.

You can further connect this source to your data warehouse by clicking the Add Destination button:

Use the Use Existing Destination option if you have an already-configured data warehouse destination in RudderStack. To configure a data warehouse destination from scratch, select the Create New Destination button.

FAQ

Is it possible to have multiple Cloud Extract sources writing to the same schema?

Yes, it is.

RudderStack associates a table prefix for every Cloud Extract source writing to a warehouse schema. This way, multiple Cloud Extract sources can write to the same schema with different table prefixes.

Where can I find the Iterable API key?

You can get your Iterable project’s API key by logging into your Iterable dashboard and navigating to Integrations > API Keys. For more information, refer to the Iterable documentation.

How does RudderStack count the events for Cloud Extract sources?

RudderStack counts the number of records returned by the source APIs when queried during each sync. It considers each record as an event.

How does RudderStack count the events for Cloud Extract sources?

RudderStack counts the number of records returned by the source APIs when queried during each sync. It considers each record as an event.

How does RudderStack set the table name for the data sent via Cloud Extract sources?

RudderStack sets the table name for the resource you are syncing to the warehouse by adding rudder_ to the Table prefix you set while configuring your Cloud Extract source in the dashboard.

For example, if you set test_ as the Table prefix in the dashboard, RudderStack sets the table name as test_rudder_<resource_name>, where <resource_name> is the name of the resource you are syncing (for example, contacts, messages, etc.).

Note that RudderStack does not add the character _ to the prefix by default. Hence, you need to specify it while setting the prefix.

Questions? Contact us by email or on Slack