Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: PostHog integration always pass random distinct_id #3001

Open
Yshayy opened this issue Nov 27, 2024 · 0 comments
Open

[Bug]: PostHog integration always pass random distinct_id #3001

Yshayy opened this issue Nov 27, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Yshayy
Copy link

Yshayy commented 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:

# curl
curl -v -L --header "Content-Type: application/json" -d '{
    "api_key": "phc_6diyp44WAiUJmihs6aqexBb8jPp5TivvPVu02hXlpcC",
    "event": "request",
    "distinct_id": "ian@posthog.com"
}' https://us.i.posthog.com/capture/

Relevant log output

No response

Twitter / LinkedIn details

@Yshayy

@Yshayy Yshayy added the bug Something isn't working label Nov 27, 2024
@Yshayy Yshayy changed the title [Bug]: Posthog integration always pass random distinct_id [Bug]: PostHog integration always pass random distinct_id Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant