PostHog

What you need

A PostHog account with a project, on either region. Kwern connects as a public client with no secret: its client id is the address of a metadata document Kwern publishes, which is what PostHog reads to identify it.

Connect it

Open Settings · Add an account and press Connect PostHog. PostHog asks you to authorize four read scopes: your user, the organization, the projects and the query engine. Nothing that could create a dashboard, an insight, a feature flag or an event.

Kwern remembers which region your grant lives on and goes back to that host on every refresh, so a project in the EU is never queried against the US host.

Then open the product's Apps page, press Choose what Kwern reads and choose the PostHog project.

What Kwern reads

Three HogQL queries per sync, whatever the range. The snapshot itself holds only the host, the project id and its name; the numbers live in the connector's series:

• active users, new users, sessions, events
• paywall views and paywall viewers
• one line per event name your app sends, so nothing PostHog counts is left behind

The first sync reads the whole life of the project. Every later one re-reads the days since the last sync plus a week of overlap, because events arrive after the day they belong to.

What Kwern can change

Nothing. The grant is read-only and no proposal targets PostHog. The queries return counts; no person is read.

The agents that use it

No agent needs PostHog to run. It is where a marketing claim meets what people actually did, and what the Usage tab of Analytics charts. A product can bind a different PostHog project per product, and one account may hold several.

When it breaks

A revoked grant marks the account as needing attention. Reconnecting repairs it and puts back whatever the breakage paused. If your PostHog account moves region, reconnect: the host is part of the stored grant.

PostHog connector · All connectors · How a product is set up