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

  1. Open the PostHog guide from Dashboard → Integrations → Apps.
  2. Configure your recipe with the public host, ingestion token, and existing distinctId.
  3. Set trusted consent: granted.
  4. Send a link.clicked event from your recipe.
  5. 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.

Open Apps · Technical reference · All app guides