PostHog + Stripe

Do PostHog checkout events line up with Stripe payments?

Connect PostHog and Stripe to Hendrik. Compare PostHog captured checkout events with Stripe payment, refund, and dispute data to test a checkout or measurement hypothesis.

Start with this stackBook a founder demo

See Hendrik at work

PostHog + Stripe review

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

MetricPreviousCurrent
PostHogcheckout-completed events (count, 28 days)1,3601,160
Stripesuccessful payment amount (USD, 28 days)102,000 USD94,000 USD

What Hendrik checks

  1. Event and release context

    Check PostHog event definition, instrumentation coverage, feature-flag exposure, annotations, and session scope before interpreting a journey change.

  2. Payment and refund scope

    Check Stripe payment, refund, dispute, and balance-transaction dates. Establish an order-to-payment reference before reconciliation.

  3. Explain the divergence

    PostHog: checkout-completed events (count, 28 days) changed from 1,360 to 1,160. Stripe: successful payment amount (USD, 28 days) changed from 102,000 USD to 94,000 USD. Compare the timing and definitions before attributing one change to the other.

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

How Hendrik handles your data

Want Hendrik to answer this with your data?

Start with this stackBook a founder demo

One analysis, different integrations

What each integration adds

Connect your stack

Set up each integration in one workspace.

  1. Create your Hendrik account. Choose a workspace for your business.
  2. Connect your data. Use each integration’s setup instructions above. Availability and permissions are shown in your workspace.
  3. 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

What you need

  • 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 Stripe account with payment, refund, and dispute data for the same legal entity.
  • Keep provider-specific definitions visible and use an identity or product mapping only where it is established for this workspace.

Keep these differences in mind

  • Captured events depend on instrumentation and coverage; they do not automatically identify a payment, order, or campaign.
  • Payments must not be added to storefront or marketplace revenue; transaction reconciliation needs a proven payment relationship.
  • PostHog events do not establish a Stripe transaction relationship without a proven reference.

Your data. Your next step.

Put Hendrik to work on your stack.

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

Start with this stackBook a founder demo
See plans and pricing