WooCommerce + Google Ads + Stripe

Did demand weaken, or did more payments fail?

Connect WooCommerce, Google Ads and Stripe to Hendrik. Compare ad delivery, store orders and payment collection to separate an acquisition problem from a checkout or payment problem.

See Hendrik at work

Ad reports rise. Collected payments fall.

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. Google Ads: spend rose from $21,000 to $26,000 while platform conversion value rose from $88,000 to $105,000. Stripe successful payments fell from $102,000 to $94,000.

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
Stripesuccessful payment amount (USD, 28 days)102,000 USD94,000 USD
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

What Hendrik checks

  1. Compare orders and refunds

    Check whether lower net order value comes from fewer orders, more refunds, or both. Match refunds to the orders they relate to.

  2. Check what Google Ads counts

    Review spend, conversion settings and account changes. A rise in reported conversion value can come from tracking changes rather than more paid orders.

  3. Check payment completion

    Compare successful payments, failures and refunds in Stripe. Find out whether fewer payments succeeded or the average payment amount fell.

  4. Match the reporting periods

    Confirm that Stripe and WooCommerce cover the same store, currencies and payment methods. Order dates and payment dates can differ.

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 Google Ads account with spend and conversion reporting for the stated window.
  • 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

  • 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.
  • Payments must not be added to storefront or marketplace revenue; transaction reconciliation needs a proven payment relationship.
  • Stripe payments and store orders may cover different scopes or dates. Do not claim that a specific Google Ads campaign produced a Stripe payment without documented identity and timing rules.

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