PostHog + Klaviyo

Did product activity and Klaviyo activity change together?

Connect PostHog and Klaviyo to Hendrik. Use PostHog captured journey data with Klaviyo message and flow context to test a lifecycle hypothesis.

See Hendrik at work

PostHog + Klaviyo review

Previous: 1–28 January. Current: 29 January–25 February. Both periods contain 28 days. Monetary values use USD and all timestamps use UTC.

Metric	Previous	Current
PostHogcheckout-completed events (count, 28 days)	1,360	1,160
Klaviyoflow-attributed orders (count, 28 days)	310	420

Event and release context
Check PostHog event definition, instrumentation coverage, feature-flag exposure, annotations, and session scope before interpreting a journey change.
Message and audience definition
Check Klaviyo attribution setting, send volume, audience, exclusions, flow changes, and message window before interpreting attributed value.
Explain the divergence
PostHog: checkout-completed events (count, 28 days) changed from 1,360 to 1,160. Klaviyo: flow-attributed orders (count, 28 days) changed from 310 to 420. Compare the timing and definitions before attributing one change to the other.

About this example Synthetic data · Illustrative analysis · Changes require your approval.

One analysis, different integrations

Events, sessions, releases, and feature flags show whether the product or checkout journey changed.

Flows, campaigns, and lifecycle activity show messages, audience changes, and repeat purchase context.

Connect your stack

Create your Hendrik account. Choose a workspace for your business.
Connect your data. Use each integration’s setup instructions above. Availability and permissions are shown in your workspace.
Ask your first question. Hendrik uses the available data and tells you when a comparison needs more history or more data.

Requirements and data limits

Use one explicit 28-day comparison window, time zone, market, and legal-entity scope before comparing values.
Connected PostHog project with the relevant event definition and capture coverage.
Connected Klaviyo account with the relevant message, flow, and attribution definitions.
Keep provider-specific definitions visible and use an identity or product mapping only where it is established for this workspace.

Captured events depend on instrumentation and coverage; they do not automatically identify a payment, order, or campaign.
Message attribution is observational and does not show that exposure caused a store, payment, or subscription outcome.
Message exposure and product events are not a causal or person-level match by default.

Your data. Your next step.

Create your account, choose your workspace and connect your data.