Product analytics

Connect PostHog to Sondola

Review product activity alongside subscriptions and cash, while keeping event counts and people counts distinct.

Read-only. Sondola never changes your data in PostHog.

Credential
API key
Refresh
Twice a day
How it connects
Pick the metric

What Sondola reads from PostHog

  • Events
  • Active users
  • First-seen people

The PostHog connector covers events, active users and first-seen people. It is a selectable-metric source: you choose what a metric reads after connecting the project. Sondola's PostHog recipes query data through HogQL.

What you need

  • A PostHog organization member with access to the intended project.
  • A personal API key with query:read and event_definition:read scopes.
  • The Project ID and the project's US Cloud or EU Cloud region.

Collection timing and the period a reading covers are separate. Check the source's data-through date as well as the metric's reporting period.

Connect PostHog in 4 steps

  1. Create a scoped personal API key

    In PostHog's account settings, open Personal API keys and create a key with query:read and event_definition:read. Copy the value when it is shown. Use the personal key requested by Sondola, rather than the project token used to send browser events.

  2. Confirm the project and region

    Find the Project ID in project settings or in the URL after /project/. Choose US or EU to match the cloud region where you sign in to PostHog.

  3. Enter the connection details and test

    In Sondola, open Settings, Connections, then Integrations and choose PostHog. Enter a Connection name, Personal API key and Project ID, select the Region, then choose Save and test. This check reads one event definition.

  4. Select and test the metric

    Choose the metric and what it should read from PostHog. Inspect the test result for the last complete period before saving. A successful event-definition check does not establish that a particular metric has data.

Enter credentials only in your Sondola workspace. Keep keys out of screenshots, public repositories and support messages.

Permissions

  • A personal API key with two scopes: query:read and event_definition:read.
  • The personal key, not the project token used to send browser events.

Refresh and first reading

Twice a day. Most tools refresh once or twice a day, and every number shows when it was read.

Limits and history

  • The reviewed connection form offers US and EU Cloud regions. It does not offer a custom host field for a self-hosted PostHog instance.
  • Collection runs on the declared schedule. PostHog ingestion delays or API errors can still delay the readings available for a period.
  • A fixed historical import window is not specified in the public connection help. Check the earliest period you need rather than assuming that all existing PostHog history has been imported.

Verify your first reading

  • In What it means, check whether the metric counts events, active users or first-seen people. More events do not necessarily mean more people.
  • In Where it comes from, confirm PostHog and compare the same completed period. Sondola's PostHog weekly recipes use weeks beginning on Monday.
  • Match the event definition and any source-side filters when comparing with a PostHog report. Check the captured date separately from the period covered.
  • Inspect Connection status and whether usable data has arrived. A connection check and a business reading are different results.
How to check a metric and its dates →

Troubleshooting

The connection test fails.

Confirm the personal key, its two required scopes, project access, Project ID and selected region. A valid key pointed at the wrong region or project is not a usable connection.

The test succeeds but the metric is empty.

Check the event or measure selected for the metric and whether the completed period contains the expected data. The connection test reads an event definition, not the final metric result.

The count differs from a PostHog report.

Match event counts versus people counts, the event definition, source-side filters and date boundaries. For weekly figures, compare a Monday-start week.

Provider documentation

PostHog personal API keys and scopes · PostHog API authentication and cloud regions

Readings missing or old? Read the setup and troubleshooting guide and the worked freshness example.

Related integrations

See your company clearly by Monday.

Apply in two minutes. Once you are in, your first numbers arrive minutes after you connect a tool.

Free for qualifying startups. Read-only.