- 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 WooCommerce event reaches HubSpot. Captured on the server, resolved to a person, then sent.
01 Capture
Captured from WooCommerce
Capture WooCommerce orders and customer events server-side and forward them to every platform you buy on.
See the WooCommerce integration →
WooCommerceWhat it sends order_idWooCommerce order numberbilling_email / phonecheckout contact fieldscustomer_idWordPress user, when logged inline_itemsproducts and quantitiesorder_totalorder value after discount
02 Understand
Resolved to one person before it leaves
Every WooCommerce 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
WordPress user IDs only exist for registered customers.
A CRM keyed on them loses every guest, which on most stores is the majority of first purchases.
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 WooCommerce feeds HubSpot. Two gains on the HubSpot side, two on the WooCommerce 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.
WooCommerce
Every event, server-side
Storefront and checkout events are captured from WooCommerce on the server, independent of the browser.
WooCommerce
One setup, every destination
Connect WooCommerce once and forward to every ad platform, email tool and warehouse you run.
Setup
Live in under 20 minutes.
Connect WooCommerce once and every destination, HubSpot included, is forwarded the same resolved events.
Upstack dashboardExample
WooCommerce Data source Connected
HubSpot Destination Healthy
Read the full HubSpot setup guide → -
01
Connect WooCommerce
Capture WooCommerce orders and customer events server-side and forward them to every platform you buy on.
-
02
Add the HubSpot destination
Under Destinations, add HubSpot. Every resolved WooCommerce event is then forwarded to it.
-
03
Check delivery to HubSpot
Trace any property back to the event that set it.
FAQ
Questions about WooCommerce and HubSpot.
How do I check that WooCommerce 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.
How long does it take to connect WooCommerce to HubSpot?
Most brands are live in under 20 minutes. Once WooCommerce is connected, every destination receives the same resolved events, HubSpot included.