Understanding Mixpanel Charges for Identify Events in Customer IO Migration

Hello all! We're currently migrating to using Customer IO Data Pipelines to pipe events etc. to Mixpanel. We've noticed that setting user properties are mapped to "identify" events on Mixpanel instead of just being handled in the background. My question is this: are these "identify" events considered the same as other customer events and will they be charged as such? Or are they treated separately?

2 comments

Calum M.
·
·
For reference, we've discovered this: Certain events and API updates are non-qualifying and excluded from the Monthly Events calculation:
Identify ($identify)
Create Alias ($create_alias)
Merge ($merge)
Opt In ($opt_in)
Session Recording Checkpoint ($mp_session_record)
User profile creation/updates"
This means that the "identify" events you're seeing from Customer.io Data Pipelines, which are used to set user properties, are not considered the same as other customer events for billing purposes. They are treated separately and are not charged as regular events. So "identify" events are used for user profile updates and identity management in Mixpanel, but they don't count towards your billable event volume
Vlad S.
·
·
are these "identify" events considered the same as other customer events and will they be charged as such
they are not
👍1