Shopify
Orders, refunds, payment status, product cost coverage, and location inventory show what happened in the store.
How to connect ShopifyShopify + PostHog
Did a product or journey change show up before Shopify orders moved?
Connect Shopify and PostHog to Hendrik. Use PostHog journey and release context to test whether a product change helps explain a Shopify order movement.
See Hendrik at work
Shopify + PostHog 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 |
|---|---|---|
| Shopifynet order value (USD, 28 days) | 110,000 USD | 106,000 USD |
| PostHogcheckout-completed events (count, 28 days) | 1,360 | 1,160 |
| Shopifyrefund value (USD, orders from the prior 28-day cohort) | 6,800 USD | 9,200 USD |
What Hendrik checks
Order and refund cohorts
Compare Shopify net order value with refunds by original order cohort. Keep paid status and the store currency visible.
Event and release context
Check PostHog event definition, instrumentation coverage, feature-flag exposure, annotations, and session scope before interpreting a journey change.
Explain the divergence
Shopify: net order value (USD, 28 days) changed from 110,000 USD to 106,000 USD. PostHog: checkout-completed events (count, 28 days) changed from 1,360 to 1,160. 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 dataWant Hendrik to answer this with your data?
One analysis, different integrations
What each integration adds
PostHog
Events, sessions, releases, and feature flags show whether the product or checkout journey changed.
How to connect PostHogConnect your stack
Set up each integration in one workspace.
- 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
What you need
- Use one explicit 28-day comparison window, time zone, market, and legal-entity scope before comparing values.
- Connected Shopify order, refund, and inventory data for the same store and comparison window.
- Connected PostHog project with the relevant event definition and capture coverage.
- 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
- Declared UTM text is not a verified ad-platform campaign identity; cost coverage and provenance control any margin claim.
- Captured events depend on instrumentation and coverage; they do not automatically identify a payment, order, or campaign.
- A parallel PostHog event and Shopify order movement does not prove the release caused the outcome.
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