Gabe

Ah thank you for the clarification

Unless it does not count overlapping users from previous days

That was my understanding, but 90 + 81 is not 163 was my point Ansh A.

on top of that, every individual day of unique users in group A is higher than group B, yet on the cumulative users report, group B is higher for the entirety of the time period, and growing faster, though it also does not match the supposed cumulative value (i.e. group b day 1 is 90 unique users, group b day 2 is 81 unique users, but in cumulative reports it goes 90 -> 163. Is there a de-depulication of sorts that only counts unique users between the different days? i.e if there were 5 unique users on day 1 and 10 unique users on day 2, 5 of which were the same from day 1 would the cumulative report then show 10 cumulative unique users on day 2, or 15?

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