LinkedIn Ads + PostHog

Did LinkedIn Ads change, or did the product journey change after the click?

Connect LinkedIn Ads and PostHog to Hendrik. Use PostHog form or journey data to test the site-side context for LinkedIn Ads lead reporting.

See Hendrik at work

LinkedIn 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
LinkedIn Adsreported leads (count, 28 days)	120	152
PostHoglead_submitted events · selected form (count, 28 days)	230	250

Lead definition and delivery
Check LinkedIn conversion rules, campaign and creative delivery, then compare the same lead definition across periods.
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
LinkedIn Ads: reported leads (count, 28 days) changed from 120 to 152. PostHog: lead_submitted events · selected form (count, 28 days) changed from 230 to 250. Compare the timing and definitions before attributing one change to the other.

About this example Synthetic data · Illustrative analysis · Changes require your approval.

One analysis, different integrations

Spend, lead volume, and delivery show the LinkedIn Ads side of the question.

Events, sessions, releases, and feature flags show whether the product or checkout journey changed.

Connect your stack

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

Use one explicit 28-day comparison window, time zone, market, and legal-entity scope before comparing values.
Connected LinkedIn Ads account with lead and delivery 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.

A platform lead is not automatically a qualified lead, deal, or paid customer.
Captured events depend on instrumentation and coverage; they do not automatically identify a payment, order, or campaign.
A LinkedIn lead count is not automatically a PostHog person or event match.

Your data. Your next step.

Create your account, choose your workspace and connect your data.