Gabe

kapa.ai is this an acceptable implementation plan? am I missing anything that you can spot? is there anything I'm missing in terms of previously active users without profiles but who have tracked events in mixpanel already? Users should be properly identified by their distinct id tied to their account id on account registration and log in. User profile properties are set upon identification (registration / log in), set when app profile information is updated, and set again on profile switch such that the demographics information collected reflect the active profile in use when those properties are stored as event properties. Event properties should get their information from the same place as the profile properties such that historical demographics data reflects the active profile in use at the time of the event.

kapa.ai is it bad practice to set all of the user profile properties upon log in to ensure that they reflect the active profile, and then setting them again whenever a profile field in the app is updated, and then setting them again when a profile is switched? or is there a preffered method to adjusting user profile properties

kapa.ai does the flutter sdk support .getPerson().remove() or just .getGroup().remove()

kapa.ai if we use .set() to set the profile properties, and then somebody adds something, say a club membership to their profile, we can use .append() to add it to the list. What about removing entries from that list of profile properties for example on membership expiration?

kapa.ai With all of the context we've discussed, can you give me a step by step outline for the implementation

kapa.ai and what about reset()? should we call that on profile switch or only on account log out? Our users require phone number validation after a certain period of inactivity or after explicit sign out, and I see that it is recommended to call reset() on signup rather than log out so that we are not constantly resetting when users automatically sign out, is that something of concern to pay attention to?

kapa.ai so if we want to have the demographics information for the current active profile that the account (user) is using, then would we call set() on profile switch, and update the information to reflect the currently active profile id's demographics info? and then set again on on profile switch back, so that the user properties are current to the browsing profile? and then we could also have all of those user properties as event properties to track events by user demographics historically?

kapa.ai Can you help me with figuring out how to identify previously signed up users that have had events recorded in mixpanel? Would we use identify() on sign up and log in, with the account id (setting it as the distinct id)? for setting their profile properties, would we set() the profile id and profiles demographic information on profile change? or can we have multiple profiles tied to one account id/distinct id?

kapa.ai can you expan upon the difference of user properties and profiles? My understanding was that user properties were tied to the users profile, so whenever a user changes their in app profile, the users user properties would have to be set again and then their profile in mixpanel would reflect said change, is that correct?