Iterable is a growth marketing and customer engagement platform. It enables brands to create, execute and optimize campaigns across email, push, SMS, in-app and more with unparalleled data flexibility.
Featureslink
| Feature Name | Supported | Notes |
|---|---|---|
| Capture Deletes | check | LIST, MESSAGE_TYPE, and CHANNEL tables |
| Custom Data | ||
| Data Blocking | ||
| Column Hashing | ||
| Re-sync | check | Connector level |
| History | check | |
| API Configurable | check | |
| Priority-first sync | check | EVENT |
| dbt Package | check | Get the package: source / transform |
Setup guidelink
Follow our step-by-step Iterable setup guide to connect Iterable with your destination using Fivetran connectors.
Schema Informationlink
This schema applies to all Iterable connections.
The EVENT table is the main table that contains all the fields we receive from the Events API. The EVENT_EXTENSION table serves as an extension to the EVENT table. We store any additional fields we receive from the webhooks in the EVENT_EXTENSION table.
To zoom, open ERD in new window
Schema Noteslink
The EVENT table contains information of following events:
- Custom Event
- Email Send
- Email Open
- Email Click
- Email UnSubscribe
- Email Subscribe
- Email Bounce
- Email Complaint
- Hosted Unsubscribe Click
- InApp Open
- InApp Click
- Inbox Message Impression
- Inbox Session
- Push Send
- Push Bounce
- Push Open
- Purchase
- SMS Send
- SMS Bounce
- SMS Received
- Web Push Send
The LIST_USER_HISTORY table is the only way to join the LIST and USER_HISTORY tables.
Excluding the table from the sync may lead to data discrepancy.