Checkout Champ integration: funnel tracking with the Upstack Pixel, resolved to a person

What Checkout Champ is

Checkout Champ is a funnel and checkout platform used by direct-response brands running upsell and continuity offers.

Funnel checkouts often sit outside the main storefront, which is exactly where tracking tends to break, and why the tracking has to go into the funnel itself.

How Checkout Champ works

Checkout Champ runs the funnel: a landing page, an initial order form, and a sequence of one-click upsell steps after the first purchase. Each accepted upsell is recorded against the same session but creates additional order value after the initial conversion has already fired. Continuity offers create recurring billing on top. Because the funnel is a separate surface from any main storefront, its order numbering, customer records and event stream are its own.

01

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.

02

Resolve each event to a person

Every Checkout Champ event is matched against a 750M+ device graph before it leaves, so a phone browse and a desktop checkout resolve to one customer rather than two strangers. Returning buyers are recognized as returning.

03

One purchase per order

The purchase event skips partial orders and fires once per order ID, so a reload doesn’t send the same order twice.

The pixel on every funnel page

The script loads the Upstack Pixel with your Pixel ID in the head of every funnel and records a page event on each load.

Events from the funnel

initiate_checkout fires when an order begins or a valid email is entered, followed by add_to_cart, add_shipping_info, add_payment_info and the purchase on completed orders.

Identity from the checkout form

The scripts read email, phone, shipping name, city, state, country and postal code from the form and send them with the events, so the funnel buyer can be resolved to a person.

One purchase per order

The purchase script reads Checkout Champ’s order data from the browser session, skips orders marked PARTIAL and fires once per order ID.

Set up with the Upstack team

The full script block comes from the Upstack team during onboarding, and the setup assumes the Upstack Data app is installed on your Shopify store.

Keep click IDs on the way to checkout

If funnel pages link to another domain, keep fbclid, gclid, ttclid and UTM parameters on those links so the ad click that started the visit stays attached.

How to verify it’s working

• On a funnel page, the Upstack Data Pixel Helper or the browser console shows the pixel firing with your Pixel ID.
• Walk through a test checkout from start to finish.
• In Events Manager, page, initiate_checkout and purchase events arrive against your Pixel ID.

Common problems and fixes

Duplicate events and inflated numbers.

Checkout Champ’s own Facebook Pixel is still on. Disable it before relying on Upstack.

Tracking doesn’t fire at all.

The Pixel ID was pasted with extra whitespace or mismatched quotes. Enter it exactly.

Conversion data that conflicts with Upstack’s.

Checkout builders may send their own conversion data. Audit the apps and integrations connected to the funnel.

Quick exits go untracked.

The script loads with defer. Load it with async instead.