# PostHog integration for paid acquisition

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?

## Illustrative example

### Check whether a release changed the checkout journey

Same 7-day windows; no monetary figures are used.

*About this example: Synthetic data · illustrative analysis · Hendrik only acts with the permissions you give it.*

- Clicks (Google Ads): 18,000 → 18,400
- Checkout-start events (PostHog): 2,100 → 1,240
- Feature flag enabled (PostHog): 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.

### What Hendrik sees

Clicks stayed nearly flat while checkout starts fell after the feature flag was enabled.

### What to do next

Pause further spend expansion while the release owner reviews the checkout change.

**Limit:** The example identifies a testable explanation, not proof that the flag caused the drop.

## What PostHog contributes

Use PostHog with an advertising integration to check whether a release, feature flag, or funnel change came before a change in spend performance.

## Data Hendrik reads

- **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:** 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.
- **Accounts:** One PostHog region, organization, and project.
- **History:** The current product configuration defaults to 90 days. Hendrik shows the actual coverage after the first sync.
- **Refresh:** Configured data streams run from hourly to every 6 hours. Hendrik shows the published freshness for each source after sync.
- **Setup timing:** PostHog starts its initial sync after authorization, account selection, and data checks. The duration depends on the selected account and history.
- **Actions:** 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.
- **Availability:** Your workspace shows Connect or Request access for your account.

## What you need to connect

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

## Important limits

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

## Provider documentation

- [PostHog API](https://posthog.com/docs/api)

## Start with PostHog

[Create a workspace and connect PostHog](https://app.withhendrik.com/auth?mode=sign-up&acquisition_channel=marketing&return_to=%2Fonboarding%2Factivation&cta_location=integration_markdown&landing_page_id=integration-posthog&integration=posthog)