Skip to content
Business productivity ⇄ CRM

Customer.io to Shopify integration — real-time, two-way sync

Keep Customer.io 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 Customer.io and Shopify

Sync what happens in Customer.io with the customer records in Shopify, in real time and in both directions.

The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Customer.io holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.

Stacksync connects Segments, Campaigns, Broadcasts, Deliveries / Messages in Customer.io to Orders, Customers, Abandoned Checkouts, Products in Shopify with bi-directional, real-time sync. Activity and record changes in Customer.io update the matching contact or account in Shopify, and CRM data flows the other way wherever Customer.io can store and use it.

Common use cases

  • Sync product usage and billing attributes from Postgres onto Customer.io people so lifecycle campaigns trigger on real product behavior.
  • Push CRM segments and lead status into Customer.io so messaging respects sales stage.
  • Write inventory levels from a WMS or ERP into Shopify locations to keep availability accurate.
  • Mirror the product catalog from a PIM or database into Shopify products, variants, and metafields.

Where Customer.io handles support or shared inboxes

Tickets and conversations attach to the right contact and account in Shopify, so sales sees open issues before the next call.

Where Customer.io runs outreach

Prospects, sends, and replies sync into Shopify, keeping lead status current without manual imports.

Where Customer.io supplies contact or company data

Enriched fields land directly on records in Shopify, and refreshes keep them from going stale.

What you can sync between Customer.io 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.

Customer.io objects Shopify objects
Deliveries / Messages Per-recipient message records whose lifecycle events flow out through reporting webhooks. ProductMedias Synced with incremental and full sync per the Stacksync docs.
Newsletters Recurring email sends with performance metrics available for reporting syncs. ProductVariants Synced with incremental and full sync per the Stacksync docs.
People Profiles with attributes, matched on identifiers like id or email; the main write target of data syncs. Orders Purchase transactions; pushed to ERPs for fulfillment and billing, and read into databases for reporting.
Objects Non-person entities such as accounts or companies, related to people for account-level messaging. Customers Buyer records; matched to CRM contacts for marketing and lifetime-value analysis.
Events Behavioral events sent via the Track API that trigger campaigns. Abandoned Checkouts Synced with incremental and full sync per the Stacksync docs.
Segments Attribute- or event-based groups; data syncs feed the attributes segments evaluate. Products Catalog entries; often mastered in a PIM or ERP and written into Shopify.
What ships with Customer.io ⇄ Shopify

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Customer.io 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 Customer.io or Shopify record.

Observability

Monitoring

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

Trading partners

EDI

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

How the Customer.io and Shopify connectors work

Customer.io

Integration surface
REST APIs split by purpose: Track API for data ingestion, App API for campaigns, people lookups, and messages
Authentication
Basic auth with site ID and API key for the Track API; bearer token for the App API
Change detection
Reporting webhooks push message and delivery events; person attribute changes are not streamed and require source-side detection
Capabilities
read · write · webhooks
Rate limits
Subject to per-API rate limits documented by Customer.io

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 Customer.io 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 Customer.io 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
    Customer.io connected
    Shopify connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Customer.io 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 · Customer.io ⇄ 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
    Customer.io Shopify
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Customer.io and Shopify integration FAQ

SECURITY

Security teams love 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
CSA STAR
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 386 integrations available for Customer.io and Shopify.

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

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