Skip to content
Marketing · Two-way sync platform

Iterable integration.

Connect your Iterable workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Users, Events and Campaigns.

  • Review your systems with an integration engineer
  • Get a scoped implementation and validation plan

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Record types

Iterable records to discuss.

These Iterable record examples help scope a technical review. They are not a list of verified Stacksync operations.

Users
Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact.
Events
Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key.
Campaigns
Keep campaign ID, channel/account context, and separate audience membership IDs.
See 3 more record examples
Templates
Identify this record type and the operation you need to review with Stacksync.
Lists
Identify this record type and the operation you need to review with Stacksync.
Catalogs
Identify this record type and the operation you need to review with Stacksync.
Connection setup

Iterable connection requirements.

Review Iterable access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion.

Prepare access and scope for the engineering review
  • Identify the Iterable account, edition, environment, and business objects the integration must access.
  • Confirm a Stacksync connector or implementation path for Iterable, including read/write support, authentication, and initial-load limits.

Integration design

Match records and fields for your Iterable integration.

Assign authority for consent, audience membership, campaign state, and analytical results separately. Define how removals and opt-outs reach every relevant destination.

Use these design questions to prepare a representative record and the business rules your integration must preserve.

Explore record matching and field-mapping checks
IterableSource record IDKeep the account and record type
Record matchingSource ID ↔ destination IDLink the same record across systems
Selected destinationDestination record IDPreserve its local key and rules
Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.
Match the same record in both systems
Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact.
Load related records in the right order
Resolve tenant and group references and establish a protected administrative-account policy.

Mapping checks by record type

Users

Confirm object support with Stacksync

Identity
Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact.
Fields to consider
Source user ID · Tenant reference · Account status · Group references
Related records to resolve first
Resolve tenant and group references and establish a protected administrative-account policy.
Test before going live
Test a renamed login, disabled account, missing group, and a user existing in two tenants.

Events

Confirm object support with Stacksync

Identity
Keep the source event ID, source system, occurrence time, and ingestion time. Use an explicit duplicate-detection key.
Fields to consider
Source event ID · Event type · Occurred-at time · Related record ID · Payload version
Related records to resolve first
Resolve the related customer, user, or transaction identity without assuming the event ID is the entity ID.
Test before going live
Deliver the same event twice, then an older event after a newer one; verify duplicate and ordering behavior.

Campaigns

Confirm object support with Stacksync

Identity
Keep campaign ID, channel/account context, and separate audience membership IDs.
Fields to consider
Source campaign ID · Channel reference · Status · Audience references · Measurement window
Related records to resolve first
Resolve contact/audience identities and channel-account references.
Test before going live
Test a removed audience member, a paused campaign, and one campaign reported across multiple channels.

Download the field-mapping workbook (CSV) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer.

Setup and validation

Validate the Iterable integration in four steps.

An opted-out person remains excluded after a profile update, and campaign results reconcile for the same channel and measurement window.

View the four setup tests and expected results

  1. Verify Iterable credentials and resource scope

    After confirming an implementation path, validate the selected access method with the intended account, region or workspace, and resource scope. Record the credential owner and renewal procedure, then demonstrate access to one selected object.

    Expected result: The selected resource is accessible through the approved credential, with the renewal and revocation procedure assigned to an owner.

  2. Test record matching for Users

    Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test a renamed login, disabled account, missing group, and a user existing in two tenants.

    Expected result: An opted-out person remains excluded after a profile update, and campaign results reconcile for the same channel and measurement window.

  3. Test the operation your workflow needs

    Review one Iterable record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration.

    Expected result: The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair.

  4. Test recovery and name the support owner

    For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity.

    Expected result: The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors.

Use the production-readiness checklist to record test results, assign support owners, and agree on when to go live.

Troubleshooting

Troubleshoot your Iterable integration.

Diagnose record matching, delayed changes, and rejected operations
A Iterable record appears under the wrong destination record
Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. Resolve tenant and group references and establish a protected administrative-account policy. Repair the ID relationship before repeating the operation.
The first load looks correct but later results differ
Confirm the selected Iterable implementation’s change-detection method for Users, Events and Campaigns. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture.
One operation succeeds while another is rejected
Check the specific Iterable object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available.

Review retry, replay, and recovery behavior before repeating an operation that may already have succeeded.

Review your Iterable workflow with an engineer

Iterable integration guides

FAQ

Iterable connector FAQ

How should I plan an integration with Iterable?

Assign authority for consent, audience membership, campaign state, and analytical results separately. Define how removals and opt-outs reach every relevant destination. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding.

Can the Iterable connector write changes back?

Write-back support is not established for this connection. Review the Iterable records and fields you need with a Stacksync engineer, then test the required operation with a representative record.

Which identifiers should I preserve for Iterable data?

Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact.

Which related records should I load first for Iterable?

Resolve tenant and group references and establish a protected administrative-account policy.

How do I validate Iterable changes after the initial load?

Test a renamed login, disabled account, missing group, and a user existing in two tenants. An opted-out person remains excluded after a profile update, and campaign results reconcile for the same channel and measurement window.

What will we cover in a Iterable integration demo?

Start with one workflow and a sample record from Users, Events and Campaigns. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document.

Explore Iterable connections

Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair.

214 integration guides

CRM · 46

ERP · 38

Database · 50

Data warehouse · 29

Accounting and finance · 17

AI · 5

Analytics · 7

Communications · 6

E-commerce · 8

Marketing · 8

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2SSH TunnellingSSL certificatesIP WhitelistingVPN gatewayVPC peeringand more
Coworkers laughing in front of a laptop in a casual office setting

Connect the systems your business runs on.
Build your next workflow with Stacksync.

Book a demo Get started