Connect PostHog
Daily users, sessions and events inside each app, next to its store downloads.
What it unlocks in StoreScope Analytics
- Daily users, sessions, events and page views inside each app, next to its store downloads.
The access it needs
| For | Least role or permission |
|---|---|
| Projects and usage queries | A personal API key with Project: Read and Query: Read |
- PostHog Cloud US or EU only; self-hosted PostHog is not supported yet. A project key (phc_) only sends events and cannot read.
Steps
- In PostHog, Settings, Personal API keys, create a key with read access to Project and Query. Open PostHog API keys
- Name each PostHog project like its app (or let its website's pageviews land in it). Each app gets its project by itself.
- In StoreScope Analytics, open Connections, choose PostHog, fill in the form and save. The connection is checked live with the store first; a connection that fails the check is never saved.
What the form asks for
| Field | Note | |
|---|---|---|
| PostHog Cloud region | required | us or eu (self-hosted PostHog is not supported yet) |
| Personal API key | required |
Keys and secrets are stored encrypted and used only for your workspace. Only the non-secret fields are shown back.
Errors the check can show
The exact sentence the Connections page shows, then what to do. Italic words are filled in with your own values.
Region must be us or eu (PostHog Cloud).
Type us or eu: the region in your PostHog address.
Personal API key is required.
Create one in PostHog, Settings, Personal API keys.
That is a project key (phc_), which only sends events. Create a personal API key (phx_).
Create a personal API key.
That does not look like a PostHog personal API key (phx_...).
Copy the whole key, with no spaces.
PostHog US or EU refused the key: check the region and that it is a personal API key.
The key belongs to the other region, or it was deleted.
The key has no read access to projects: give it Project read and Query read.
Edit the key's scopes in PostHog.
The key works but sees no project.
The key's organisation has no project the key may read.
PostHog answered status.
PostHog answered something unexpected. Try again in a few minutes.
Errors any connection can show are on Connect your stores.