Send Releaseo events to PostHog
Connect PostHog with a project token, choose which widget events to forward for each environment, and check delivery in the logs.
The PostHog integration sends events from your Releaseo widget to your PostHog project in batches, so you can analyze how people interact with changelog posts, CTAs, and the contact form alongside the rest of your product analytics. Each environment (Production, Stage, and Development) has its own settings.
Before you start
You need a PostHog project token. It starts with
phc_and you'll find it in PostHog under Project settings.Personal API keys won't work. They can't receive events.
Connect PostHog
Open Integrations in the sidebar and find PostHog under Analytics.
Select Connect.
Choose the Environment: Production, Stage, or Development.
Under PostHog endpoint, pick US Cloud, EU Cloud, or Custom. If you self-host PostHog, choose Custom and enter your Ingestion endpoint. US Cloud uses
https://us.i.posthog.com.Paste your Project token. The token is write-only, so it isn't shown again after you save.
Select Save PostHog settings, then turn on the delivery toggle at the top of the panel.
Choose what to send
Send SDK events forwards the widget events you select in the Events list. On by default.
Send identify events sends identify calls so events are linked to known users in PostHog. On by default.
Forward custom events also sends the custom events you've set up in Releaseo. Off by default.
Rate limit per minute caps how many events are delivered each minute. The default is 1,000.
Events you can send:
SDK initialized (
sdk_init)Widget loaded (
widget_loaded)Widget opened (
widget_open)Widget closed (
widget_closed)Post viewed (
post_open)CTA clicked (
cta_click)Link clicked (
link_clicked)Contact CTA clicked (
home_contact_cta_clicked)Read state changed (
read_state_changed)Contact submission created (
contact_submission_created)
All events are selected by default except SDK initialized and Read state changed.
Test and monitor delivery
In Delivery logs, select Test connection to send a test event.
Check each delivery's status, number of events, HTTP response, attempts, duration, and any error.
Open your PostHog project and confirm the events show up.
Troubleshooting
Events aren't arriving: make sure you used a project token (
phc_...), not a personal API key, and that the endpoint matches your PostHog region.The delivery toggle is disabled: save a project token first. Delivery can't be enabled without one.
"PostHog settings could not be loaded": close the panel and open it again.
Was this article helpful?
Still stuck? Contact us and mention this article.