Can Demandbase and Iterable sync in both directions?

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.

What should be ready before the Demandbase and Iterable initial load?

Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Identify the Demandbase account, edition, environment, and business objects the integration must access. Identify the Iterable account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.

How fast does the Demandbase to Iterable sync run?

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.

Will existing duplicates merge automatically?

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.

How do I map Demandbase fields to Iterable?

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.

What should I do if a record fails to sync?

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.

What does a Demandbase and Iterable integration cost?

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.

Which records should the Demandbase and Iterable pilot start with?

Start by reviewing Campaigns in Demandbase 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.

Marketing

Demandbase and Iterable integration

Plan how Demandbase and Iterable should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

Scope your workflow with an integration engineer
Review the systems, records, and updates you need

Integration planning

stacksync.com

Demandbase

Iterable

Review the integration scope

Teams building with Stacksync

Plan the connection your business needs

Explore a Demandbase and Iterable integration with a Stacksync engineer. Stacksync support for Demandbase and 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.

01 / Business process

Start with one meaningful update

Identify the record that changes in Demandbase or Iterable, where it needs to appear, and which team depends on it.

02 / Data access

Establish the available connection

Bring the objects, account editions, and required directions. An engineer can review the connector path, permissions, and field access.

03 / Success criteria

Define a result you can verify

Agree on record matching, acceptable delay, expected volume, and how your team will resolve failed updates.

Explore the technical references

Technical referenceAvailable documentation, candidate record relationships, and questions for your technical review.

What records can you sync?

Explore the record types and read/write requirements for each system.

DemandbaseConnection and object support require review

Record types to review with Stacksync

Record type	Coverage and requirements
Accounts	Confirm support for this record type and the direction you need.
Opportunities	Confirm support for this record type and the direction you need.
People (Persons)	Confirm support for this record type and the direction you need.
Activities	Confirm support for this record type and the direction you need.
Campaigns	Confirm support for this record type and the direction you need.
Account & Person Lists (Audiences)	Confirm support for this record type and the direction you need.

Discuss Demandbase requirements

IterableConnection and object support require review

Record types to review with Stacksync

Record type	Coverage and requirements
Users	Confirm support for this record type and the direction you need.
Events	Confirm support for this record type and the direction you need.
Campaigns	Confirm support for this record type and the direction you need.
Templates	Confirm support for this record type and the direction you need.
Lists	Confirm support for this record type and the direction you need.
Catalogs	Confirm support for this record type and the direction you need.

Discuss Iterable requirements

Connection requirements and limits

Demandbase

Integration interface: REST APIs (Demandbase One) - a B2B API (company/contact search, details, and match with async bulk enrichment jobs), a read-only Data Export API and a write-capable Data Import API (both async bulk jobs), and a Subscription API for webhook change alerts.
Authentication: Confirm the credentials, API plan, and permissions required for Demandbase.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Limitations to check

Confirm Stacksync support for Demandbase and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Iterable

Integration interface: Iterable REST API (JSON over HTTPS): Users, Events, Campaigns, Templates, Lists, Catalogs, and Commerce endpoints, plus a bulk Export API for historical data
Authentication: Confirm the credentials, API plan, and permissions required for Iterable.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Limitations to check

Confirm Stacksync support for Iterable and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare your technical review

Use the worksheets and reference checks to capture record identity, ownership, and the result your business expects.

Implementation reference

Record identity and field ownership

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, ownership, and test cases

Record matchingCampaigns Campaigns

Compare whether Demandbase Campaigns and Iterable Campaigns describe the same campaign or audience in your business.

Demandbase: Object support to establish
Iterable: Object support to establish

Record identity

Keep campaign ID, channel/account context, and separate audience membership IDs.

Field ownership

Marketing owns campaign activation and audience eligibility; analytical metrics do not imply permission to launch a campaign.

Fields to include

Source campaign ID
Channel reference
Status
Audience references
Measurement window

Architecture decision

Choose how to connect your systems

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.

Stacksync managed sync

Best fit: Review compatibility with a Stacksync engineer using an example of the records and updates you need.
Operating responsibility: Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose: Check record matching: Keep campaign ID, channel/account context, and separate audience membership IDs. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit: A vendor-built integration may fit if it supports your Demandbase and Iterable record types.
Operating responsibility: Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose: First check whether either vendor offers this integration. If available, verify Campaigns / Campaigns, update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider when Demandbase and Iterable need a transformation, approval, or action outside a direct record sync.
Operating responsibility: Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose: Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery.

File or scheduled snapshot

Best fit: Consider for a one-time Demandbase / Iterable migration or a reporting need with an explicit freshness window.
Operating responsibility: Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose: Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow reference

From a business event to the right update

Open a workflow to see its trigger, record relationships, and expected result.

Campaign or audience sync test

Starting event: A change to the selected Campaigns or Campaigns record needs a defined result in the other system.

Start with Demandbase 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.

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.

Link audience context between Demandbase and Iterable

Starting event: An approved customer or campaign change affects eligibility or reporting in Demandbase.

Identify the relevant Accounts or Opportunities and the corresponding identity in Users or Events.
Choose the authority for consent, audience membership, and campaign activation. Reporting a customer attribute does not authorize outreach.
Define how unsubscribes, deleted identities, and late activity change the current audience.

Expected result: A removed or ineligible person stays excluded after a repeated update; audience membership refers to the correct identity.

If it fails: Recompute current eligibility before retrying membership or activation; do not replay an obsolete permission to contact someone.

Production readiness

Test the behavior your business depends on

Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.

Campaigns / Campaigns

Test case

Test a removed audience member, a paused campaign, and one campaign reported across multiple channels.

Expected result

The expected campaign or audience relationship is preserved with no duplicate action or unintended write.

Direction and permissions

Test case

Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.

Expected result

Only an approved, supported direction and permitted fields are written.

Freshness and reconciliation

Test case

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.

Expected result

The process meets its agreed freshness target and reconciliation has no unexplained differences.

Failure recovery

Find the cause. Restore the data flow.

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated campaign or audience change

Investigate

Inspect Demandbase Campaigns and Iterable Campaigns, their IDs, and the destination error.

Next action

Rebuild the current eligible audience before retrying activation or membership updates.

A record type or update is unavailable

Investigate

Check the Demandbase and Iterable connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

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.

How updates move between Demandbase and Iterable

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

Demandbase Iterable Direction requires confirmation

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 Iterable.

Iterable Demandbase Direction requires confirmation

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 Demandbase.

Update timing and record limits

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
Review write-back, deletion handling, update timing, and account limits with the integration team.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare Demandbase and Iterable access

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.

Demandbase setup checklist

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

Iterable setup checklist

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.

Prepare to go live

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 Demandbase and Iterable planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Security and control for your integrations

Use SSO and SCIM to manage access, secure connection options to reach your systems, and record-level retry and revert controls to resolve sync errors.

Explore security controls

FAQ