- 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 Checkout Champ event reaches StackAdapt. Captured on the funnel page, resolved to a person, then sent.
01 Capture
Captured from Checkout Champ
Track Checkout Champ funnels with the Upstack Pixel, from the first page to the completed order, and send each event to your destinations resolved against the same identity graph.
See the Checkout Champ integration →
Checkout ChampWhat it sends orderId / transactionIdthe completed Checkout Champ orderemail / phoneread from the checkout formfirstName / lastNameshipping name from the formcity / country / postalCodeshipping address fieldsvaluethe order value sent with the purchase
02 Understand
Resolved to one person before it leaves
Every Checkout Champ 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 StackAdapt
Server-side conversions to StackAdapt with hashed identifiers attached, so multi-channel programmatic is measured on your orders.
See the StackAdapt integration →
StackAdaptWhat it receives hashed email / phoneidentity matching on arrivalsa_click_idcredit the click that drove itexternal_idstable person across sessionsevent_iddedupe against the browser pixelvalue / currencyvalue-based bidding
The catch
Checkout Champ funnels don't run the Upstack app embed, so tracking has to be added to the funnel itself: the Upstack Pixel and event scripts go into Global Scripts and load in the head of every funnel page.
The purchase fires once per order ID and skips partial orders, so a reload doesn't send an order twice.
Where to check in StackAdaptDelivery you can audit
StackAdapt › Conversions › Conversion tracking
Server-side conversions are labeled by source, so a deduplicated pair is visible as one.
What changes
What changes when Checkout Champ feeds StackAdapt. Two gains on the StackAdapt side, two on the Checkout Champ side.
StackAdapt
Server-side delivery
Events reach StackAdapt through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.
StackAdapt
Identity-resolved events
Events sent to StackAdapt carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.
Checkout Champ
Every funnel step tracked
Page views, checkout starts, add-to-carts, shipping and payment steps and completed orders fire from the funnel, so your platforms see the whole path rather than the landing page alone.
Checkout Champ
One setup, every destination
Connect Checkout Champ once and forward to every ad platform and email tool you run.
Setup
Live in under 20 minutes.
Connect Checkout Champ once and every destination, StackAdapt included, is forwarded the same resolved events.
Upstack dashboardExample
StackAdapt Destination Healthy
Read the full StackAdapt setup guide → -
01
Add the Upstack Pixel to Global Scripts
With the Upstack Data app installed on your Shopify store, paste the Checkout Champ tracking script the Upstack team provides, with your Pixel ID, into Global Scripts so it loads in the head of every funnel page. Disable Checkout Champ’s Facebook Pixel first.
-
02
Add the StackAdapt destination
Under Destinations, add StackAdapt. Every resolved Checkout Champ event is then forwarded to it.
-
03
Check delivery to StackAdapt
Every conversion is inspectable from the moment it fires to the moment the platform confirms it.
FAQ
Questions about Checkout Champ and StackAdapt.
How do I check that Checkout Champ events are reaching StackAdapt?
Open StackAdapt › Conversions › Conversion tracking. Server-side conversions are labeled by source, so a deduplicated pair is visible as one.
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 Checkout Champ to StackAdapt?
Most brands are live in under 20 minutes. Once Checkout Champ events reach Upstack, every destination receives the same resolved events, StackAdapt included.