Learn how to create Syncs for Iterable

Welcome to the Iterable Signal Sync setup article! In this guide, we will show you how to connect to it as a destination and send data to your Iterable. Let's get started!

Connecting to Iterable

  1. To begin, sign into the GrowthLoop Platform and navigate to the Destinations tab on the left sidebar. Click New Destination in the top right corner.

  1. In the Select Destination window that pops up, type Iterable into the search bar to find the Iterable. Click Add Iterable.

  1. Clicking Add Iterable will require you to select/insert the following information:

  • Destination Name: This is a friendly name for the destination, used to refer to it within the app.
  • Sync frequency: The default frequency for syncing audiences to a destination (Hourly or Daily).
  • API Key:
  1. Select Create. We will validate that we have all the proper permissions to load audience data to Iterable. If successful, you should now see the new Iterable Destination in your list of connected destinations!

Routing conversion signals to Iterable

  1. To route conversion signals to your Iterable, go to the Signals tab on the left sidebar and click New Signal Route in the top right corner.

  1. Clicking Create Signal Route will require you to select/insert the following information:

  • Route Name: A friendly name for the signal route.
  • Sync frequency: The default frequency for syncing conversion signals to a destination.
  • Update Rule: The default operation for syncing conversion signals to a destination. “Update only” changes existing data, “Insert only” inserts new data, and “Insert or update” is a hybrid action that adds new data if it's not already present or updates it if it is.
  • Source: The table that holds your conversion data for each event. Usually, it's organized within an events table.
  • Match Field: The column used to match and identify users from your source table in the destination system.
  • Unique Field: The column that contains values that are distinct for each user in the table.
  • Connection: The destination you will sync conversion data to. Please select the destination you set above.
  • Object Type: The event that you want to track and send to Iterable for conversion tracking and analytics. Please select Event.
  • Unique Field: The column used to match and identify users from the destination system in your source table.
  1. Once you finish selecting/inserting the required fields, click Save Route.

  1. Now it’s time to add the field mappings to enable your signal route. Iterable requires the following information about each conversion signal to be mapped:
  • Event Name: A distinct identifier for a specific customer action, which can be either a standard event like “Subscribe” or custom event.
  • Event ID: A unique string chosen by the advertiser, required for event deduplication, matching with browser/app events.
  • Event Time: Indicates when the event occurred.
  • Action Source: Indicates where conversions took place. The values you can send in the field are as follows: email, website, app, phone_call, chat, physical_store, system_generated, and other.
  1. To map the fields, select the column that represents the Event Name from the drop-down under Source.

  1. Under the Destination section, select Event Name from the drop-down.

  1. Click Add Mapping to include a new Source -> Destination row underneath.

  1. Repeat steps 5 through 7 to map the remaining 3 required destination fields: Event IDEvent Time, and Action Source.

  1. When you are ready to update your signal route with the newly mapped fields, you’ll be prompted with the following 2 options:
  • We recommend you go with the Updates Only option, especially if you’re setting up the signal for the first time.
  • Note: the Back-fill option is when you are updating an existing Signal Route with newly mapped fields and you’d like all your already synced events to have those fields backfilled for them. This operation can be very expensive and time consuming on your underlying Data Warehouse, so please choose that option if you’re absolutely sure.

  1. Congratulations! You have successfully created a signal sync to Iterable!