Mixpanel cohorts as a source
Sync Mixpanel cohort membership into getuserfeedback.com so the same audience definitions drive flow (survey) targeting.
- Last reviewed
Mixpanel cohorts as a source
Use this when you already define audiences in Mixpanel and want those same audiences to drive who sees a flow.
Every cohort sync run in Mixpanel posts membership to getuserfeedback.com. Flow targeting can filter by cohort membership, and members are added or removed automatically as the cohort changes in Mixpanel.
1. Create the integration
- Open Integrations and click New integration.
- Under Data in, choose Mixpanel Cohorts.
- Click Continue.
On the detail page you'll see three values to copy:
- Webhook URL —
https://mixpanel.ingest.getuserfeedback.com/int_<id> - Username — the integration ID
- Password — a generated secret. Copy it now.
The password is what authenticates Mixpanel as the caller. Treat it like an API key.
2. Connect from Mixpanel
- In Mixpanel, go to Settings → Integrations → Cohort Syncs: Custom Webhook.
- Paste the Webhook URL from step 1.
- Choose Basic Auth and paste the Username and Password.
- Save.
3. Sync a cohort
- Open the cohort you want to send.
- Click Sync and pick the webhook destination you just created.
- Save.
4. Verify it's working
Open Users in getuserfeedback.com and filter by the cohort segment. The initial sync usually takes a few minutes. After that, Mixpanel pushes updates every 30 minutes.
Field mapping
For a new integration, your active Identity Resolution configuration determines the first mapping:
- If the active configuration accepts the canonical Mixpanel
External ID,
mixpanel_distinct_idmaps to External ID (mixpanel_distinct_id). - If canonical is not accepted but
userIdis accepted, it maps touserIdfor compatibility with your active configuration. - If the active configuration accepts neither identity, setup stops before the integration is created. Contact support to activate a compatible configuration, then try again.
If you don't have an active Identity Resolution configuration yet, setup uses
your current settings instead. If those settings accept neither identity,
enable the canonical Mixpanel External ID or userId in Settings → Identity
resolution, then try again.
If Identity Resolution changes while setup is finishing, no integration is created. Retry once so setup can use the current configuration.
The remaining default mappings are:
| Mixpanel field | getuserfeedback.com field |
|---|---|
email | traits.email |
first_name | traits.firstName |
last_name | traits.lastName |
phone_number | traits.phone |
Existing integrations keep the mapping they were created with. Identity Resolution is checked only when creating a new integration.
What can break
- 401 in Mixpanel logs. The basic auth username or password is wrong. Copy both again from the integration detail page. The password is the only one you can rotate.
- Members appear but traits don't. Check that the Mixpanel profile uses the property names in the table. Other property names aren't mapped automatically.
- Integration paused. Paused integrations reject inbound traffic and Mixpanel surfaces 4xx in its delivery logs. Resume from Integrations.