Salesforce 
HubSpot 
NetSuite 
Zendesk 
Microsoft Dynamics 365 Sales 
Dynamics 365 F&O 
Attio 
Pipedrive 
Zoho CRM 
Campfire 
Rillet 
Front 
Shopify 
Amazon Seller Central 
SendGrid Plan how HubSpot and Iterable should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.
Proposed workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting eventA change involving HubSpot Campaigns or Iterable Campaigns needs a defined result in the other system.
Start with HubSpot Campaigns and Iterable Campaigns. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve contact/audience identities and channel-account references.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
What to verifyTest a removed audience member, a paused campaign, and one campaign reported across multiple channels.
Review records and field ownershipProposed record relationships
Use these examples to define record matching and field ownership for your technical review.
Download the mapping worksheetCSV · No email required
| HubSpot record | Iterable record | Record matching | Field ownership |
|---|---|---|---|
| CampaignsDocumented record: 🕘 Coming soonRecord matching | CampaignsProposed record; confirm Stacksync object support. | Keep campaign ID, channel/account context, and separate audience membership IDs. | Marketing owns campaign activation and audience eligibility; analytical metrics do not imply permission to launch a campaign. |
| UsersDocumented record: SupportedRecord matching | UsersProposed record; confirm Stacksync object support. | Use the immutable user ID within the tenant or directory. Do not equate an application user with a CRM customer contact. | Identity and application owners approve account lifecycle and access changes; synchronize only approved attributes. |
These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.
Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.
Read and write support varies by record
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| ✅ Supported. Confirm field permissions and sync direction. |
| 🕘 Coming soon. Confirm field permissions and sync direction. |
| ❌ Not supported. Confirm field permissions and sync direction. |
Connection and object support require review
Record types to review with Stacksync
| Record types | Coverage and requirements |
|---|---|
| Confirm support for this record type and the direction you need. |
Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.
View setup requirements and limits| Connection requirement | HubSpot | Iterable |
|---|---|---|
| Integration interface | REST API (CRM v3) | Iterable REST API (JSON over HTTPS): Users, Events, Campaigns, Templates, Lists, Catalogs, and Commerce endpoints, plus a bulk Export API for historical data |
| Authentication | OAuth | Confirm the credentials, API plan, and permissions required for Iterable. |
| Change detection | Record updates and association changes need separate validation. | Confirm how Stacksync detects changes for this connector and the objects you need. |
| Read access | Available for supported records | Confirm with Stacksync |
| Write access | Available for supported records | Confirm with Stacksync |
Enterprise controls
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Inspect sync errors and use retry and revert controls to resolve failed updates.
Read the recovery guideImplementation
Review setup, record relationships, testing, and recovery for your implementation.
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.
Setup guides: Authorize HubSpot
Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.
Use the HubSpot and Iterable planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.
Download the mapping worksheet · CSV, no email required
Record matching
Compare whether HubSpot Campaigns and Iterable Campaigns describe the same campaign or audience in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Fields to include
References: HubSpot: Campaigns documentation
Record matching
Compare whether HubSpot Users and Iterable Users describe the same application user or identity in your business.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Fields to include
References: HubSpot: Users documentation
Choose a method around one example record and the update your business needs. Use Campaigns / Campaigns to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Campaigns or Campaigns record needs a defined result in the other system.
Expected result: Test a removed audience member, a paused campaign, and one campaign reported across multiple channels.
If it fails: Rebuild the current eligible audience before retrying activation or membership updates.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Users or Users record needs a defined result in the other system.
Expected result: Test a renamed login, disabled account, missing group, and a user existing in two tenants.
If it fails: Review access impact before retrying a lifecycle change; reconcile current identity state and retain an approval trail.
This is an evaluation scenario; connector and operation support require confirmation.
Starting event: A customer-facing change in HubSpot needs operational context in Iterable.
Expected result: The relationship survives a lifecycle change without creating a duplicate customer or triggering an unintended business action.
If it fails: Inspect merge/conversion history and existing destination records before replaying a lifecycle transition.
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Test a removed audience member, a paused campaign, and one campaign reported across multiple channels.
The expected campaign or audience relationship is preserved with no duplicate action or unintended write.
Test a renamed login, disabled account, missing group, and a user existing in two tenants.
The expected application user or identity relationship is preserved with no duplicate action or unintended write.
Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.
Only an approved, supported direction and permitted fields are written.
Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Inspect HubSpot Campaigns and Iterable Campaigns, their IDs, and the destination error.
Rebuild the current eligible audience before retrying activation or membership updates.
Inspect HubSpot Users and Iterable Users, their IDs, and the destination error.
Review access impact before retrying a lifecycle change; reconcile current identity state and retain an approval trail.
Check the HubSpot and Iterable connector guides, account permissions, and any operations marked On Request.
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Compare current source values, destination validation, identity mappings, and any side effects already completed.
Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.
Read the Stacksync issues dashboard guide for retry and revert behavior.
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
Detect changesRecord updates and association changes need separate validation. Association detection uses full scans unless Associations CDC Boost is configured for an eligible account.
Apply updatesConfirm that Stacksync can create or update the records you need in Iterable.
Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.
Apply updatesConfirm that Stacksync can create or update the records you need in HubSpot.
Explore a HubSpot and Iterable integration with a Stacksync engineer. Stacksync support for Iterable is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.
Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Have a HubSpot Super Admin authorize Stacksync through the account connection flow. Identify the Iterable account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
Start by reviewing Campaigns in HubSpot and Campaigns in Iterable. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.
Choose a method around one example record and the update your business needs. Use Campaigns / Campaigns to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
Integration directory
Review documented support, sync direction, and setup requirements on each pair page. Search all 496 integrations listed for HubSpot and Iterable.
Popular · 8 of 496
HubSpot and Twitter Ads 
HubSpot and Marketo 
HubSpot and Salesforce Marketing Cloud 
HubSpot and Cvent 
Iterable and Insightly 
Iterable and Intercom 
Iterable and Kommo 
Iterable and Kustomer Next step
Walk through your HubSpot and Iterable records, field mappings, and requirements with an integration engineer.
