People Properties Best Practices - Articles From the Archive


Userlevel 5
Badge +4

Each week, Mixpanel will release articles from our archives to help you get the most out of Mixpanel. Follow the Topic Tag #fromthearchive to subscribe to these posts and get alerted when they drop.


Recommendations

Here’s some advice to help you get the most out of your people profiles:

  • Before you start, determine the key types of messages you’d like to send.
    You can trigger people profile updates from actions that happen on your page. If you want to send a message to your users when they view your Help pages, you could set a property once they’ve viewed your Help pages. Similarly, if you want to check in with your users two days after they viewed a Help page, you could store the date of the last time they viewed a resource.

  • Store date or numeric data types instead of booleans when possible.
    Because Mixpanel allows you to cast people properties on the fly, a Date property type can be cast as a Boolean. If it is set, it will resolve to True. If it is not set or doesn’t exist on that profile, then it will resolve to False. For example, instead of “Has used Our Awesome Feature?” you could set “Last Awesome Feature Use” as a date and increase your power without cluttering your profiles or your code.

  • Store similar information in different ways.
    Storing the last plan purchased as a string indicates the current plan that the user has. But if you append the plan to a list, you would have access to all their past plans as well. It is also a really good idea to store much of this information as super properties so you have access to this information in your events that you send into Mixpanel.

  • Use Mixpanel’s special and reserved people properties.


0 replies

Be the first to reply!

Reply