Google Ads
Spend, delivery, and Google reported conversions show the Google Ads side of the question.
How to connect Google AdsGoogle 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 Hendrik at work
Google 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.
| 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 |
What Hendrik checks
Conversion and delivery settings
Check Google Ads conversion actions, attribution window, change events, and campaign mix before interpreting reported value or leads.
Event and release context
Check PostHog event definition, instrumentation coverage, feature-flag exposure, annotations, and session scope before interpreting a journey change.
Explain the divergence
Google Ads: reported conversion value (USD, 28 days) changed from 88,000 USD to 105,000 USD. PostHog: checkout-completed events (count, 28 days) changed from 1,360 to 1,160. Compare the timing and definitions before attributing one change to the other.
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
PostHog
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 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.
- Captured events depend on instrumentation and coverage; they do not automatically identify a payment, order, or campaign.
- No Google Ads click-to-PostHog person relationship is assumed.
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