- US device IDs in the graph
- 750M+
- Match rate on events
- 90%+
- Identity window, per customer
- Lifetime
- Most brands are live
- <20 min
How it flows
How a Shopify event reaches Postscript. Captured on the server, resolved to a person, then sent.
01 Capture
Captured from Shopify
One Upstack app setup that captures Shopify storefront and checkout events with the Upstack Pixel, records every order directly from Shopify, and forwards both to every tool you spend on.
See the Shopify integration →
ShopifyWhat it sends order_idShopify order and checkout tokenemail / phonecustomer contact from checkoutcustomer_idShopify customer record, if they have oneline_itemsproducts, variants and quantitiestotal / subtotal / discountorder economics
02 Understand
Resolved to one person before it leaves
Every Shopify event is matched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer rather than two strangers.
How resolution works →
Resolved before it is sent - IdentityMatched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer.
customer_typeNew or returning, resolved before send.- DeduplicationOne order produces one event, so a single purchase cannot trigger the same flow twice.
- Bot and fraud filteringAutomated traffic never becomes a profile, so list quality and deliverability are not paying for it.
03 Activate
Delivered to Postscript
Send identity-resolved events to Postscript so SMS flows reach subscribers the pixel missed.
See the Postscript integration →
PostscriptWhat it receives phonesubscriber keyemailprofile matchingorder / cart propertiesautomation triggers
The catch
Shopify only knows a customer at checkout.
Everything before that (the browse, the add to cart, the return visit four days later) is anonymous unless something resolves it. That is the gap the flows fall into, not a problem with the flows.
Where to check in PostscriptSending you can audit
Postscript › Subscribers › the individual subscriber's activity feed
What changes
What changes when Shopify feeds Postscript. Two gains on the Postscript side, two on the Shopify side.
Postscript
Server-side delivery
Events reach Postscript through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.
Postscript
Identity-resolved events
Events sent to Postscript carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.
Shopify
Orders recorded from Shopify itself
Purchases also reach Upstack directly from Shopify, about 10 minutes after the order, so an order still counts when an ad blocker stopped the pixel or the shopper closed the page.
Shopify
Recognize returning customers
Shopify customer IDs, emails and phones are matched against the graph, so repeat buyers are identified across devices.
Setup
Live in under 20 minutes.
App install, no theme edits and no developer.
Upstack dashboardExample
Shopify Data source Connected
Postscript Destination Healthy
Read the full Postscript setup guide → -
01
Connect Shopify
In the Upstack dashboard, open System, then Data Sources, and click Connect Shopify. Approve the install in your Shopify Admin: Upstack reads products, orders and customers, and writes only its own pixel.
-
02
Add the Postscript destination
Under Destinations, add Postscript. Every resolved Shopify event is then forwarded to it.
-
03
Check delivery to Postscript
Trace any event to the profile it resolved to, and see why.
FAQ
Questions about Shopify and Postscript.
How do I check that Shopify events are reaching Postscript?
Open Postscript › Subscribers › the individual subscriber's activity feed.
Can one purchase trigger the same flow twice?
No. One order produces one event, so a single purchase cannot trigger the same flow twice.
Do I need a developer to connect Shopify to Postscript?
No. Shopify connects as an app install with no theme edits, and most brands are live in under 20 minutes. Headless storefronts add the Upstack Pixel script instead of the theme app extension.