Home
Connectors
Checkout Champ - PostHog

Send Checkout Champ funnel events to PostHog

Q: How does Upstack identify users in PostHog?

Upstack assigns each visitor a consistent distinct_id that persists across sessions, devices and browsers when it can resolve the visitor’s identity. Anonymous visitors get a temporary ID that Upstack tries to merge once the visitor is identified.

Q: Will I see duplicate events if I also have PostHog installed via another method?

Possibly. If PostHog’s JavaScript snippet or another integration sends the same events, you may see duplicates, so disable overlapping event types in either Upstack or the other integration.

Q: Which events does PostHog receive?

PageView as $pageview, ViewContent as view_item, AddToCart as add_to_cart, InitiateCheckout as initiate_checkout and Purchase as purchase.

Q: Which customer parameters are sent to PostHog?

Each event carries Upstack’s resolved distinct_id, which persists across sessions, plus email when the visitor is identified, IP address, user agent and device details.

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

Visit your store, view a product or add to cart, and confirm the event appears in PostHog under Activity, Live Events.

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

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

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

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 PostHog. 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 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 PostHog

Stream resolved product and commerce events into PostHog for analysis on a person, not a session.

See the PostHog integration

PostHogWhat it receives

distinct_idthe person, across devices
event name and propertiesfunnels and retention
$set person propertiesuser-level attributes

Which events reach PostHog

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

Upstack event	Sent to PostHog as
Page view	$pageview
Product view	view_item
Add to cart	add_to_cart
Checkout	initiate_checkout
Purchase	purchase

Each event carries Upstack’s resolved distinct_id, which persists across sessions, plus email when the visitor is identified, IP address, user agent and device details.

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 PostHogRecords you can audit

PostHog Activity

then check that a single person shows events from more than one device.

What changes

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

PostHog

Server-side delivery

Upstack always sends events to PostHog from its servers as well as through the PostHog snippet, so an event an ad blocker or browser privacy setting stops in the browser still arrives from the server.

PostHog

Identity-resolved events

Events sent to PostHog 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 your PostHog Project API Key from Project Settings and the data region, US or EU, where your project is hosted.

Upstack dashboardExample

PostHog Destination Healthy

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

Under Destinations, add PostHog with your Project API Key, which starts with phc_, and the Data Region (US or EU) that matches where your PostHog project is hosted.
03

Check Live Events in PostHog

Visit your store, view a product or add to cart, and confirm the event appears in PostHog under Activity, Live Events.

FAQ

Questions about Checkout Champ and PostHog.

How does Upstack identify users in PostHog?

Upstack assigns each visitor a consistent distinct_id that persists across sessions, devices and browsers when it can resolve the visitor’s identity. Anonymous visitors get a temporary ID that Upstack tries to merge once the visitor is identified.

Will I see duplicate events if I also have PostHog installed via another method?

Possibly. If PostHog’s JavaScript snippet or another integration sends the same events, you may see duplicates, so disable overlapping event types in either Upstack or the other integration.

Which events does PostHog receive?

PageView as $pageview, ViewContent as view_item, AddToCart as add_to_cart, InitiateCheckout as initiate_checkout and Purchase as purchase.

Which customer parameters are sent to PostHog?

Each event carries Upstack’s resolved distinct_id, which persists across sessions, plus email when the visitor is identified, IP address, user agent and device details.

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

Visit your store, view a product or add to cart, and confirm the event appears in PostHog under Activity, Live Events.

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

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