Mixpanel
Connect Mixpanel to getuserfeedback.com in either direction — sync cohorts in, send flow (survey) events out, or both.
- Last reviewed
Mixpanel connects in two directions. Pick one or both.
| Direction | What it does | When to use |
|---|---|---|
| Mixpanel cohorts as a source | Mixpanel pushes cohort membership to getuserfeedback.com. | You want to target flows at audiences you already define in Mixpanel. |
| Mixpanel as a destination | getuserfeedback.com streams flow events to Mixpanel. | You want flow responses to live in Mixpanel alongside the rest of your product events. |
What you need
- A Mixpanel project.
- Permission to add an integration in the Mixpanel project.
- Workspace admin access in getuserfeedback.com to add and manage integrations in Integrations.
Identity model
For a newly created cohort-source integration, Mixpanel distinct_id maps to
the External ID mixpanel_distinct_id. Creation adds its identity rule if
missing, with a default limit of one distinct ID ever, while preserving existing
rules' limits and priorities. This applies going forward; it does not start
historical reprocessing. Existing integrations keep their configured mapping,
including legacy userId mappings. See
cohort source setup for details.
Common Mixpanel properties — email, first_name,
last_name, phone_number — map onto traits.email, traits.firstName,
traits.lastName, and traits.phone by default. Identities resolve into a
single profile across every source you connect; see Identity
resolution.
Pick a direction
In this section
Mixpanel cohorts as a source
Sync Mixpanel cohort membership into getuserfeedback.com so the same audience definitions drive flow (survey) targeting.
Mixpanel as a destination
Send flow (survey) events from getuserfeedback.com into Mixpanel so responses live alongside your product analytics.