Two-way sync
Changes in Iterable or Shopify instantly reflect in both systems. No stale data, no manual imports.
Keep Iterable and Shopify in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Shopify 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 ProductVariants, Orders, Customers, Abandoned Checkouts in Shopify with Export data, Users, Events, Campaigns in Iterable field by field, in real time, and in both directions. You decide which system owns which fields — Shopify 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.
Where Iterable builds lists, segments, or ad audiences, membership tracks the fields and stage owned in Shopify, so who receives a campaign reflects current pipeline reality instead of a stale export.
New leads or responders captured in Iterable flow into Shopify assigned and deduplicated, so nothing sits in a marketing list waiting for someone to export it.
When a contact or lead is created or edited in either system, the matching record appears or updates in the other, so campaigns reach real people and reps see who is already being marketed to.
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.
| Iterable objects | Shopify objects | How this pairing syncs | |
|---|---|---|---|
| Catalogs Named catalogs of items (products, content) used for personalization and recommendations; items upserted and read via /api/catalogs/{catalogName}/items. | ProductVariants Synced with incremental and full sync per the Stacksync docs. | Catalogs is specific to Iterable and ProductVariants to Shopify — each maps to any object or custom field on the other side. | |
| Commerce / Purchases Purchase and cart activity tracked via /api/commerce/trackPurchase and /api/commerce/updateCart, feeding revenue attribution and abandoned-cart journeys. | Orders Purchase transactions; pushed to ERPs for fulfillment and billing, and read into databases for reporting. | Commerce / Purchases is specific to Iterable and Orders to Shopify — each maps to any object or custom field on the other side. | |
| 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. | Customers Buyer records; matched to CRM contacts for marketing and lifetime-value analysis. | Export data is specific to Iterable and Customers to Shopify — each maps to any object or custom field on the other side. | |
| 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. | Abandoned Checkouts Synced with incremental and full sync per the Stacksync docs. | Users is specific to Iterable and Abandoned Checkouts to Shopify — each maps to any object or custom field on the other side. | |
| 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}. | Products Catalog entries; often mastered in a PIM or ERP and written into Shopify. | Events is specific to Iterable and Products to Shopify — each maps to any object or custom field on the other side. | |
| 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. | ProductMedias Synced with incremental and full sync per the Stacksync docs. | Campaigns is specific to Iterable and ProductMedias to Shopify — 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.
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 Shopify through its API, with automatic retries and rate-limit backoff.
DetectionShopify notifies Stacksync of record changes through webhook events. Webhook topics per resource, with polling on updated_at as a fallback.
DeliveryEach detected change is written to Iterable through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Iterable–Shopify connection.
Changes in Iterable or Shopify instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Iterable or Shopify data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Iterable or Shopify record.
Track your Iterable ⇄ Shopify sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Iterable and Shopify.
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 Iterable and Shopify 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 Iterable and Shopify 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 Iterable and Shopify: authenticate both systems, choose the objects to sync (such as Iterable's Catalogs and Commerce / Purchases), map fields visually, and changes propagate both ways in milliseconds — no code required.
On the Shopify side: ProductVariants, Orders, Customers, Abandoned Checkouts, plus custom fields where Shopify exposes them. On the Iterable side: Export data, Users, Events, Campaigns. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Iterable and Shopify: Segments and audiences follow the CRM; Where Iterable generates leads: hand-off without re-keying; New and updated people stay in step. Where Iterable builds lists, segments, or ad audiences, membership tracks the fields and stage owned in Shopify, so who receives a campaign reflects current pipeline reality instead of a stale export.
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. Shopify: GraphQL Admin API (primary) and REST Admin API (legacy). Authentication: OAuth via a custom Shopify app: admin creates an app in the Shopify Dev Dashboard, enables required API scopes, sets the Stacksync redirect URL, then supplies shop name + Client ID and Client Secret to Stacksync. Stacksync manages authentication, retries, and rate limits on both sides.
Shopify: Setup requires the Shopify administrator to create a custom app in the Shopify Dev Dashboard (no one-click OAuth app). 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 Iterable and Shopify without custom code.
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 492 integrations available for Iterable and Shopify.