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.
How it flows
01 Capture
Not on the list? Send events to Upstack from any stack over webhook or direct post, with the same schema and the same resolution.
See the Custom stack integration
Custom stack event_namewhatever you choose to call ituser identifiersany of email, phone, external IDvalue / currencyif the event carries revenuecustom propertiesany attribute in your own schema02 Understand
Every Custom stack 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
customer_typeNew or returning, resolved before send.A CRM is only as trustworthy as its worst duplicate. These controls exist so the record reflects the person.
03 Activate
Stream resolved product and commerce events into PostHog for analysis on a person, not a session.
See the PostHog integration
PostHog distinct_idthe person, across devicesevent name and propertiesfunnels and retention$set person propertiesuser-level attributesEach 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
PostHog Activity
then check that a single person shows events from more than one device.
What changes
PostHog
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
Events sent to PostHog carry the resolved customer whenever Upstack can identify one, matched against a 750M+ device graph.
Custom stack
Headless, custom checkout, native app or a platform we haven’t listed: if it can make an HTTP request, it can send to Upstack.
Custom stack
Custom events are resolved, filtered and forwarded exactly like a Shopify order.
Setup
You need your PostHog Project API Key from Project Settings and the data region, US or EU, where your project is hosted.
01
Not on the list? Send events to Upstack from any stack over webhook or direct post, with the same schema and the same resolution.
02
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
Visit your store, view a product or add to cart, and confirm the event appears in PostHog under Activity, Live Events.
FAQ
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.
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.
PageView as $pageview, ViewContent as view_item, AddToCart as add_to_cart, InitiateCheckout as initiate_checkout and Purchase as 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.
Visit your store, view a product or add to cart, and confirm the event appears in PostHog under Activity, Live Events.
Related connectors
A 15-minute walkthrough of this connector on your own account.
21-day free trial, no card. Month to month.
Loops 
ActiveCampaign 
Meta Conversions API 
Google Ads Conversions 
TikTok Events API 
Funnelish 
Lasso Commerce 
Phoenix Technologies 
Skio 
Loop Subscriptions 
Stripe