Connecting Shopify to Customer.io
Shopify is the system of record for the order, and its admin numbers are the ones the business runs on. Customer.io triggers messages from behaviour, which means an event you send is not recorded — it is acted on, usually within seconds, by sending something to a real person. The join between them succeeds or fails on one thing: whether the person identifier you assign reaches the Shopify order before the conversion happens, because Customer.io can only match a conversion it can tie back to a click it recognizes.
Free30 minutesNo obligation
Specific to this pair
Shopify into Customer.io: order events that fill the email template
Forward Shopify webhooks to the Customer.io Track API, or use its integration, keyed on the Shopify customer ID or email your signup form also sends. Flatten the nested line-item fields templates use, send money as a number with currency, and include email consent. Acknowledge webhooks quickly and drop repeats on order ID so retries don't re-enter workflows.
Customer.io is usually added to a Shopify store to send post-purchase and win-back email from the order. Check whether Customer.io's own Shopify integration covers your needs; many stores instead forward Shopify webhooks to the Track API, keyed on the Shopify customer ID or email. Whichever key you pick must match what your signup form sends, or a newsletter subscriber who buys becomes a second person and gets the welcome series and the post-purchase series at once.
Attribute shape is the Shopify-specific trap. Templates reference product title, image and order number, and Shopify's order payload nests those inside line items; a webhook forwarded unflattened leaves the template rendering blanks. Flatten the fields the template uses, send money as a number with its currency, and include the email marketing consent from the Shopify customer record so campaigns can filter on it.
The failure that reaches customers: Shopify retries a webhook when your endpoint responds slowly, and each retry posted as a fresh event enters the workflow again. Acknowledge webhooks quickly and drop repeats on the order ID before anything reaches Customer.io. Test with a real Shopify test order against a separate workspace before pointing it at production.
Shopify → Customer.io · what breaks
Why this join usually fails — Shopify → Customer.io
- 01
The person identifier you assign never reaches Shopify
Shopify's checkout is locked down. Custom scripts on the checkout steps are not permitted on standard plans, and the old additional-scripts route is gone, so the identifier has to be captured on the storefront and carried into the order through cart or order attributes rather than read at the checkout itself.
- 02
Checkout extensibility hides what you need
Shopify deliberately restricts what runs during checkout. Setups that assumed free rein there broke when the platform moved to Checkout Extensibility, and many stores have been quietly under-reporting since.
- 03
A test event sending a real email
Because campaigns evaluate on arrival, there is no safe place to test in production. A malformed purchase event fired during development against a live workspace will send a real order confirmation to a real person, and that cannot be recalled.
- 04
Nothing reconciles afterwards
Customer.io shows the event and the resulting campaign activity on the person's timeline. Check what the event triggered, not just that it arrived.
Shopify → Customer.io · the fix
What working looks like — Shopify → Customer.io
The person identifier you assign on every order
Conversions arriving in Customer.io
The event lands on the person, evaluates against every campaign trigger and segment condition, and may send immediately.
Reconciled against the source
Shopify → Customer.io · architecture
How Shopify and Customer.io actually connect
- 1
Shopify holds the truth
The order carries line items, discounts, shipping, tax, currency and the customer. Note which figure you intend to report — total, subtotal, or net of shipping and tax — because most mismatches between Shopify and an ad platform turn out to be two people comparing two different numbers.
- 2
Customer.io needs a click to match
Customer.io needs the person identifier, the event name and any attributes the campaign conditions reference. An event whose attributes are missing will still trigger a campaign, which may then send a message with an empty placeholder in it.
- 3
The identifier is the bridge
The person identifier you assign, captured at the visit and carried into the Shopify order.
- 4
The event source decides reliability
Send when Shopify says the order is paid, from your server. This also covers draft orders, POS, and the customer who closes the tab on the thank-you page — none of which a pixel on the order-status page will ever see.
- 5
Deduplication at the destination
Customer.io does not deduplicate events. A purchase sent twice can enter a workflow twice and send two emails, and unlike a reporting duplicate the customer sees this one.
Shopify → Customer.io · normal or broken
Working vs. broken, side by side — Shopify → Customer.io
Normal, not a fault
The person identifier you assign present on the order
Sent from the orders/paid webhook
Deduplicated correctly
Customer.io does not deduplicate events. A purchase sent twice can enter a workflow twice and send two emails, and unlike a reporting duplicate the customer sees this one.
Reconciles with the source
Actually broken
The person identifier you assign missing on most records
Shopify's checkout is locked down. Custom scripts on the checkout steps are not permitted on standard plans, and the old additional-scripts route is gone, so the identifier has to be captured on the storefront and carried into the order through cart or order attributes rather than read at the checkout itself.
Sent from the browser
Shopify deliberately restricts what runs during checkout. Setups that assumed free rein there broke when the platform moved to Checkout Extensibility, and many stores have been quietly under-reporting since.
Counted twice, or not at all
Because campaigns evaluate on arrival, there is no safe place to test in production. A malformed purchase event fired during development against a live workspace will send a real order confirmation to a real person, and that cannot be recalled.
Nobody has reconciled it
Shopify → Customer.io · diagnose
Diagnostic order — Shopify → Customer.io
- 01
Count orders carrying the person identifier you assign
- 02
Follow one real conversion end to end
- 03
Open a recent paid order and read its note attributes
If the identifier is not on the order, nothing downstream can attribute it. Check ten orders, not one — partial coverage is the normal failure, not total absence.
- 04
Confirm which workspace you are writing to before sending anything
Environment separation is the whole safety mechanism in behaviour-triggered tools, and it is the thing most often skipped.
- 05
Read the match rate, not the success message
Customer.io shows the event and the resulting campaign activity on the person's timeline. Check what the event triggered, not just that it arrived.
Shopify → Customer.io · prove
How it gets proven — Shopify → Customer.io
Source of truth
Shopify Admin → Orders, for the same window, in the same currency and on the same timezone.
- The person identifier you assign confirmed present on a live order.
- Events confirmed on person profiles with the triggered campaign activity verified, in a test workspace before production.
- Order totals in Shopify Admin reconciled per order, not on the summed total, over a closed window.
Shopify → Customer.io · free audit
What we check in the free audit
- Count orders carrying the person identifier you assign
- Follow one real conversion end to end
- Open a recent paid order and read its note attributes
- Confirm which workspace you are writing to before sending anything
- Read the match rate, not the success message
Checked against
Shopify Admin → Orders, for the same window, in the same currency and on the same timezone.
Free30 minutesNo obligation
Shopify → Customer.io · when not to buy
When you don't need this — Shopify → Customer.io
- Measure identifier coverage yourself first — pull your last hundred orders and count how many carry the person identifier you assign.
- Shopify's own native channel integrations already cover simple single-currency stores adequately. If your admin numbers and platform numbers already agree, you do not need this.
- If your messaging is scheduled rather than behavioural, a simpler email platform does the job and removes the whole class of accidental-send risk.
Shopify → Customer.io · what we deliver
What gets built — Shopify → Customer.io
Identifier capture into Shopify
Capture the click identifier on the storefront, write it to a cart attribute so it becomes an order note attribute, and read it back server-side from the order. That path survives the checkout domain hop that breaks cookie-based approaches.
Event source: the orders/paid webhook
Send when Shopify says the order is paid, from your server. This also covers draft orders, POS, and the customer who closes the tab on the thank-you page — none of which a pixel on the order-status page will ever see.
Dispatch to Customer.io
The Customer.io Track API, posted server-side from your order or product system with the person identifier and event attributes.
Reversals where they exist
refunds/create fires with the original order reference, so refunds and cancellations can be reversed at the destination.
Written guarantee
95%+ tracking accuracy
Measured against Shopify Admin → Orders, for the same window, in the same currency and on the same timezone.. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Shopify → Customer.io questions, answered
Through Customer.io's Shopify integration if it fits, or by forwarding the paid-order webhook to the Track API with the customer key and flattened order fields. The key must match the one your signup forms use.
Shopify retries slow webhooks, and each retry can arrive as a new event. Deduplicate on the order ID before sending, and acknowledge webhooks quickly.
Almost always because the person identifier you assign never reached the Shopify order. Shopify's checkout is locked down. Custom scripts on the checkout steps are not permitted on standard plans, and the old additional-scripts route is gone, so the identifier has to be captured on the storefront and carried into the order through cart or order attributes rather than read at the checkout itself. Measure coverage before debugging the dispatch.
Customer.io identifies people by an ID you control, with email as a common choice. Anonymous events can be sent and later merged, but a mismatch creates a second profile — and a second profile means a second copy of every campaign that person is enrolled in.
The orders/paid webhook. Send when Shopify says the order is paid, from your server. This also covers draft orders, POS, and the customer who closes the tab on the thank-you page — none of which a pixel on the order-status page will ever see.
Customer.io shows the event and the resulting campaign activity on the person's timeline. Check what the event triggered, not just that it arrived.
More on Shopify → Customer.io
- Shopify POS → Customer.ioConnecting Shopify POS to Customer.io
- Checkout Extensibility → Customer.ioConnecting Shopify Checkout Extensibility to Customer.io
- Stripe → Customer.ioConnecting Stripe to Customer.io
RELATED GUIDES
Where Shopify → Customer.io fits in the rest of your tracking
- Ecwid → Customer.ioConnecting Ecwid to Customer.io
- Shopify POS → Customer.ioConnecting Shopify POS to Customer.io
- WooCommerce → Customer.ioConnecting WooCommerce to Customer.io
- Shopify → BrazeConnecting Shopify to Braze
- Shopify → AttentiveConnecting Shopify to Attentive
- Furniture ecommerceConversion tracking for furniture ecommerce, measured after delivery
- Swell → Customer.ioConnecting Swell to Customer.io
- Saleor → Customer.ioConnecting Saleor to Customer.io
Free · 30 min
Get Shopify and Customer.io joined properly
Free30 minutesNo obligation
