Skip to main content
  1. Home
  2. Connectors
  3. Checkout Champ - Loops
Checkout Champ Loops

Send Checkout Champ funnel events to Loops

Each event is resolved to a person against a 750M+ device graph before it reaches Loops, so records and reporting reflect the person, not the device.

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 Loops. 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
Upstack DataResolved 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 person, one record, across devices and identifiers.
  • Bot and fraud filteringAutomated traffic never becomes a contact.

A CRM is only as trustworthy as its worst duplicate. These controls exist so the record reflects the person.

03 Activate

Delivered to Loops

Send resolved customer events to Loops for lifecycle messaging.

See the Loops integration
LoopsWhat it receives
  • emailcontact key
  • event namewhat the lifecycle message reacts to
  • data variablespersonalization

Which events reach Loops

Each Upstack event is mapped to the Loops event below before it is sent.

Upstack eventSent to Loops asKey data on the event
Product viewViewed ProductProductName, ProductID, Price, ImageURL
Add to cartAdded to CartProductName, ProductID, Price, Quantity, CartValue
CheckoutStarted CheckoutCartValue, ItemCount, CheckoutURL
PurchasePlaced OrderOrderID, Revenue, Items, DiscountCodes

When Upstack identifies a visitor, it attaches the contact’s email and other known properties, and syncs profile properties including name, email and location to Loops.

The catch

Funnel platforms and storefront platforms number their orders independently, so a CRM fed both ends up with colliding IDs.

Where to check in LoopsRecords you can audit

Loops the contact's event history

What changes

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

Loops

Server-side delivery

Upstack sends events to Loops from its servers only, so ad blockers and browser privacy settings can’t block delivery.

Loops

Identity-resolved events

Events sent to Loops 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.

You need a Loops account where you can create an API key with write access to events and contacts.

Upstack dashboardExample
Loops Destination Healthy
Read the full Loops setup guide
  1. 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.

  2. 02

    Add the Loops destination

    Under Destinations, add Loops with an API key created under Settings, API in your Loops account. It is the only credential the destination needs.

  3. 03

    Check events in Loops

    Trigger a test action on your store, such as viewing a product or adding to cart, and check Events in Loops. In Upstack, the Real-Time Events feed under System, Events Manager shows the events as delivered to Loops.

FAQ

Questions about Checkout Champ and Loops.

What permissions does the Loops API key need?

The key must have permission to write events and contacts, so Upstack can send events and create or update contacts.

Which events does Loops receive?

ViewContent as Viewed Product, AddToCart as Added to Cart, InitiateCheckout as Started Checkout and Purchase as Placed Order.

Which customer parameters are sent to Loops?

When Upstack identifies a visitor, it attaches the contact’s email and other known properties, and syncs profile properties including name, email and location to Loops.

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

Trigger a test action on your store, such as viewing a product or adding to cart, and check Events in Loops. In Upstack, the Real-Time Events feed under System, Events Manager shows the events as delivered to Loops.

How long does it take to connect Checkout Champ to Loops?

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

Related connectors

See all 408 connectors

Get Checkout Champ talking to Loops.

A 15-minute walkthrough of this connector on your own account.

21-day free trial, no card. Month to month.