- 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 Okendo. 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.- DeduplicationOne purchase, one request, even when the order is amended.
- Bot and fraud filteringFraudulent orders never enter the request queue.
03 Activate
Delivered to Okendo
Send resolved customers and orders to Okendo so review requests reach the right person.
See the Okendo integration →
OkendoWhat it receives emailwho to surveyorder_idthe purchase in questionproduct IDswhat to ask about
The catch
A funnel buyer who accepted two upsells has three purchases and one experience.
Review requests keyed on orders ask three times.
Where to check in OkendoDelivery you can audit
Okendo › the review request schedule
checked against the same day's orders.
What changes
What changes when Checkout Champ feeds Okendo. Two gains on the Okendo side, two on the Checkout Champ side.
Okendo
Server-side delivery
Events reach Okendo through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.
Okendo
Identity-resolved events
Events sent to Okendo 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, Okendo included, is forwarded the same resolved events.
Upstack dashboardExample
Okendo Destination Healthy
Read the full Okendo 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 Okendo destination
Under Destinations, add Okendo. Every resolved Checkout Champ event is then forwarded to it.
-
03
Check delivery to Okendo
Trace any request back to the order and customer it came from.
FAQ
Questions about Checkout Champ and Okendo.
How do I check that Checkout Champ events are reaching Okendo?
Open Okendo › the review request schedule, checked against the same day's orders.
Will a customer be asked twice about one order?
No. One purchase, one request, even when the order is amended.
How long does it take to connect Checkout Champ to Okendo?
Most brands are live in under 20 minutes. Once Checkout Champ events reach Upstack, every destination receives the same resolved events, Okendo included.