Meta Ads
Spend, delivery, and Meta reported conversions show the Meta Ads side of the question.
How to connect Meta AdsMeta Ads + PostHog
Did Meta change, or did the product journey change after the click?
Connect Meta Ads and PostHog to Hendrik. Test whether Meta Ads delivery changes coincide with a PostHog journey or feature-flag change.
See Hendrik at work
Meta 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 |
|---|---|---|
| Meta Adsreported conversion value (USD, 28 days) | 71,000 USD | 82,000 USD |
| PostHogcheckout-completed events (count, 28 days) | 1,360 | 1,160 |
| Meta Adsspend (USD, consecutive 28-day periods) | 21,000 USD | 26,000 USD |
What Hendrik checks
Attribution and delivery mix
Check Meta attribution setting, conversion event, placements, audiences, and creative delivery before interpreting reported outcomes.
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
Meta Ads: reported conversion value (USD, 28 days) changed from 71,000 USD to 82,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 Meta Ads account with delivery 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
- Meta attribution remains separate from store, payment, or CRM outcomes; do not sum it with another platform’s conversion value.
- Captured events depend on instrumentation and coverage; they do not automatically identify a payment, order, or campaign.
- Parallel delivery and event changes do not establish causal credit.
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