Google Ads + Google Merchant Center + Google Analytics 4

Is Shopping losing eligible products or potential buyers?

Connect Google Ads, Google Merchant Center and Google Analytics 4 to Hendrik. Test whether a Shopping catalog constraint or a paid-journey change needs attention before increasing Google spend.

See Hendrik at work

Google Ads + Google Merchant Center + Google Analytics 4 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
Google Adsreported conversion value (USD, 28 days)88,000 USD105,000 USD
Google Analytics 4reported purchase events (count, 28 days)1,4201,230
Google Adsspend (USD, consecutive 28-day periods)21,000 USD26,000 USD
Google Analytics 4GA4 paid sessions (configured channel group, consecutive 28-day periods)16,80015,300
Google Merchant CenterEligible offers · same account, country and Shopping destination; period-end snapshots1,240 · 28 Jan1,010 · 25 Feb

What Hendrik checks

  1. Review Google Ads delivery

    Compare spend, clicks, impression share, campaign type, and conversion settings within Google Ads.

  2. Read the Merchant Center snapshot

    The third integration adds catalog approval and diagnostics. Inspect disapproval reason, feed freshness, price, and availability for affected offers.

  3. Use Google Analytics 4 for journey coverage

    Google Analytics 4 adds whether fewer paid visits or fewer recorded purchases appear before the store order is completed; it cannot identify a Merchant issue as the cause.

  4. Separate the interventions

    Record the date of any feed repair separately from bid, budget, or landing-page changes so the next comparison remains interpretable.

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 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 GA4 property with comparable acquisition and event reporting.
  • 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

  • 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.
  • GA4 events and attribution do not automatically establish a paid order, payment, or campaign relationship.
  • Do not infer product-level delivery loss unless the operator verifies that affected offers were actually promoted.

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