PostHog
Connect PostHog and getuserfeedback.com in either direction.
- Last reviewed
PostHog
PostHog can connect in either direction. Use it as a source when PostHog already sees product activity you want to use for targeting. Use it as a destination when you want survey events from getuserfeedback.com to show up in PostHog.
| Direction | What it does | When to use |
|---|---|---|
| PostHog as a source | PostHog sends product events and person traits to getuserfeedback.com. | You want surveys to react to product activity you already capture in PostHog. |
| PostHog as a destination | getuserfeedback.com sends survey events to PostHog. | You want survey responses and flow activity in PostHog reports. |
What you need
- A PostHog project.
- For source setup: permission to create an HTTP Webhook destination in PostHog.
- For destination setup: your PostHog project API key.
- A getuserfeedback.com workspace, with access to Integrations.
Identity model
PostHog distinct_id becomes a user external ID in getuserfeedback.com. If the
webhook includes a PostHog person, the person ID is stored as a second external
ID and person properties become traits on the profile.
For events sent to PostHog, getuserfeedback.com uses userId first, then
anonymousId, as PostHog distinct_id.
Identities resolve into a single profile across every source you connect. See Identity resolution for how matching works.