Home
Connectors
Checkout Champ - MGID

Send Checkout Champ funnel events to MGID

Q: How do I check that Checkout Champ events are reaching MGID?

Open MGID › Dashboard › Conversions. The postback log records each server-side conversion and the click it was matched to.

Q: Will a purchase be counted twice?

No. Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.

Q: How long does it take to connect Checkout Champ to MGID?

Most brands are live in under 20 minutes. Once Checkout Champ events reach Upstack, every destination receives the same resolved events, MGID included.

Each event is resolved to a person against a 750M+ device graph before it reaches MGID, with restored click IDs, deduplicated conversions and delivery you can audit.

Request a demo Start free trial

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 MGID. 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 order
email / phoneread from the checkout form
firstName / lastNameshipping name from the form
city / country / postalCodeshipping address fields
valuethe 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.

Ad platforms accept almost anything and tell you very little. These controls exist so you can see what was sent and what was accepted, rather than inferring it from a reporting gap.

03 Activate

Delivered to MGID

Server-side conversions to MGID with hashed identifiers and restored click IDs, so a channel that is hard to attribute stops being invisible.

See the MGID integration

MGIDWhat it receives

hashed email / phoneidentity matching on arrival
mgid_click_idcredit the click that drove it
external_idstable person across sessions
event_iddedupe against the browser pixel
value / 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 MGIDDelivery you can audit

MGID Dashboard Conversions

The postback log records each server-side conversion and the click it was matched to.

What changes

What changes when Checkout Champ feeds MGID. Two gains on the MGID side, two on the Checkout Champ side.

MGID

Server-side delivery

Events reach MGID through its server API rather than the browser, so ad blockers and ITP don’t cost you conversions.

MGID

Identity-resolved events

Events sent to MGID 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, MGID included, is forwarded the same resolved events.

Upstack dashboardExample

MGID Destination Healthy

Read the full MGID 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 MGID destination

Under Destinations, add MGID. Every resolved Checkout Champ event is then forwarded to it.
03

Check delivery to MGID

Every conversion is inspectable from the moment it fires to the moment the platform confirms it.

FAQ

Questions about Checkout Champ and MGID.

How do I check that Checkout Champ events are reaching MGID?

Open MGID › Dashboard › Conversions. The postback log records each server-side conversion and the click it was matched to.

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 MGID?

Most brands are live in under 20 minutes. Once Checkout Champ events reach Upstack, every destination receives the same resolved events, MGID included.