Connect PostHog to PostgreSQL

Add your PostHog API key and instance base URL, save your PostgreSQL connection details, then pair both systems in a datastream. The explicit base URL supports US, EU, and self-hosted PostHog deployments.

Build PostgreSQL tables with the Records metric and dimensions such as UTM Campaign, Date, Hour of the day, Week of the year, Month of the year, Quarter of the year, and Year. You can select and rename the columns before writing them.

Catchr follows the next URL returned by PostHog to retrieve additional event pages because limit and offset are not reliable for historical paging. Available history and recurring load frequency depend on the PostHog API and your Catchr plan.

Select the PostHog Date dimension as the job's date field. Catchr can then delete and rewrite the scheduled window, helping limit duplicate rows when successive loads overlap.

Use the Records metric to count exported events, then group results by UTM Campaign or time dimensions such as Date, Hour, Week, Month, Quarter, and Year. This supports reusable PostgreSQL queries and views for campaign and activity reporting.

Yes. Connect an existing PostgreSQL database first. The Catchr job creates and populates the destination table you configure inside that database.

Yes. Create a separate datastream and job for each source, write each export to its own table, then combine the data downstream with SQL, views, or your BI tool.