PostHog + Salesforce

Did product activity turn into Salesforce leads and opportunities?

Connect PostHog and Salesforce to Hendrik. Test whether a PostHog journey or flagged release change aligns with Salesforce lead and opportunity movement.

Start with this stackBook a founder demo

See Hendrik at work

PostHog + Salesforce review

Previous: 1–28 January. Current: 29 January–25 February. Both periods contain 28 days. Monetary values use USD and all timestamps use UTC. The example compares acquisition measures with CRM deal progression. A submitted lead and a qualified deal are different events, with different reporting dates. The selected website event is a lead form submission.

MetricPreviousCurrent
PostHoglead_submitted events · selected form (count, 28 days)230250
Salesforcequalified opportunities created (count, 28 days)2824

What Hendrik checks

  1. Event and release context

    Check PostHog event definition, instrumentation coverage, feature-flag exposure, annotations, and session scope before interpreting a journey change.

  2. Opportunity and campaign definition

    Check Salesforce record type, stage history, campaign membership, and identity coverage before using opportunity movement.

  3. Explain the divergence

    PostHog: lead_submitted events · selected form (count, 28 days) changed from 230 to 250. Salesforce: qualified opportunities created (count, 28 days) changed from 28 to 24. 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 data

Want Hendrik to answer this with your data?

Start with this stackBook a founder demo

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 PostHog project with the relevant event definition and capture coverage.
  • Connected Salesforce org with agreed lead, opportunity, and stage definitions.
  • 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

  • Captured events depend on instrumentation and coverage; they do not automatically identify a payment, order, or campaign.
  • CRM campaign and opportunity records require an established identity relationship before attribution claims.
  • A PostHog person is not automatically a Salesforce lead or opportunity.

Your data. Your next step.

Put Hendrik to work on your stack.

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

Start with this stackBook a founder demo
See plans and pricing