Mixpanel
Connect Mixpanel to getuserfeedback.com in either direction — sync cohorts in, send flow (survey) events out, or both.
- Last reviewed
Mixpanel
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.
- A getuserfeedback.com workspace, with access to Integrations.
Identity model
For a newly created cohort-source integration, Mixpanel distinct_id maps to
the External ID mixpanel_distinct_id when the workspace's active Identity
Resolution configuration accepts that identity. Before an active configuration
exists, current Identity Resolution settings are used instead. Workspaces that
accept userId but not the canonical identity keep the legacy userId mapping;
setup stops before creation if neither is accepted. Existing integrations keep
their configured mapping. 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.