Sticky Tutorial

Mixpanel Health Check

  • 26 July 2021
  • 0 replies
  • 18 views

Userlevel 4
Badge +5

Although we all have access to the same reports in Mixpanel our experience will be different depending on what we have chosen to track, our goals and teams involved. It is for this reason that our first week will be dedicated to understanding exactly what that is for each of us.

A purposeful project starts with clear data that is connected to a clear strategy.

Your strategy is underpinned by your implementation and your implementation is driven by strategy. This worksheet will walk you through a routine check for success in both areas.

Start Here

p.s. If you prefer to come back to this later, download the pdf. attached

  1. Carve out about 1-2 hours depending on how intricate your user experience is

  2. Open your existing Implementation plan or create a new one from our template here and export your current lexicon into a tab.

  3. Review your analytics strategy or create one following our training here

Now that you have time, a place to note your next steps and a strategy and focus we can begin!


QYfaqx7CR-lJpSutYgnt-oqeJnM5V6xppg1WWhnLQkA8cpVrcUbCGIKnWmrQcBsa7I_ceaa0Az9ZKpAN9K2uqUSXhPmkcL2EeGlGt52iyThk1P7D68bHqH1qv10jdDVvl5g09WgJ

Your Strategy, KPIs & Metrics

We often get stuck when we think of strategy, we imagine it to be this grandiose high-level vision when the definition is simply “a plan of action designed to achieve a long-term or overall aim”.

Strategy = what do you want?

This could be many things, some of the most popular are:

  • xx% Growth

  • xx% Retention Rate

  • $xx in ARR

  • $xx Average revenue per paying user

  • xx% churn

  • xx Daily/Weekly/Monthly active users

So, in the spirit of translating concepts into questions your complete analytics framework can easily translate into a list of questions that you want your data to answer.

Here are 21 questions you can answer in Mixpanel alongside 12 things you probably didn’t know you could do for inspiration.

At the top of the “tree” you will have the company focus and everything else will branch out from there until it encompasses all teams and if you’re feeling fancy you could make it look like the below to truly democratise the data in your Mixpanel project.

It’s important not to get stuck here. Release yourself from any overwhelm by remembering that this strategy will evolve and change as your business changes. It is also a great stage to include other teams by asking I4iQg9Q6c1a7bTR7JcEZ3gYHBoQYSD_AuBKbB3PjTqtHq9U7FB9qPLO1oP-TTcgg6hdpccL1CDJu6UUncDqmKN8uJy7cOBywfY8WfqlDzmINe8ijVGC-UmDCDrw_FgNtSgLXQBWzthem to share their metrics and KPIs for inclusion. 

Your user journey

Help: Explore your users

Mixpanel is designed to follow your user’s journey but we understand that sometimes development can run ahead of expanding your Mixpanel implementation. We are going to begin by testing your implementation against your most recent user experience.

Prepare to Test

  • Grab your phone/device and login to a profile

  • Find yourself in Explore by searching the email address or alias you are using

  • Once you appear in the search list click your profile which will take you to your User profile.

  • On the left you will have your user properties and on the right will be a powerful feed of events as you trigger them

Time to test

Work your way through every corner of your app checking the following:

  • When you press the button/trigger does it appear in the feed? 

  • Are any events missing? If so, note them on the spec

  • Click the arrow on the event to see which properties have been sent alongside?

  • Are any properties missing? If so, note them on the spec

Review all the events triggered and add them to implementation spec.

Your Events & Properties

Help: Lexicon overview

This is the source of truth for what you are tracking, this is 100% in your team’s control which means it can contract and expand to your whim. 

  • Review the list of events tracked on your recent ‘tour’ and see if any events listed no longer exist in the platform

  • Double click the header where it notes “volume” to see the most triggered event in your project. Does that look right?

  • Double click the header where it notes “queries” to see the most queried event in your project (i.e. included in reports from your team). Does that look right?

  • Are the “top” events aligned with your analytics framework?

  • Do you have clear descriptions for each event and property?

  • Are there any duplicates?

Repeat this process for your custom events, event properties and user profile properties noting any key points on your implementation spec.

You might have a to-do list alongside some questions, add a reply with your questions or bring them along to office hours tomorrow!

 


0 replies

Be the first to reply!

Reply


Mixpanel