Shopify to Klaviyo
Forward every Shopify event to Klaviyo server-side, resolved to a person against a 750M+ device graph — so flows trigger on a known profile rather than an anonymous session.
Connection
Connect Shopify to Klaviyo with Upstack Data
Shopify
One server-side setup that captures every Shopify storefront and checkout event, then forwards it to every tool you spend on.
Shopify integrationKlaviyo
Attach re-identified emails to events before they reach Klaviyo, so browse and cart flows fire for people the pixel lost.
Klaviyo integrationWhat changes
What changes when Shopify feeds Klaviyo.
Recover carts you couldn’t email
Anonymous browsers are resolved to a known profile, so abandonment flows can trigger for visitors Klaviyo never identified.
Profiles, not sessions
Events arrive attached to a resolved customer, so flow logic and segmentation work on a person.
100% of conversions, server-side
Orders are captured from Shopify’s servers, so nothing is lost to ad blockers, ITP or a failed browser call.
Recognise returning customers
Shopify customer IDs, emails and phones are matched against the graph, so repeat buyers are identified across devices.
What actually moves
What Shopify carries, and what Klaviyo needs.
Shopify and Klaviyo describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what Shopify can put on an event, the right is what Klaviyo can actually use.
Shopify sends
- order_id
- Shopify order and checkout token
- email / phone
- customer contact from checkout
- customer_id
- Shopify customer record, if they have one
- line_items
- products, variants and quantities
- total / subtotal / discount
- order economics
- customer_type
- new or returning, resolved before send
Klaviyo receives
- email / phone
- the profile key — no profile, no send
- external_id
- tie a browse to a known person
- $value
- flow and campaign revenue attribution
- event properties
- what the flow branches on
Sending you can audit
How you know it is working.
Messaging mistakes are expensive and public. These controls exist so a flow never fires against a profile that should not have received it.
Per-profile inspection
Trace any event to the profile it resolved to, and see why.Deduplication
One order produces one event, so a single purchase cannot trigger the same flow twice.Bot and fraud filtering
Automated traffic never becomes a profile, so list quality and deliverability are not paying for it.
Where to check in Klaviyo
KlaviyoAnalyticsMetrics. The event appears as its own metric, and the profile count on it is the number you were losing before.
Related connectors
Other places Shopify can send to.
- ShopifyMeta Conversions API
- ShopifyGoogle Ads Conversions
- ShopifyTikTok Events API
- ShopifyPinterest
- ShopifySnapchat
- ShopifyReddit
- ShopifyMicrosoft Ads
- ShopifyX
Other sources that feed Klaviyo.
- WooCommerceKlaviyo
- BigCommerceKlaviyo
- Checkout ChampKlaviyo
- RechargeKlaviyo
- Custom stackKlaviyo
- FunnelishKlaviyo
- Lasso CommerceKlaviyo
- Phoenix TechnologiesKlaviyo
- SkioKlaviyo
- Loop SubscriptionsKlaviyo
- StripeKlaviyo
- Everything Klaviyo can take12 sources feed Klaviyo, and the setup is the same for each one.Klaviyo integration
- How resolution worksEvery event matched against a 750M+ device graph before it is forwarded.Upstack Signal
- What it costsThree plans that scale with your order volume. Every connector is on every plan.See pricing
Get Shopify talking to Klaviyo.
A 15-minute walkthrough of this connector on your own account.