Tracking Monthly New Users and Actions: Seeking Assistance

Daniel C. · 2024-10-18T07:44:02.143Z

:sos: Maybe someone can help me with this one. I'm blocked. How can I plot: • new users each month • new users each month that performed a certain action that month

Tracking Monthly New Users and Actions: Seeking Assistance | Mixpanel Community

11 comments

· Sorted by Oldest

Lamei T.
·
·
Hi, for the 1st , have you tried leveraging User Profiles?
Set a "User Created Date" Property: When a user first signs up, send a $set call to Mixpanel's API to add a "User Created Date" property to their profile.
Filter by "User Created Date": You can then filter users based on this property to identify those who were created within a specific time frame (e.g., new users this week).
OR
introduce an event like "new users" that records the user profiles/ ids per MIN (user created date)
then you just need to simply select that event, and count distinct the "new users" per month
Lamei T.
·
·
Rge. the 2nd, I usually apply
Use "First Time" Property: Mixpanel automatically adds a "First Time" property to every event. This property is true if the event is the first time a user has performed that specific action. You can use this in conjunction with your "new users" event to identify new users.
OR create a cohort for those users
Ronen I.
·
·
Daniel C. I actually use "First Seen" breakdown instead of "Time״ - you can avoid creating new properties
Ronen I.
·
·
Loading attachments
Daniel C.
·
·
Ronen I. thanks for your response. If i do that I get the active users each month broken down by the month they were first seen. And get a plot similar to this.
Loading attachments
Daniel C.
·
·
Nevertheless, I'm looking to produce sth like
Loading attachments
Daniel C.
·
·
The problem comes with defining the cohort of new users
Daniel C.
·
·
If you define new users cohort as first seen in the last 30 days you get this plot
Loading attachments
Daniel C.
·
·
Which certainly does not show the amount of users that were first seen each month
Daniel C.
·
·
Lamei T. thanks for your response. I was hoping to not need new properties as then I would not be able to apply the analysis retroactively.... unless I merge profiles with an imported table. Trying to avoid this. Also was assuming that first seen was the path to go but behaves strangely as explained above.
👋1
Ronen I.
·
·
makes sense Daniel C.

Lamei T.
·
·
Hi, for the 1st , have you tried leveraging User Profiles?
Set a "User Created Date" Property: When a user first signs up, send a $set call to Mixpanel's API to add a "User Created Date" property to their profile.
Filter by "User Created Date": You can then filter users based on this property to identify those who were created within a specific time frame (e.g., new users this week).
OR
introduce an event like "new users" that records the user profiles/ ids per MIN (user created date)
then you just need to simply select that event, and count distinct the "new users" per month
Lamei T.
·
·
Rge. the 2nd, I usually apply
Use "First Time" Property: Mixpanel automatically adds a "First Time" property to every event. This property is true if the event is the first time a user has performed that specific action. You can use this in conjunction with your "new users" event to identify new users.
OR create a cohort for those users
Ronen I.
·
·
Daniel C. I actually use "First Seen" breakdown instead of "Time״ - you can avoid creating new properties
Ronen I.
·
·
Loading attachments
Daniel C.
·
·
Ronen I. thanks for your response. If i do that I get the active users each month broken down by the month they were first seen. And get a plot similar to this.
Loading attachments
Daniel C.
·
·
Nevertheless, I'm looking to produce sth like
Loading attachments
Daniel C.
·
·
The problem comes with defining the cohort of new users
Daniel C.
·
·
If you define new users cohort as first seen in the last 30 days you get this plot
Loading attachments
Daniel C.
·
·
Which certainly does not show the amount of users that were first seen each month
Daniel C.
·
·
Lamei T. thanks for your response. I was hoping to not need new properties as then I would not be able to apply the analysis retroactively.... unless I merge profiles with an imported table. Trying to avoid this. Also was assuming that first seen was the path to go but behaves strangely as explained above.
👋1
Ronen I.
·
·
makes sense Daniel C.