Skip to content
Marketing ⇄ CRM

Iterable to Shopify integration — real-time, two-way sync

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.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Iterable and Shopify

Keep the people you sell to and the people you market to in one shared view: Shopify and Iterable sync contacts, accounts, and engagement in real time, in both directions.

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.

Common use cases

  • 01 Write inventory levels from a WMS or ERP into Shopify locations to keep availability accurate.
  • 02 Mirror the product catalog from a PIM or database into Shopify products, variants, and metafields.
  • 03 Write list subscribe/unsubscribe changes from a CRM back into Iterable Lists so suppression and opt-in state stay current before the next send.
  • 04 Two-way sync User profiles and their custom data fields between Iterable and a Postgres database or CRM so attributes and subscription state stay aligned in both systems.

Common sync patterns

Segments and audiences follow the CRM

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.

Where Iterable generates leads: hand-off without re-keying

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.

New and updated people stay in step

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.

What you can sync between Iterable and Shopify

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.

How changes propagate between Iterable and Shopify

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.

Iterable Shopify Sub-second propagation

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.

Shopify Iterable Sub-second propagation

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.

Rate-limit considerations

  • Iterable: Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.
  • Shopify: GraphQL uses a calculated query-cost budget; the REST API uses a leaky-bucket model.
What ships with Iterable ⇄ Shopify

Connect Iterable and Shopify for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Iterable–Shopify connection.

Real-time

Two-way sync

Changes in Iterable or Shopify instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Iterable or Shopify data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Iterable or Shopify record.

Observability

Monitoring

Track your Iterable ⇄ Shopify sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Iterable and Shopify.

How the Iterable and Shopify connectors work

Iterable

Integration surface
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.
Change detection
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.
Capabilities
read · write · webhooks
Rate limits
Limits are per endpoint and per project/key; exceeding one returns HTTP 429, so exponential backoff is advised. Event tracking allows far higher volume than metadata endpoints like campaigns/templates, and the Export API is throttled more tightly. Since Nov 10, 2025, passing the key in the query string or body is rate-limited more strictly than the Api-Key header.

Shopify

Integration surface
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
Change detection
Webhook topics per resource, with polling on updated_at as a fallback
Capabilities
read · write · webhooks
Rate limits
GraphQL uses a calculated query-cost budget; the REST API uses a leaky-bucket model.
Shopify setup guide
How it works

How to connect Iterable to Shopify — three steps, no code

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.

  1. 01

    Connect your apps

    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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Iterable connected
    Shopify connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Iterable ⇄ Shopify
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Iterable Shopify
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Iterable and Shopify integration FAQ

SECURITY

Security teams trust Stacksync

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.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Related integrations

Every pair below is a real-time, two-way sync. Search all 492 integrations available for Iterable and Shopify.

Popular · 8 of 492
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.