- 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 HubSpot. 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 person, one record, across devices and identifiers.
- Bot and fraud filteringAutomated traffic never becomes a contact.
03 Activate
Delivered to HubSpot
Push identity-resolved events and contacts into HubSpot so CRM records match what actually happened.
See the HubSpot integration →
HubSpotWhat it receives emailthe contact keylifecycle propertiesstage and pipelinedeal / order valuerevenue on the record
The catch
Shopify's customer ID and the email a shopper types at checkout are frequently not the same person over time.
Treating either as the primary key on its own is how a CRM ends up with duplicate contacts that never merge.
Where to check in HubSpotRecords you can audit
HubSpot › the contact timeline
and the duplicate-management view, which should stop growing.
What changes
What changes when Shopify feeds HubSpot. Two gains on the HubSpot side, two on the Shopify side.
HubSpot
Server-side delivery
Events reach HubSpot through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.
HubSpot
Identity-resolved events
Events sent to HubSpot 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
HubSpot Destination Healthy
Read the full HubSpot 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 HubSpot destination
Under Destinations, add HubSpot. Every resolved Shopify event is then forwarded to it.
-
03
Check delivery to HubSpot
Trace any property back to the event that set it.
FAQ
Questions about Shopify and HubSpot.
How do I check that Shopify events are reaching HubSpot?
Open HubSpot › the contact timeline, and the duplicate-management view, which should stop growing.
Will this create duplicate contacts?
No. One person, one record, across devices and identifiers.
Do I need a developer to connect Shopify to HubSpot?
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.