Funnelish to PostHog
Forward every Funnelish event to PostHog server-side, resolved to a person against a 750M+ device graph — so records and reporting reflect the person, not the device.
Connection
Connect Funnelish to PostHog with Upstack Data
Funnelish
Capture every Funnelish order and one-click upsell from the server, so funnel revenue is counted in full rather than at the first step.
Funnelish integrationPostHog
Stream resolved product and commerce events into PostHog for analysis on a person, not a session.
PostHog integrationWhat changes
What changes when Funnelish feeds PostHog.
Server-side delivery
Events reach PostHog through its server API, not the browser — so ad blockers, ITP and consent banners don’t cost you conversions.
Identity-resolved events
Every event sent to PostHog carries a resolved customer, matched against a 750M+ device graph.
Every event, server-side
Storefront and checkout events are captured from Funnelish on the server, independent of the browser.
One setup, every destination
Connect Funnelish once and forward to every ad platform, email tool and warehouse you run.
What actually moves
What Funnelish carries, and what PostHog needs.
Funnelish and PostHog describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what Funnelish can put on an event, the right is what PostHog can actually use.
Funnelish sends
- order_id
- Funnelish order, including the upsell sequence
- email / phone
- contact from the order form
- line_items
- initial offer plus every accepted upsell
- total / upsell_total
- the full amount taken, not the first step
- funnel_id / step
- which funnel and which step converted
- customer_type
- new or returning, resolved before send
PostHog receives
- distinct_id
- the person, across devices
- event name and properties
- funnels and retention
- $set person properties
- user-level attributes
Records you can audit
How you know it is working.
A CRM is only as trustworthy as its worst duplicate. These controls exist so the record reflects the person.
Per-record inspection
Trace any property back to the event that set it.Deduplication
One person, one record, across devices and identifiers.Bot and fraud filtering
Automated traffic never becomes a contact.
Where to check in PostHog
PostHogActivity, then check that a single person shows events from more than one device.
Related connectors
Other places Funnelish can send to.
- FunnelishMeta Conversions API
- FunnelishGoogle Ads Conversions
- FunnelishTikTok Events API
- FunnelishPinterest
- FunnelishSnapchat
- FunnelishReddit
- FunnelishMicrosoft Ads
- FunnelishX
Other sources that feed PostHog.
- ShopifyPostHog
- WooCommercePostHog
- BigCommercePostHog
- Checkout ChampPostHog
- RechargePostHog
- Custom stackPostHog
- Lasso CommercePostHog
- Phoenix TechnologiesPostHog
- SkioPostHog
- Loop SubscriptionsPostHog
- StripePostHog
- Everything PostHog can take12 sources feed PostHog, and the setup is the same for each one.PostHog integration
- How resolution worksEvery event matched against a 750M+ device graph before it is forwarded.Upstack Signal
- What it costsThree plans that scale with your order volume. Every connector is on every plan.See pricing
Get Funnelish talking to PostHog.
A 15-minute walkthrough of this connector on your own account.