WooCommerce + Meta Ads + PostHog

More ad spend. Fewer orders. Where is the gap?

Connect WooCommerce, Meta Ads and PostHog to Hendrik. Separate ad performance, website behavior and store revenue before changing your budget.

See Hendrik at work

WooCommerce + Meta Ads + 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. Net order value fell from $96,000 to $93,000 while refunds rose from $5,600 to $7,900. Meta Ads: spend rose from $21,000 to $26,000 while platform conversion value rose from $71,000 to $82,000. PostHog: checkout-completed events fell from 1,360 to 1,160.

MetricPreviousCurrent
WooCommercenet order value (USD, all store channels, 28 days)96,000 USD93,000 USD
Meta Adsreported conversion value (USD, 28 days)71,000 USD82,000 USD
PostHogcheckout-completed events (count, 28 days)1,3601,160
WooCommercerefund value (USD, orders from the prior 28-day cohort)5,600 USD7,900 USD
Meta Adsspend (USD, consecutive 28-day periods)21,000 USD26,000 USD

What Hendrik checks

  1. Read the WooCommerce commercial result

    Compare completed net orders and refunds. This is the store outcome, not an attribution result.

  2. Review Meta Ads delivery

    Check spend, impressions, clicks, conversion definition, and conversion value inside Meta Ads; its reporting is specific to that platform.

  3. Use PostHog for the journey question

    It shows whether the checkout journey weakened before the store recorded its order result. It does not map an ad interaction to an order by itself.

  4. Test the operational explanation

    Check the landing page, checkout, tracking, price, and refund policy change log for the same period before choosing a campaign action.

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

How Hendrik handles your data

Want Hendrik to answer this with your data?

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 WooCommerce orders and refunds for the same store and comparison window.
  • Connected Meta Ads account with delivery and conversion reporting for the stated 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.
  • Meta attribution remains separate from store, payment, or CRM outcomes; do not sum it with another platform’s conversion value.
  • Captured events depend on instrumentation and coverage; they do not automatically identify a payment, order, or campaign.
  • Do not combine Meta Ads conversion value with WooCommerce net orders. A campaign-to-order claim needs a documented identifier and matching conversion window.

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