PostHog integration
Connect PostHog to Hendrik.
Hendrik reads your PostHog events, persons, cohorts, feature flags, annotations, insights, and sessions so you can compare paid traffic with product and website journeys.
Questions Hendrik can help answer
- Did a release or flag change the landing or checkout journey?
- Which event definition is reliable enough to use?
- Does the funnel result support a campaign pause or product fix?
PostHog + Google Ads example
Check whether a release changed the checkout journey
Same 7-day windows; no monetary figures are used.
| Metric | Previous | Current |
|---|---|---|
| Google AdsClicks | 18,000 | 18,400 |
| PostHogCheckout-start events | 2,100 | 1,240 |
| PostHogFeature flag enabled | false | true |
What Hendrik checks
Validate event instrumentation
Check that the event remained defined and emitted consistently.
Review flag exposure
Confirm the audience and activation date.
Check landing mix
Rule out a material traffic-source or landing-page shift.
About this example Synthetic data · Illustrative analysis · Changes require your approval.
How Hendrik handles your dataWant Hendrik to answer this with your data?
Your connected data
What Hendrik reads from PostHog
Use PostHog with an advertising integration to check whether a release, feature flag, or funnel change came before a change in spend performance.
- Events
- Captured product and web events.
- Feature flags
- Flag configuration and exposure context.
- Insights
- Saved product analysis context.
- Cohorts
- Defined user groups.
- Sessions
- Captured session data.
Setup and access
Setup and access for PostHog
- Setup
- When available, sign in with PostHog, confirm the region, organization, and project, then approve creation of the Hendrik Batch Export resources.
- Permissions
- PostHog OAuth read permissions for annotations, cohorts, feature flags, insights, persons, and projects, plus Batch Export and integration permissions to create Hendrik's export resources.
- Supported accounts
- One PostHog region, organization, and project.
- Available history
- The current product configuration defaults to 90 days. Hendrik shows the actual coverage after the first sync.
- Data refresh
- Configured data streams run from hourly to every 6 hours. Hendrik shows the published freshness for each source after sync.
- Setup time
- PostHog starts its initial sync after authorization, account selection, and data checks. The duration depends on the selected account and history.
- Can Hendrik make changes?
- Hendrik reads your PostHog data. Setup creates the approved Batch Export resources that move that data into Hendrik. It does not change your product events or feature flags.
- Integration availability
- Your workspace shows Connect or Request access for your account.
Requirements and data limits
What you need
- Confirm the customer’s PostHog project and event definitions.
- Check consent and event coverage for the relevant period.
- Verify whether a release, flag, or annotation changed.
Keep these differences in mind
- PostHog here means the customer’s data, not Hendrik telemetry.
- Captured events can be incomplete or affected by instrumentation changes.
- Person identity must be established before linking to CRM or commerce records.
- The example identifies a testable explanation, not proof that the flag caused the drop.
Your data. Your next step.
Put Hendrik to work on your stack.
Create your account, choose your workspace and connect your data.
See plans and pricing