Data sent to Mixpanel can be differentiated from data sent by teammates testing or using a product and actual end users. Building this distinction depends largely on the nature of the product, and the desired division between teammate activity vs. your user activity present in the data.
Continue to collect data, but filter out of reports by email
One way to build reports that exclude teammate or employee activity is to filter out data where the Email property contains your company domain.
The process is similar across Mixpanel reports.
For example, this can be reflected in an Insights report by:
1. Clicking the 'Filter' button.
2. Specifying the 'Email' property.
3. Selecting 'Does not contain' and specifying the domain of the group to be excluded.
4. Select 'Add filter'.
5. Additional filters can then be added for additional granularity.
Create Separate Projects for Development and Production
It is possible to create two separate projects for development and production so that test data remains completely separate from live product data. In order to do this, create two separate Mixpanel projects. Simply switch the project token from the development project token to the production project token when it is time to switch to the product project. See this article to find your project token.
Opt individuals out of tracking in a single project (web, mobile)
Mixpanel’s client-side tracking library contains the opt_out_tracking() method, which will set the user’s local opt-out state to “true” and will prevent data from being sent from a user’s device. More detailed instructions can be found in our developer documentation.
This will prevent data from being sent out from the user’s browser or app going forward, but it will not remove past events that were already sent in before this method was implemented. It will also not prevent any data related to the user from being sent from other platforms.