Solved

What are some best practices for Events vs. Properties?

  • 12 September 2018
  • 2 replies
  • 555 views

Userlevel 2
Badge

I understand there should be limited events and that properties should be descriptions of an event. But can a property also be a micro-event, correct? What are some best practices for events and properties?


icon

Best answer by michael 4 January 2019, 21:14

Hi @john.austin,

Great question!

Our philosophy here at Mixpanel is that your analytics should embody a scientific approach to solving your business problems. This all starts with planning out your data collection strategy. A little work upfront before your implementation can pay off tenfold when down the line you can instantly access the metrics you need.

The data that goes into Mixpanel is broken out into events and properties. Events in Mixpanel should represent meaningful interactions a user has with your website or mobile app, while properties add additional information to these actions that you can use to segment and filter your data further.

At a very high level, we recommend keeping your event names general and storing greater details in the properties.

For example, if your users can download a file from your site, even if you have only one type of file users can download, call the event “initiated download” rather than “downloaded lolcat.gif”.

It’s better to store the details of what’s being downloaded in a property for that event. Then when your company expands and adds “laughing_baby.gif” you can easily keep tracking (and reporting to assess the success of your new content) without a hiccup! Keeping meta-data out of your events and in your properties where it belongs will keep your Mixpanel implementation scalable and maximize the value you get out of reporting.

For more information on planning your implementation, please check out this help center article: https://help.mixpanel.com/hc/en-us/articles/360000857366-Plan-Your-Implementation

Hope that addresses your question! But if not please feel free to keep the conversation going.

Best,

Michael


View original

2 replies

Userlevel 4
Badge +2

Hi @john.austin,

Great question!

Our philosophy here at Mixpanel is that your analytics should embody a scientific approach to solving your business problems. This all starts with planning out your data collection strategy. A little work upfront before your implementation can pay off tenfold when down the line you can instantly access the metrics you need.

The data that goes into Mixpanel is broken out into events and properties. Events in Mixpanel should represent meaningful interactions a user has with your website or mobile app, while properties add additional information to these actions that you can use to segment and filter your data further.

At a very high level, we recommend keeping your event names general and storing greater details in the properties.

For example, if your users can download a file from your site, even if you have only one type of file users can download, call the event “initiated download” rather than “downloaded lolcat.gif”.

It’s better to store the details of what’s being downloaded in a property for that event. Then when your company expands and adds “laughing_baby.gif” you can easily keep tracking (and reporting to assess the success of your new content) without a hiccup! Keeping meta-data out of your events and in your properties where it belongs will keep your Mixpanel implementation scalable and maximize the value you get out of reporting.

For more information on planning your implementation, please check out this help center article: https://help.mixpanel.com/hc/en-us/articles/360000857366-Plan-Your-Implementation

Hope that addresses your question! But if not please feel free to keep the conversation going.

Best,

Michael


Badge

Hi @john.austin,

I've actually published an article on this subject in MindTheProduct.

Let me know if that was useful.

Best of luck,

Yoav


Reply