WooCommerce + Google Ads + Google Merchant Center + PostHog

Is Shopping losing eligible products or potential buyers?

Connect WooCommerce, Google Ads, Google Merchant Center and PostHog to Hendrik. Distinguish catalog eligibility, paid delivery, buyer journey, and completed store revenue.

Start with this stackBook a founder demo

See Hendrik at work

WooCommerce + Google Ads + Google Merchant Center + 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. Merchant Center counts are two dated snapshots, not period totals. Eligibility fell from 1,240 to 1,010 offers. Inspect disapproval reasons and affected products before deciding whether this explains the delivery change.

MetricPreviousCurrent
WooCommercenet order value (USD, all store channels, 28 days)96,000 USD93,000 USD
Google Adsreported conversion value (USD, 28 days)88,000 USD105,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
Google Adsspend (USD, consecutive 28-day periods)21,000 USD26,000 USD
Google Merchant CenterEligible offers · same account, country and Shopping destination; period-end snapshots1,240 · 28 Jan1,010 · 25 Feb

What Hendrik checks

  1. Read WooCommerce outcome

    Use net orders and refunds as the completed commercial result.

  2. Review Google Ads delivery

    Check campaign spend, clicks, conversion settings, and operator changes.

  3. Inspect Merchant Center eligibility

    The third integration adds dated feed, approval, price, availability, and policy diagnostics for offers.

  4. Use PostHog for the journey

    The fourth integration adds whether the checkout journey weakened before the store recorded its order result, which separates a catalog question from a buyer-journey question.

  5. Validate affected scope

    Verify whether diagnosed offers were promoted before connecting a feed repair to a Google Ads decision.

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 WooCommerce orders and refunds for the same store and comparison window.
  • Connected Google Ads account with spend and conversion reporting for the stated window.
  • Connected Merchant Center account with offer diagnostics for the same market and product scope.
  • 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.
  • Google-reported conversion value is platform attribution, not incremental revenue or a deduplicated business total.
  • Offer diagnostics do not prove a store-product or campaign relationship unless that mapping is established.
  • Captured events depend on instrumentation and coverage; they do not automatically identify a payment, order, or campaign.
  • These integrations can be compared by date and product scope, but they do not automatically map an ad click to an order or establish causality.

Works better together

Find more combinations
  • WooCommerce
  • Google Ads

Google Ads looks stronger. Are WooCommerce sales up too?

Connect WooCommerce and Google Ads to Hendrik. Check whether Google Ads reported conversion value agrees with WooCommerce store-level net order and refund movement.

See WooCommerce + Google Ads
  • Google Ads
  • Google Merchant Center

Is Shopping down because offers are ineligible or because ads are underperforming?

Connect Google Ads and Google Merchant Center to Hendrik. Distinguish Google Ads Shopping delivery from Merchant Center offer eligibility before changing Shopping bids.

See Google Ads + Google Merchant Center
  • Google Ads
  • PostHog

Did Google Ads change, or did the product journey change after the click?

Connect Google Ads and PostHog to Hendrik. Use PostHog event and release context to check whether a Google Ads performance change is paired with a product-journey change.

See Google Ads + PostHog

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