Google Ads
Spend, delivery, and Google reported conversions show the Google Ads side of the question.
How to connect Google AdsGoogle Ads + Google Merchant Center + PostHog
Is Shopping losing eligible products or potential buyers?
Connect Google Ads, Google Merchant Center and PostHog 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 + 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.
| Metric | Previous | Current |
|---|---|---|
| Google Adsreported conversion value (USD, 28 days) | 88,000 USD | 105,000 USD |
| PostHogcheckout-completed events (count, 28 days) | 1,360 | 1,160 |
| Google Adsspend (USD, consecutive 28-day periods) | 21,000 USD | 26,000 USD |
| Google Merchant CenterEligible offers · same account, country and Shopping destination; period-end snapshots | 1,240 · 28 Jan | 1,010 · 25 Feb |
What Hendrik checks
Review Google Ads delivery
Compare spend, clicks, impression share, campaign type, and conversion settings within Google Ads.
Read the Merchant Center snapshot
The third integration adds catalog approval and diagnostics. Inspect disapproval reason, feed freshness, price, and availability for affected offers.
Use PostHog for journey coverage
PostHog adds whether the checkout journey weakened before the store recorded its order result; it cannot identify a Merchant issue as the cause.
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 dataWant Hendrik to answer this with your data?
One analysis, different integrations
What each integration adds
Google Merchant Center
Offer eligibility, policy issues, and feed diagnostics show whether Shopping can serve the products you want to promote.
How to connect Google Merchant CenterPostHog
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 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
- 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.
- 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