Use Hoko with PostHog
Hoko provides a manual PostHog recipe for capturing a consented link.clicked event. Configure PostHog with your own project credentials and run the recipe from your application or server. The project must have a public HTTPS host, and Hoko uses an existing distinctId. The Apps page does not create a PostHog connection.
Before you start
- Use a PostHog project with a public HTTPS host.
- Have the project ingestion token. Do not use a personal or admin token.
- Choose one existing, non-empty
distinctId. - Have the Hoko workspace and account identity used by your recipe.
Send an event
- Open the PostHog guide from Dashboard → Integrations → Apps.
- Configure your recipe with the public host, ingestion token, and existing
distinctId. - Set trusted
consent: granted. - Send a
link.clickedevent from your recipe. - Inspect the event in the project activity view.
Verify the result
Find the event in PostHog’s activity view. A click event is activity data. Record conversions separately in the provider flow that owns them.
Troubleshoot and clean up
An HTTP host or admin token is rejected. A blank or newly invented distinctId is rejected. Provider ingestion may take time to appear. Remove the recipe credentials when you stop using the integration.