Two-way sync
Changes in DealCloud or Iterable instantly reflect in both systems. No stale data, no manual imports.
Keep DealCloud and Iterable in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
DealCloud owns the customer relationship and the pipeline; Iterable runs the campaigns, audiences, and outreach that fill it. The two overlap on the same people and companies — a lead in one system is a subscriber, a segment member, an event registrant, or an ad audience in the other. When that overlap is bridged by CSV exports or a nightly job, sales works from lists that no longer match reality and marketing keeps targeting people whose status has already moved on.
Stacksync syncs Task, User, Deal, Company in DealCloud with Lists, Catalogs, Commerce / Purchases, Export data in Iterable field by field, in real time, and in both directions. You decide which system owns which fields — DealCloud can own account and opportunity status while Iterable owns engagement and campaign membership — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Status, stage, or score set in one system updates the matching record in the other, so a lead marketing is still nurturing is not worked as sales-ready, and a closed account stops receiving prospecting.
Where Iterable builds lists, segments, or ad audiences, membership tracks the fields and stage owned in DealCloud, so who receives a campaign reflects current pipeline reality instead of a stale export.
New leads or responders captured in Iterable flow into DealCloud assigned and deduplicated, so nothing sits in a marketing list waiting for someone to export it.
Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.
| DealCloud objects | Iterable objects | How this pairing syncs | |
|---|---|---|---|
| User Synced with incremental and full sync. | Users User profiles keyed by email or userId with custom data fields; upserted via POST /api/users/update, read via GET /api/users/{email} or getByUserId, bulk-written via /api/users/bulkUpdate (up to 1000 users per call), and deleted or GDPR-forgotten. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| Relationship Synced with incremental and full sync. | Export data Historical user and event records pulled through the Export API (/api/export/data.json, data.csv, and userEvents) across data types like emailSend, emailOpen, emailClick, emailBounce, purchase, and customEvent. | Relationship is specific to DealCloud and Export data to Iterable — each maps to any object or custom field on the other side. | |
| Activity Synced with incremental and full sync. | Events Custom and system events tracked via /api/events/track and /api/events/trackBulk (up to 1000 events per call); a single user's event history is read via GET /api/events/{email}. | Activity is specific to DealCloud and Events to Iterable — each maps to any object or custom field on the other side. | |
| Task Synced with incremental and full sync. | Campaigns Email, SMS, push, and in-app sends; metadata and metrics read via GET /api/campaigns and /api/campaigns/metrics, created and sent via /api/campaigns/create and /api/campaigns/trigger. | Task is specific to DealCloud and Campaigns to Iterable — each maps to any object or custom field on the other side. | |
| Deal Synced with incremental and full sync. | Templates Reusable email/SMS/push/in-app message templates with handlebars fields; read via /api/templates and per-channel get endpoints, written via /api/templates/email/upsert and the other channel upserts. | Deal is specific to DealCloud and Templates to Iterable — each maps to any object or custom field on the other side. | |
| Company Synced with incremental and full sync. | Lists Static subscriber lists; read via GET /api/lists and /api/lists/getUsers, with users added or removed via /api/lists/subscribe and /api/lists/unsubscribe to control who receives a send. | Company is specific to DealCloud and Lists to Iterable — each maps to any object or custom field on the other side. |
Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.
DetectionStacksync polls DealCloud for changes on an incremental schedule, reading only records changed since the previous pass. Incremental via each entry's last-modified timestamp.
DeliveryEach detected change is written to Iterable through its API, with automatic retries and rate-limit backoff.
DetectionIterable notifies Stacksync of record changes through webhook events. System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time.
DeliveryEach detected change is written to DealCloud through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every DealCloud–Iterable connection.
Changes in DealCloud or Iterable instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever DealCloud or Iterable data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single DealCloud or Iterable record.
Track your DealCloud ⇄ Iterable sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between DealCloud and Iterable.
Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.
Authenticate DealCloud and Iterable with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the DealCloud and Iterable objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between DealCloud and Iterable: authenticate both systems, choose the objects to sync (such as DealCloud's User and Relationship), map fields visually, and changes propagate both ways in milliseconds — no code required.
DealCloud: The DealCloud API authenticates with OAuth 2.0 client-credentials; API access and scopes are provisioned by a DealCloud administrator. Iterable: Bulk endpoints cap at 1000 records per call - /api/users/bulkUpdate accepts up to 1000 users and /api/events/trackBulk up to 1000 events. Stacksync's field mapping accounts for these differences between DealCloud and Iterable without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means DealCloud and Iterable records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed DealCloud and Iterable connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom DealCloud–Iterable integration in-house.
Yes — Stacksync ships production-grade connectors for both DealCloud and Iterable. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on DealCloud: Incremental via each entry's last-modified timestamp; DealCloud has no universal native change-data-capture, so Stacksync polls modified rows on an interval. On Iterable: System Webhooks push email/SMS/push/in-app and custom events (send, open, click, bounce, complaint, unsubscribe) as JSON POSTs in near real time; historical backfill and incremental catch-up run through the Export API over a date range. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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:
Every pair below is a real-time, two-way sync. Search all 382 integrations available for DealCloud and Iterable.