PostHog
Connect PostHog to build dashboards on product analytics, sessions, and error tracking, by signing in or with a personal API key.
Read only access to one PostHog project. Sign in with PostHog, or paste a personal API key limited to that project. Flitch reads events, sessions and the things your team has built in PostHog, and never creates, edits, or deletes anything.
Objects
| Object | Fields |
|---|---|
| Events (last 30 days) | ID, timestamp, event, distinct ID, person ID, session ID, current URL, path, referring domain, browser, OS, device type, country |
| Sessions (last 30 days) | Session ID, distinct ID, start and end, duration, pageviews, autocaptures, bounce, entry and exit URL, entry path, channel type, referring domain, UTM source and campaign |
| Persons | ID, distinct IDs, properties, created, last seen, identified |
| Insights | ID, name, description, query, dashboards, created, last refreshed |
| Dashboards | ID, name, description, pinned, created, last viewed |
| Cohorts | ID, name, description, count, created |
| Feature flags | ID, key, name, active, filters, rollout, created |
| Experiments | ID, name, feature flag, start and end, created |
| Surveys | ID, name, type, questions, start and end, created |
| Session recordings | ID, distinct ID, start and end, duration, active seconds, clicks, key presses, console errors, start URL |
| Error tracking issues | ID, name, description, status, severity, first seen, assignee |
| Annotations | ID, content, date, scope, created |
| Actions | ID, name, description, steps, created |
| Event definitions | ID, name, description, last seen, verified, hidden |
| Property definitions | ID, name, type, numerical, verified, hidden |
Events and sessions are flattened into the columns above rather than carrying every property, so charts can group by them directly.
Scopes
Signing in asks for these read scopes, and a personal API key needs Read on the same:
query:read
person:read
insight:read
dashboard:read
cohort:read
feature_flag:read
experiment:read
survey:read
session_recording:read
error_tracking:read
annotation:read
action:read
event_definition:read
property_definition:readNo write scopes.
Connect
Find your region and project ID
Your region is the address you sign in at: us.posthog.com is US Cloud, eu.posthog.com is EU Cloud. The project ID is the number after /project/ in that address.
Create a key (API key only)
To use a key, in PostHog go to Settings → Personal API keys → Create personal API key. Limit it to the project, grant Read on the scopes above, and copy the phx_… key. PostHog shows it once.
Open Data
In app.flitch.io, open the Data page.
Add PostHog
Top right, click Add, pick PostHog.
Choose a method and connect
Pick Sign in with PostHog or Personal API key, choose the region, and enter the project ID. Then sign in, or paste the key and connect.
Pick objects and save
Tick the objects you want. Set a name. Save.
Each object becomes a dataset.
Refresh
Refresh is off by default. Every dashboard load runs a live query against PostHog. Enable refresh to schedule a background refresh and serve from cache between runs. See Refresh.
Events and sessions cover the last 30 days at the time of each refresh.
Disconnect
- In Flitch: open the connection from the Data page and delete it. Cache cleared.
- In PostHog: delete the personal API key in Settings → Personal API keys to cut off a key immediately. A sign-in connection stops working once you delete it in Flitch.
Troubleshooting
Every object fails. The project ID or region is wrong. Check the address you sign in at and the number after /project/, then add the source again.
One object returns a permission error. The key or sign-in is missing that object's read scope. Create a key with the scope, or reconnect.
Authentication failed. The key was deleted or the sign-in was revoked. Reconnect from the connection's settings.