PostHog
Resolved events flow into your PostHog project with a consistent distinct_id — the anonymous visitor and the identified lead arrive as the same person, because identity was resolved before sending.
Data delivered
Data delivered
- Free-form events with full properties
- Visitor distinct_id (with lead fallback)
- Real event timestamps
What it is for
What you can do with it
- Analyze product funnels with the same events marketing uses
- Use PostHog Cloud US, EU or self-hosted (configurable host)
Why integrate
The business reason, not just the tech
Product and marketing watching the same event
Product analyzes funnels in PostHog; marketing fires ad conversions. With one event source feeding both, the "why is your number different" meeting is over.
Identity resolved before arrival
distinct_id arrives consistent: the anonymous visitor who became a lead is the SAME person in your funnel, no manual merges in PostHog.
Cloud US, EU or self-hosted
The host is configurable — events go to the instance you already run.
How to connect
Step by step
- Step 1
Copy the project token from your PostHog project.
- Step 2
Create the destination (host optional for EU/self-hosted).
- Step 3
Create a Delivery with the events you want to analyze.
Frequently asked questions
Do I need the PostHog SDK?
Not for these events — they enter through the capture API. The SDK can coexist; CDP events arrive with the same distinct_id for the same person.
Start measuring what actually becomes revenue
Create a free account, connect your first source and see your first lead timeline today. No card required.