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

You need workspace admin access to create an integration.

1. Open Integrations and click Add integration.
2. Under Data in, choose Mixpanel Cohorts.
3. Click Create integration.

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

1. In Mixpanel, go to Settings → Integrations → Cohort Syncs: Custom Webhook.
2. Paste the Webhook URL from step 1.
3. Choose Basic Auth and paste the Username and Password.
4. Save.

3. Sync a cohort

1. Open the cohort you want to send.
2. Click Sync and pick the webhook destination you just created.
3. 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

New integrations map mixpanel_distinct_id to the Mixpanel external identifier, externalId.users.none.mixpanel_distinct_id. It isn't mapped to your app's user ID.

Creating the integration adds that identifier to your identity rules if it's missing, with a limit of 1 ever. Existing limits and priorities stay as you set them. This applies to incoming data without reprocessing existing profiles.

If identity settings change while setup is finishing, creation is refused. Refresh the page before trying again.

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 their original mappings, including older mappings to userId.

While the integration exists, its required identifier cannot be removed from identity rules. You can still change its limit and priority. Pausing the integration keeps this requirement; deleting it releases the requirement only if no other integration uses that identifier. Deletion doesn't remove the rule or reset its tuning.

See Changing identity rules to choose whether a rule change should also reprocess existing data.

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.

Next

• Send flow events to Mixpanel
• Targeting and segments