Iterable 

Iterable is a cross-channel customer engagement platform for marketing teams, providing campaign management, customer journey orchestration, email, SMS, and push messaging, and engagement analytics.

Iterable integration replicates data using the Iterable API.

Preparing for authentication

To access your data, you need to authenticate the connection with your account credentials.

To set up your Iterable account, you need:

• An Iterable project hosted in Iterable's US Data Center (USDC). The European Data Center (EDC) is not supported.
• An Iterable user account with the Org Admin role or the Manage Integrations project permission.

To create an API key:

1. Log into your Iterable account.
2. Navigate to Integrations > API Keys.
3. Click New API Key.
4. Enter a descriptive name, for example QlikDataIntegration.
5. For Key type, select Server-side. Do not select Read-only, Mobile, JavaScript, or any JWT-enabled variant — those key types are not supported by the connector.
6. Click Create.

   Copy and paste the API key into a secured file.

Creating the connection

자세한 내용은 SaaS 응용 프로그램에 연결을 참조하십시오.

1. 필요한 연결 속성을 입력합니다.

2. 연결 이름에 연결 이름을 입력합니다.

3. 연결이 만들어질 때 연결에 대한 메타데이터를 정의하려면 연결 메타데이터 열기를 선택합니다.

4. 만들기를 클릭합니다.

Limitations and considerations

• Server-side API key only. Read-only, Mobile, JavaScript, and JWT-enabled API keys are not supported. A Read-only Server-side key passes initial connection validation but cannot access Iterable's data export API, so syncs of the email_* and users streams will fail.
• The API key is validated when the connection is saved. If the key has insufficient permissions, has been disabled, or was created in a different Iterable data center, connection creation fails with an authentication error.
• Data export rate limit. Iterable's data export API — used by the email_* and users streams — applies a limit of 4 requests per minute per project, compared to 100 requests per second for standard resource endpoints. The Window in Days setting controls how many data-export requests are issued per sync: a 1-year backfill at the default 30-day window produces approximately 12 requests per affected stream and fits within the limit, whereas very small window values produce significantly more requests and may exceed the export rate limit.
• Rate-limit responses (HTTP 429) and transient server errors (5xx) are retried automatically with exponential backoff. Authentication errors (401) and validation errors (400) are surfaced immediately and fail the sync.
• Renamed fields in users. Two user-profile fields are renamed to avoid case-normalization collisions at the destination: Industry is emitted as _industry, and the nested field offers.Intro APR is emitted as _offers.intro APR. This applies only to these two fields in the users stream.
• list_users is a thin membership view. Each record contains only email, listId, and a synthetic updatedAt timestamp set to the time the sync ran. It does not include user profile fields. To get full user data, sync the users stream and join on email.
• templates re-reads all records on every sync. The Iterable templates API does not support server-side filtering by updatedAt, so the connector retrieves all templates on every sync and applies the bookmark filter client-side. Sync time for this stream does not decrease as the bookmark advances.
• Start Date sets the initial bookmark for the eleven incremental streams only. Once a stream has advanced past Start Date, subsequent syncs resume from the saved bookmark. Changing Start Date in the connection settings does not affect records already replicated.

Schema

Depending on your destination, table and column names may not appear as they are outlined below.