PostHog integration

Connect PostHog and Swoop watches the insights your team already saved, asking the people closest to a metric why it moved.

Why a human answer beats another chart

PostHog can tell you that a funnel step lost eight points on Tuesday. It cannot tell you that the onboarding copy changed on Monday, or that support has been fielding the same confusion for a week. Those facts exist, in people.

What Swoop watches

Read-only, and only what you point it at.

  • Saved insights you tick
  • Trends over time
  • Breakdowns as segments

History arrives on connect. PostHog can hand over past values, so signals can appear on the first sync rather than after a wait.

Goals you can track from this

Swoop reads what PostHog already reports and proposes a goal with your own numbers in it — a baseline, a target you can change, and who to ask about it each week. Nothing is asked of anyone until you accept one.

Activation rateWeekly active usersFunnel completion

What it asks, and who it asks

Questions are phrased from the change, never from a theory about the cause — a leading question gets you agreement instead of information.

The signal

A saved funnel drops several points week over week

It asks

What are you seeing at the invite step that the numbers wouldn't show?

Routed to: Whoever ships onboarding, plus anyone who has answered about activation recently

The signal

A feature's weekly actives fall after a release

It asks

What changed for people using this last week?

Routed to: The engineers and PMs on that surface

The signal

One segment diverges sharply from the rest

It asks

What do you know about this cohort that the segment definition misses?

Routed to: Growth, and the support people who talk to them

Usually answered by: Product, engineering and support — the people who changed something, or who heard about it first. Answering is free and unlimited on every plan — you are never billed for the people who reply.

Connecting it

A couple of minutes. A personal API key with read access, from your own PostHog profile. No admin needed.

  1. 01PostHog address

    Use https://eu.posthog.com for EU cloud, or your own address if self-hosted.

  2. 02Project ID

    In PostHog: Settings → Project. It's the number in the URL.

  3. 03Personal API key

    PostHog: your avatar → Personal API keys. Read access is enough.

  4. 04Choose what it may watch

    Every source states what it is allowed to look at. Ingesting everything available is how this becomes another dashboard nobody opens.

Credentials are stored in your own infrastructure and used read-only. Nothing is ever written back to PostHog, and answers are synthesized by an open-source model on Amazon Bedrock inside your own AWS account — no foundational-model vendor sees your data.

Connect PostHog and ask your first question

Free to start, and you only pay for panels that answer. A question nobody responds to, one that duplicates a live one, or one answered from what your people already told us costs nothing.

Start free

Other integrations