Community Tip: Naming conventions to stay organized
This Community Tip will describe some useful naming conventions to organize events, properties, reports, and campaigns.
Add prefixes to separate product components
As your application matures, different teams may be accessing the same Mixpanel project to analyze completely different product and process-oriented user-behavior. This shared studying of a project can very well increase the complexity in reporting, as your Mixpanel implementation accommodates tracking of all products and processes within your application. This can lead to an increase in the number of events and properties deployed to capture key metrics and granularity of data.
Using prefixes offers you and your team an invaluable way to distinguish different types of metrics for easy recognition and usage across your teams while maintaining a comprehensive and granular tracking scheme. Prefixes such as “Billing -” and “Product -” enables different teams to filter and select in an instant processes and products that are of greater importance to them!
It is important for us to note that prefixing your event data is a reporting organizational tip. Specifics of an event should in general be recorded within the properties of the event, as properties are imperative for segmenting across event data. For further reference on how to name your events and effectively deploy the use of properties, please refer to the “Events and Properties” section within this blog post.
You may also add prefixes to the names of your bookmarked reports to improve searchability, but be careful of going overboard! There is no need to add your name/initials to differentiate your bookmarks from others’, as Mixpanel already adds the creator of the bookmark within the search bar.
It would be wise to also describe custom events in a manner that summarizes the metric in a meaningful manner rather than to simply compile the names of the individual events that the custom event is comprised of. For example, “Active User Engagement”, is much more understandable to all members of a project than “Character Created + Tutorial Finished + MA” as a name for a custom event that represents any user action you would consider to be an active engagement by a unique user.
Bring events and properties to the top with ‘!’ or ‘#’ or bottom with ‘~’
A simple but nifty “partitioning system” that Change.org deployed to distinguish experiments they were running to increase petition-signing rates was to add a tilde to the beginning of their property names. Since Mixpanel orders your data in alphabetical order, adding a tilde to a property sends it to the bottom of a drop down list. The inclusion of a tilde also informs the user at a glance that the property represents an experiment, and is transient in nature (after all, any events or properties that are not sent into the Mixpanel project are hidden from your project after 30 days to help declutter your reports. Don’t worry though! These events and properties are still stored on our backend, and can be resurfaced as soon as they are sent into the project again). To learn more about how Mixpanel empowered Change.org to learn from its data and improve KPIs, please click here.
Some events (like “App Install” and “Order Confirmation”) and properties (such as “Number of Friends Invited” and “Purchased Amount”), matter more to the overall analytics of a company than others. To answer the need for studying these metrics frequently, you may add a ‘!’ or ‘#’ to the beginning of an event or property’s name to send the property to the top of a drop down list.
In doing so, the most significant metrics will be but a few clicks away for all your reports!
Standardize the indexing of your notification campaigns
By ensuring that all members of a project title their Notification campaigns by a standardized indexing system, you can ensure that a perpetually expanding Notification campaign system is search-friendly!
As you can see from the screenshot above, I have chosen to order the indexing of my campaigns in the following manner:
- Point in Lifecycle Reached
- Paying State (if applicable)
- Date Created
- Cohort (if applicable)
This not only allows for easy searching at a glance, but also enables my team to systematically search for campaigns they are responsible for!
These are just a few examples of how you can get creative and organized! If you have any reporting best practices or tips up your sleeves, or if you have any questions or concerns, please reach out to firstname.lastname@example.org to speak with someone smart, quickly!