Best Practices -Updated-

Our hope here is to provide a more up to date outline of some of the best practices for quickly getting up and running with mixpanel.

The best way to get started

We advise you begin by instrumenting only a small handful of key metrics. We think you'll be amazed how much value you can get out of even just 5 events. By starting your implementation small, you can quickly separate signal from noise, and begin from day one with a manageable reporting environment that you can share with your co-workers. You'll also be able to start making decisions based on your data faster, allowing the tool to demonstrate its value before additional development time and effort are spent on a more elaborate implementation. Furthermore, a small implementation is also easier to fix if, for instance, after chatting on the phone with a Solutions Architect you decide you'd like to adopt a new system of organizing or naming your events and properties.

One easy way to start small is to envision a single funnel, measuring one of the most important processes on your site or in your app (sign-up, or purchase funnels are good choices). Try choosing the steps of that funnel as your first few events.

Make good use of properties

Properties are the place to articulate all the details associated with an event. Properties fall into two camps: event specific (like the revenue associated with a purchase event) and user specific (like demographic information about the user). The user specific data we call "super properties." For example, you might want to send the gender, age, or traffic source of a particular user along with their events. All the user specific data is stored in a cookie (on the web) or in a local object (on native mobile) and appended onto all subsequent events for that user. A rich set of event and user specific properties will allow added agility in reporting, since mixpanel lets you drill down and inspect the intersections of many different properties across all reporting. It's important to keep in mind that properties are entirely defined by you. Do your best to avoid storing details in event names that could be stored in properties. For example, don't do mixpanel.track("Facebook Share"). Do something like this: mixpanel.track("Share", {"Network": "Facebook"}). More on that here.

Employing this strategy makes Mixpanel's UI and reporting significantly more powerful and easier to understand.

Clear event and property naming

We advise always using clear, human readable event and property names. This makes your reports much easier for everyone on your team to understand. There's no reason you can't use spaces as opposed to underscores if you'd like. Naming things nicely makes reporting more navigable for everyone on your team. For example, don't use us a property name "c_id" for the id associated with a video channel if you don't have to. Why not send us a property called "Channel" and use a plain-text representation of the channel name as opposed to a raw numeric id?

As you continue to expand and improve you mixpanel implementation, keep track of the choices you've made about what to track with an implementation specification. You can can find a sample document to get started with here.

Keep your development data separate from your production data

A common question is "how do we delete some old development data we sent while we were instrumenting?" The answer, unfortunately here, is that you cannot. We advise all customers to create at least two projects. If our project was called "Mixpanel" then we would call one project "Mixpanel - Dev." and the other "Mixpanel - Prod." Use logic in your code to swap out the two project tokens for when you're developing and pushing to production. It costs you nothing extra to have multiple projects as we price based only on the amount of data you send us.

How do I track distinct users and what is this "distinct_id" thing?

One of the most important properties in mixpanel is distinct_id. Distinct_id is a property that is sent with every mixpanel event, and it is what we use to determine uniqueness across all reports. In JS or in the iOS/Android SDKs you can let mixpanel handle distinct_id for you, but you can also choose to control it yourself. You can set distinct_id using the identify method. You can grab distinct_id using mixpanel.get_property("distinct_id") in JS (or the equivalent in our mobile SDKs).

A common question is what to do when an anonymous piece of traffic traverses the signup funnel and then finally converts to a user. If you are setting the distinct_id yourself (to say your internal user id) so that if a registered user comes back on a new machine, or after clearing their cookies, you'd like to keep tracking them as the same user. You may then find yourself changing the distinct_id part way through a funnel, which will break your funnel! And unfortunately there is no way to change the distinct_id of an event that has already been sent to mixpanel. Oh no!

The best practice here is to allow mixpanel's JS library (or mobile SDK) to issue its own automatic distinct_id value to a user when they visit your site. Allow the user to send events from that distinct_id as they traverse the signup funnel. At the time of registration (if you are using mixpanel's JavaScript library v. 2.2 or later) then you can fire mixpanel.alias("whatever_you_aliasing_to") to alias that previous id to your newly issued internal id. From then on, when that user returns and authenticates, ensure that they have the id you just aliased by using mixpanel.register({"distinct_id": "whatever_you_aliased_to"}) or mixpanel.identify("whatever_you_aliased_to"). That way you ensure that the signup funnel does not break, and also that you continue to attribute all post authentication activity to that user, using the same id as originally used in the signup funnel. More on aliasing here.

What is the difference between Engagement data and People data?

The Engagement section of reporting pulls and renders event-based data. The People analytics section pulls and renders People data. Right now these two data types are totally separate from one another. That said, often data is sent to both. For instance, when registering a super property marking a user as paid=true, it makes sense to send both people data and event data. The libraries for sending event data can be found here, whereas those for sending people data can be found here.

We recommend Javascript for web integrations

Javascript is the most robust library we have for integrating Mixpanel into your website. You are of course welcome to host the JS library locally, or to modify it if you desire, but unless you have a good reason, we recommend using our snippit that pulls the full library asynchronously from our CDN. Our Javascript has many features to make instrumentation as easy as possible, and if you use our snippit, you will be able to tap into updates that we make to the library without changing your code at all (in most cases).

In some cases, sending events server side makes more sense. For these instances, we offer more functionally limited libraries in many server side languages (python, php, ruby, etc.).

The javascript library works well for mobile applications that consit of html5 views, but for native apps we advise using our native Android and iOS SDKs. Our mobile SDKs are mature, offer the same functional richness as the javascript library, and the strategy for implementation is similar.

Paid customers should be careful who the project owner is

If you're a paid customer, the user who "owns" (is the admin of) the project must also hold the billing information for the project. You can email support@mixpanel.com if you wish to transfer your project or billing info to a different mixpanel account.

Sending data to one project

If you have similar user behavior coming from multiple platforms (perhaps a Facebook game which also has a mobile version), we recommend you send all the data to one project and track the platform the data came from as a super property. That way you can look at one user's behavior across platforms, and choose whether or not to view all user activity on the same set of axes, or filter down to a particular platform. This is of course only recommended when the basic actions taken by users are similar enough to be described with the same set of event names (properties can be different).

Data flexibility

Mixpanel is very flexible and open ended tool. You can use it for anything from measuring how your users fair slaying digital monsters, to QAing a back- end fix, or monitoring and tweaking performance metrics such as how long it takes a UI to render. Anything that can be thought of as an "event" with "properties" can be tracked with mixpanel. Furthermore you can send us data from literally anything that can send an http request. Hacking our data model is not just expected but heartily encouraged. So use your imagination when you send events and properties. Don't let traditional ideas about web analytics limit the questions you can answer in a data driven way. And if you come up with a new or cool use for the tool drop us a line at support@mixpanel.com so we can brag about you!

Community Tip: All About Time

In this Community Tip we discuss all aspects of time in Mixpanel, including how to set your project timezone, send time properties, and handle timestamps when exporting or importing data. Using these directions, Mixpanel can help standardize how you handle time to ensure your data reflects accurate timestamps. In today’s connected world, a startup can be headquartered in Berlin, Germany, have a core user-base in Beijing, China, and be analyzing their data through an analytics company in San Francisco, California, USA. With all of these different locations in play, seamlessly handling time data being received from around the world can be intimidating. Luckily, with a few of the following best practices, you can ensure your Mixpanel data is time agnostic to the physical location of your users. Setting Your Mixpanel Timezone When you create a new Mixpanel project, your project timez...

Community Tip: Implement Mixpanel in Swift Apps

This Community Tip will describe how to implement the Mixpanel iOS SDK, written in Objective-C, within your Swift app. We will walk through integration using CocoaPods, library set-up, provide code samples, and ultimately save you development time. Requirements: CocoaPods This guide assumes you are using CocoaPods since that is the recommended way to integrate your app with the Mixpanel iOS library . For assistance integrating Mixpanel into Swift projects without CocoaPods, please follow the instructions to build the Mixpanel iOS library from source . Please note the below instructions for integration will only work for Swift apps targeting iOS 8.0 or higher — if you are targeting any versions below iOS 8.0 please jump to the final section of this guide. Integration with CocoaPods With any version of CocoaPods greater than 0.36, integration of Objective-C libraries within...

How HubSpot grows a product into something you can't live without

Did they even open my email? Did they check out my link? Marketers have had tools to answer these questions for a long time. Sidekick , a project from HubSpot, brings this kind of email tracking to one-on-one email communication. For HubSpot, it's a little outside their wheelhouse. Over the last nine years they’ve developed some of the largest and most popular software for marketers. Sidekick is part of a decision to broaden their scope and serve non-marketers. And it's built on the freemium model. "The whole idea from the beginning was to go for really big scale that millions of people could use for free," says Dan Wolchonok. "And then to have a seamless path for those who want to pay for power features." Dan is a senior product manager at HubSpot. It's his job to get those millions of users. Which is less about finding them and more about keeping them around. Being active ...

Mobile A/B Testing: Walkthrough & Best Practices

Using Mobile A/B testing, you can test changes to your app without writing code. You can measure the impact on any conversion, like signups or purchases. In this Community Tip, we'll provide a walkthrough and best practices for running A/B tests in your iOS or Android app. Setup To get started with Mobile A/B testing, all you need is the Mixpanel SDK installed and initialized in your app. If you haven’t done this step yet, you can jump over to our iOS Integration Docs or Android Integration Docs for instructions on installing Mixpanel. To work with complex A/B tests which go beyond modifying UI elements, such as changing view flows, modifying defined constants, and more, you will need to implement developer tweaks ( iOS / Android ) in your app. Tweaks allow you to adjust actual variables in your code from the comfort of your Mixpanel dashboard. Once you add a Tweak to your...

Geolocation Error on 7/9/2015

Incident Summary: No geolocation was being performed on events and people requests between 5:00PM PST 7/8/2015 to 1:30AM PST 7/9/2015. This affected all customers. Timeline: On 7/8/2015 at approximately 5:00 PM PST, a change was deployed to consumers that migrated our geolocation system from a Python module to a C replacement as part of our systems optimization plan. After this point, all geolocation requests made to the Maxmind DB began failing. Around 7/9/2015 1:00AM PST, Mixpanel began reverting the change and by 1:30AM, all consumers were reverted back to the Python Maxmind DB reader, which resolved the issue. Root Cause: The migration from a Python module to a C replacement proved not to be a direct drop-in replacement and generated errors (TypeError) when fed a value other than a string. We typically send IPs in the format we receive them, which can sometimes be a long...

A/B testing comes to Android

So you've got an idea. "We have all these awesome features most users just haven’t tried yet. I bet more people would use them if they couldn't skip the tutorial. " "I know more people would create an account if our button just said 'Get Started'." "Our game's too easy. People want a challenge. If it were a bit faster, it would keep users coming back." Great, but a good idea alone isn’t gonna cut it. Especially when opinions differ. What you really need is cold, hard data. You need to put that hypothesis to the test and see how it fares with real users in the real world. That's where A/B testing comes in. Previously, you've been able to use Mixpanel to experiment and improve your iOS app. And we've seen how useful it has been to our customers. Today, we're expanding Mixpanel A/B Testing to Android. All the capabilities that enable you to experiment and improve your iOS a...

Community Tip: Benefits & Best Practices for Cross-platform Apps

In this Community Tip, we highlight the benefits and best practices for accommodating all of your varied products, environments, and platforms under a single Mixpanel project. Using this guide, your team can decide how to best track your cross-platform app data within Mixpanel. If you're one of the many users working with cross-platform apps, you may have wondered whether it's best to combine everything into one Mixpanel project or split everything up and analyze it separately. We've found that creating separate Development and Production projects to avoid cluttering your Production data is a great best practice, but the question of what to do with cross-platform Production apps is a matter of preference. The good news: Mixpanel is flexible enough to handle cross-platform scenarios in any configuration you'd like to implement. The choice is yours, and each approach comes with its...

Introducing Codeless Mobile Analytics

Tracking how users are interacting with your app just got easier. Now you can get Mixpanel's advanced mobile analytics without writing a line of code. Let's face it, everyone's dealing with limited developer resources. If you've got to add a tracking request to the growing queue of dev needs, it'll probably take some time. With Codeless Mobile Analytics , you can focus your development time on what matters - making your app better. With a simple point and click setup, Codeless makes tracking events a breeze. Want to know if people are using a new feature? Skipping that tutorial? Changing a setting? After you've installed the Mixpanel SDK you can just fire up Codeless Mobile Analytics (it's that icon on the bottom of your sidebar). Select your platform - iOS or Android. Then connect to your app using either a phone or an emulator. That's it. From right there in your bro...

How Cozi got a 38% increase in signup completion

Tara Pugh, product owner of Cozi, stopped by our June Office Hours to explain the process for improving their UX through many small, data-driven steps. Cozi helps bring order to the chaos of modern family life with an app that gets the entire family on the same page with shared calendars, to-do lists, and shopping lists. Digging into their conversion funnel data with Mixpanel, they identified opportunities to improve user experience by streamlining the account creation flow. Testing hypothesis after hypothesis, Tara and the team at Cozi were able to incorporate bits of learning into the flow: lighter background, different calls to action, pre-populating name and email forms. No single change resulted in a huge increase in conversions, but all together, the improvements raised the signup completion rate from 55% to 76%—a 38% increase. Check out Tara's talk for all th...