Home
Connectors
Checkout Champ - Omnisend

Send Checkout Champ funnel events to Omnisend

Q: Which customer parameters are sent to Omnisend?

When Upstack identifies a visitor, it enriches the event with the contact’s email and any other known properties, and can create or update the contact in Omnisend.

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

Upstack marks the destination Healthy, and Audience or Reports in Omnisend shows contacts and events from Upstack Data, typically within a few minutes of a test purchase or page view.

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

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

Each event is resolved to a person against a 750M+ device graph before it reaches Omnisend, so flows trigger on a known profile rather than an anonymous session.

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 Omnisend. 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.
DeduplicationOne order produces one event, so a single purchase cannot trigger the same flow twice.
Bot and fraud filteringAutomated traffic never becomes a profile, so list quality and deliverability are not paying for it.

Messaging mistakes are expensive and public. These controls exist so a flow never fires against a profile that should not have received it.

03 Activate

Delivered to Omnisend

Resolved events and profiles into Omnisend for email and SMS automation.

See the Omnisend integration

OmnisendWhat it receives

email / phonecontact key
event propertiesworkflow triggers
cart / order valuerevenue attribution

The catch

Funnel checkouts sit outside the main storefront, so retention flows built around storefront events simply do not fire for them.

Where to check in OmnisendSending you can audit

Omnisend Audience the contact's activity

and the automation's own trigger log.

What changes

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

Omnisend

Server-side delivery

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

Omnisend

Identity-resolved events

Events sent to Omnisend 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 admin access to your Omnisend account, with permission to create API keys.

Upstack dashboardExample

Omnisend Destination Healthy

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

Under Destinations, add Omnisend with an API key created under Store settings, API in Omnisend: typically a 64 character secret followed by a hyphen and a short identifier. It is the only field the destination needs.
03

Check contacts and events in Omnisend

Upstack marks the destination Healthy, and Audience or Reports in Omnisend shows contacts and events from Upstack Data, typically within a few minutes of a test purchase or page view.

FAQ

Questions about Checkout Champ and Omnisend.

Which customer parameters are sent to Omnisend?

When Upstack identifies a visitor, it enriches the event with the contact’s email and any other known properties, and can create or update the contact in Omnisend.

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

Upstack marks the destination Healthy, and Audience or Reports in Omnisend shows contacts and events from Upstack Data, typically within a few minutes of a test purchase or page view.

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

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