Understanding Mixpanel Cohort Sync Actions in Kapa.ai

Avinash K. · 2025-04-23 13:42:31.998746+00

In mixpanel cohort sync , if i updated the conditions in an existing cohort, which is being synced via webhook and sync is recurring. in this case, will i get a "members" action or "add_members", "remove_members" action for the removed/added members in updated cohort?

When you update the conditions in an existing cohort that's being synced via webhook with a recurring sync, Mixpanel will send the differences (diffs) between the previous cohort state and the new cohort state. This means you'll receive: - add_members actions for users who newly qualify for the cohort based on your updated conditions - remove_members actions for users who no longer qualify for the cohort based on your updated conditionsMixpanel stores a snapshot of the cohort state from the last successful sync and uses this to compute the differences. These diffs are then sent to your webhook via the add_members and remove_members calls during the next scheduled sync (which occurs every 30 minutes).You would only receive a full members action in specific cases: 1. When the cohort is synced for the first time 2. If your webhook server was down (returning 429 or 5XX errors) for more than 3 days, causing the snapshot to expireAs explained in the documentation:

"Subsequent syncs include only differences in membership since the previous successful sync in order to preserve bandwidth, through a diffing mechanism."Mixpanel Webhook Sync Documentation

kapa.ai is still learning and improving, please let me know how I did by reacting below.

ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

2 comments