Docs
Sign up now
  • Getting started
    • Welcome to Sortment
    • Core Concepts
  • Schema
    • Overview
    • Related and Events Table
    • Setting Up Related Table
    • Setting Up Events Table
    • Custom Properties
  • ENGAGE
    • Audiences
      • Creating Audience
      • Audience Filters
      • Campaign Event Filters
      • Creating Audience Using SQL Builder
      • Managing Audiences
      • Audience Insights
    • Traits
      • Use Cases
      • Calculated Traits
        • Advanced Mode
      • Dynamic Traits
    • Profiles
      • User Profile View
    • Campaigns
      • Overview
      • Building a Campaign
      • Campaign Reports
        • Glossary
      • Conversion Tracking
  • Journeys
    • Getting Started
    • Journey Builder
    • Journey Components
      • Trigger
      • Delays
      • Flow Control
      • Action blocks
    • Tutorial: Creating a journey
    • Journey Settings
  • Connector
    • Overview
    • Getting started
      • Iterable
      • Klaviyo
  • Enable Data Sync
  • Setup
    • Data Warehouses
      • Snowflake
      • BigQuery
      • Redshift
      • Databricks
      • PostgreSQL
    • Cloud Bucket Storage
      • Amazon S3 for Snowflake
      • Google Cloud Storage for BigQuery
      • Amazon S3 for Redshift
      • Amazon S3 for Databricks
    • Communication Channels
      • Email
        • SendGrid
        • SES
        • Mailmodo
      • SMS
        • MSG91
        • Gupshup
      • WhatsApp
        • Meta (Facebook)
          • Add new Phone Number to Meta
        • Gupshup Enterprise
        • WATI
        • Gallabox
        • Yellow.ai
        • Kaleyra.io
    • Real-time Events
      • Setting up Event Source
      • Whitelist Event Payload
  • Settings
    • Sync Schedules
    • Audit Logs
    • Subscription Groups And Contact Fields
    • Delivery Controls
    • Test Profiles
    • Alerts
  • Data and Security
    • Technical Overview
    • Warehouse Data Practices
    • Data Access And Usage
    • Security Compliance
    • Audit Logs
    • Privacy Policy
Powered by GitBook
On this page
  • What you can sync to Iterable
  • Connection configuration
  • How to connect
  • Matching audience in Iterable
  • Need help?

Was this helpful?

  1. Connector
  2. Getting started

Iterable

PreviousGetting startedNextKlaviyo

Last updated 3 days ago

Was this helpful?

Sortment allows you to seamlessly send customer data—including audiences and traits – directly into Iterable. This guide walks you through the steps to set up the Sortment + Iterable integration, ensuring a smooth and reliable connection between platforms.

What you can sync to Iterable

Sortment supports sending the following data to Iterable:

  • Audiences: Synced as static lists into Iterable.

  • User Properties: Sync user properties from the warehouse directly. These get auto-mapped and synced into Iterable user fields.

  • User Traits: Custom traits defined on Sortment can be synced to Iterable as user fields.


Connection configuration

To connect Sortment to Iterable, you need the following:

  1. Iterable API Key: A server side API Key

  2. Project Type Identifier: Available in your Iterable account under Settings -> Project Settings

For detailed instructions on generating an API Key and understanding your Project Type Identifier, please refer to Iterable’s and documentation.

We recommend creating a dedicated Iterable API key for Sortment, with a clear name and appropriate scopes to ensure security and ease of management.

  • The API key should have to support syncing with sortment.

How to connect

  1. In Sortment, navigate to Integrations → Add Destination, then select Iterable.

  2. Enter your Iterable API Key and Project Identifier.

  3. Click Connect.

Sortment will verify your credentials and securely connect to your Iterable account. Once completed, you can start syncing data directly into your Iterable project.

Matching audience in Iterable

You can match audiences in Iterable using either:

  • Email

  • User ID

Pick the relevant identifier based on your Iterable project type (email-based, userID-based, or hybrid). Whenever possible, we recommend matching by User ID for greater consistency and to ensure a one-to-one mapping across systems.

Automated Field Creation: If a user field doesn’t exist in Iterable, Sortment will automatically create it with the correct data type.

Need help?

For assistance, please reach out to our support team at .

API Key Guide
Project Type Identifier
server-side permissions
support@sortment.com