Two-way sync
Changes in Azure Synapse Analytics or Iterable instantly reflect in both systems. No stale data, no manual imports.
Keep Azure Synapse Analytics 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.
Azure Synapse Analytics is where your team models customers, product usage, and revenue into trusted tables; Iterable runs the campaigns, audiences, and messages that reach those people. The two overlap wherever the same person, account, or segment matters to both, and when the bridge between them is a nightly export or a hand-built list, marketing targets stale data while analytics never sees what the campaign returned.
Stacksync syncs Tables (dedicated SQL pool), External tables, Views, Schemas in Azure Synapse Analytics 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 — a computed score or segment can flow out to Iterable while sends, opens, and conversions flow back to Azure Synapse Analytics — and Stacksync keeps every copy consistent and resolves conflicts by rules you set.
Unsubscribes, bounces, and consent or opt-out flags held in either system propagate to the other, so no one is messaged after opting out and Azure Synapse Analytics holds the current state for auditing.
Product-usage counts, plan tier, region, or account owner computed in Azure Synapse Analytics appear on the matching record in Iterable, so targeting, routing, and personalization use up-to-date context.
A segment or score built in Azure Synapse Analytics — high-intent accounts, churn risk, a lifetime-value tier — lands as an audience or contact field in Iterable, so campaigns target the people your data actually points to instead of a static export.
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.
| Azure Synapse Analytics objects | Iterable objects | How this pairing syncs | |
|---|---|---|---|
| Schemas Namespaces that separate staging, integration, and presentation layers. | Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. | Schemas is specific to Azure Synapse Analytics and Commerce / Purchases to Iterable — each maps to any object or custom field on the other side. | |
| Materialized views Precomputed aggregates that speed reads of frequently synced result sets. | 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. | Materialized views is specific to Azure Synapse Analytics and Export data to Iterable — each maps to any object or custom field on the other side. | |
| SQL pools Dedicated or serverless compute contexts that determine how and where queries run. | 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. | SQL pools is specific to Azure Synapse Analytics and Users to Iterable — each maps to any object or custom field on the other side. | |
| Tables (dedicated SQL pool) Distributed warehouse tables that serve as sync destinations for analytics workloads. | 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}. | Tables (dedicated SQL pool) is specific to Azure Synapse Analytics and Events to Iterable — each maps to any object or custom field on the other side. | |
| External tables Tables over files in the data lake, queried through serverless SQL and often read-only in syncs. | 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. | External tables is specific to Azure Synapse Analytics and Campaigns to Iterable — each maps to any object or custom field on the other side. | |
| Views Curated projections used when downstream tools should not read base tables directly. | 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. | Views is specific to Azure Synapse Analytics and Templates 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 Azure Synapse Analytics for changes on an incremental schedule, reading only records changed since the previous pass. Polling on watermark columns.
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 applied to Azure Synapse Analytics as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Synapse Analytics–Iterable connection.
Changes in Azure Synapse Analytics or Iterable instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Azure Synapse Analytics 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 Azure Synapse Analytics or Iterable record.
Track your Azure Synapse Analytics ⇄ Iterable sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Azure Synapse Analytics 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 Azure Synapse Analytics 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 Azure Synapse Analytics 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 Azure Synapse Analytics and Iterable: authenticate both systems, choose the objects to sync (such as Azure Synapse Analytics's Schemas and Materialized views), map fields visually, and changes propagate both ways in milliseconds — no code required.
Common patterns for Azure Synapse Analytics and Iterable: Suppression and consent stay aligned; Enrich records with warehouse context; Activate a modeled audience. Unsubscribes, bounces, and consent or opt-out flags held in either system propagate to the other, so no one is messaged after opting out and Azure Synapse Analytics holds the current state for auditing.
Azure Synapse Analytics: SQL wire protocol (TDS) with T-SQL for SQL pools; additional Spark and pipeline surfaces exist but syncs use the SQL endpoint. Authentication: SQL authentication or Microsoft Entra ID. Iterable: Iterable REST API (JSON over HTTPS): Users, Events, Campaigns, Templates, Lists, Catalogs, and Commerce endpoints, plus a bulk Export API for historical data. Authentication: API key sent in the Api-Key HTTP header (also accepted as Api_Key; the name is case-insensitive). Keys are scoped by type - Server-side, JavaScript (Web SDK), or Mobile - with optional JWT-enabled keys. US projects use api.iterable.com; EU projects use api.eu.iterable.com. Stacksync manages authentication, retries, and rate limits on both sides.
Azure Synapse Analytics: Batch-style loading (staged, set-based inserts) performs far better than row-by-row writes, which shapes how a sync should deliver data into it. Iterable: Rate limits are per endpoint and return HTTP 429 when exceeded; since November 10, 2025, providing the API key in the query string or request body is throttled more strictly than the Api-Key header. Stacksync's field mapping accounts for these differences between Azure Synapse Analytics 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 Azure Synapse Analytics and Iterable records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Azure Synapse Analytics and Iterable connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Azure Synapse Analytics–Iterable integration in-house.
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 501 integrations available for Azure Synapse Analytics and Iterable.