- 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 MNTN. 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.- DeduplicationBrowser and server copies of the same purchase collapse on event ID, so nothing is counted twice.
- Bot and fraud filteringAutomated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
03 Activate
Delivered to MNTN
Forward resolved conversions to MNTN so connected-TV spend is judged against orders rather than against household reach.
See the MNTN integration →
MNTNWhat it receives hashed email / phonematch a purchase to an exposed householdip / user_agenthousehold matching for a no-click channelevent_iddedupe against site-side reportingvalue / currencymeasure television on revenueorder timestampplace the order inside the airing window
The catch
WooCommerce sites vary enormously in how checkout is built, and browser-side conversion tags break on custom checkouts more often than on hosted platforms.
Capturing on the server sidesteps the theme entirely.
Where to check in MNTNDelivery you can audit
MNTN › Performance › Conversions
Matched conversions report the household attribution window they fell inside.
What changes
What changes when WooCommerce feeds MNTN. Two gains on the MNTN side, two on the WooCommerce side.
MNTN
Server-side delivery
Events reach MNTN through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.
MNTN
Identity-resolved events
Events sent to MNTN 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, MNTN included, is forwarded the same resolved events.
Upstack dashboardExample
WooCommerce Data source Connected
MNTN Destination Healthy
Read the full MNTN 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 MNTN destination
Under Destinations, add MNTN. Every resolved WooCommerce event is then forwarded to it.
-
03
Check delivery to MNTN
Every conversion is inspectable from the moment it fires to the moment the platform confirms it.
FAQ
Questions about WooCommerce and MNTN.
How do I check that WooCommerce events are reaching MNTN?
Open MNTN › Performance › Conversions. Matched conversions report the household attribution window they fell inside.
Will a purchase be counted twice?
No. Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.
How long does it take to connect WooCommerce to MNTN?
Most brands are live in under 20 minutes. Once WooCommerce is connected, every destination receives the same resolved events, MNTN included.