You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When integrating PostHog, the Helicone-User-Id should serve as the distinct_id (or at least, should be configurable) as distinct_id use to define the identity linked to the event.
The current behavior create lots of identities/persons entities in PostHog.
Yshayy
changed the title
[Bug]: Posthog integration always pass random distinct_id
[Bug]: PostHog integration always pass random distinct_id
Nov 27, 2024
What happened?
When integrating PostHog, the Helicone-User-Id should serve as the distinct_id (or at least, should be configurable) as distinct_id use to define the identity linked to the event.
The current behavior create lots of identities/persons entities in PostHog.
Reference:
https://posthog.com/tutorials/api-capture-events
From the basic example:
Relevant log output
No response
Twitter / LinkedIn details
@Yshayy
The text was updated successfully, but these errors were encountered: