WooCommerce
Orders, refunds included in net order value, product history, customers, and current inventory show what happened in the store.
How to connect WooCommerceWooCommerce + PostHog
Did a product or journey change show up before WooCommerce orders moved?
Connect WooCommerce and PostHog to Hendrik. Test a PostHog journey change against WooCommerce store outcomes while preserving the missing identity and attribution boundaries.
See Hendrik at work
WooCommerce + 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 |
|---|---|---|
| WooCommercenet order value (USD, all store channels, 28 days) | 96,000 USD | 93,000 USD |
| PostHogcheckout-completed events (count, 28 days) | 1,360 | 1,160 |
| WooCommercerefund value (USD, orders from the prior 28-day cohort) | 5,600 USD | 7,900 USD |
What Hendrik checks
Order and refund dates
Compare WooCommerce net order value with refund creation and original-order timing. WooCommerce does not supply campaign attribution.
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
WooCommerce: net order value (USD, all store channels, 28 days) changed from 96,000 USD to 93,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 WooCommerce orders and refunds 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
- WooCommerce campaign attribution fields are unavailable; current data does not establish campaign revenue, historical COGS, settlement, or profit.
- Captured events depend on instrumentation and coverage; they do not automatically identify a payment, order, or campaign.
- PostHog events are not linked to WooCommerce campaign revenue by default.
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