Skip to content
Overall Program Steps
Search
Setup
4
Signing off to begin
Agreement on implementation is signed
Understanding the why behind product
People behind the product
Understanding the objectives from the analytics
Planning
7
Analytics Strategy Session
Detailed implementation steps
Focus Metrics framework
Vertical specific Tracking plan for SaaS, eCom, Financial, Consumer etc.
Specification on mixpanel implementation
Approval
Signing off on Development
Development
7
Review by tech to identify the required data
Setting up analytics on staging
Providing Mixpanel Codes for implementation for Plug & Play approach
Set up of identity layer
Setting up events and tracking plan
Implementation includes setting up Mixpanel in app and enabling the tracking code
Phase wise planning
Implementation consists of 2 phases
1. Planning
2. Development
Check for assurance before deployment
Cheat Sheet
**Client-Side**
Call the identify method once you know who the user is.
Use the reset method on logout if you want to track multiple users on a single device.
**Server-Side**
Use the $merge event when you know two distinct_ids should be merged.
**Hybrid Implementation**
Pass distinct_id either from server to client or client to server.
Server to client - Use the identify method with the id from your server on the client side.
Client to server - Use the $merge event to merge the server and client ids.
Cutover
2
Deployment
Review on production
Hypercare
4
Dashboard for Product, Marketing, CxO, CS, Tech and Operations
Daily email at 10:00 am your time with your relevant dashboards
Workshop on how to use Mixpanel
Workshop
Step 1: Select a data governance owner or team
If you belong to a smaller, more nimble organization, select a primary data governance owner, who may be the owner of the initial analytics implementation. You should also choose a backup data governance owner who can quickly and easily step into the lead role if the primary owner cannot take responsibility.
If you belong to a larger organization, create a data governance team or governing council with a lead from each functional business unit leveraging this data (e.g., Product, Marketing, Analytics, Data Science) so that each team is well represented. This will also help to break down silos that may exist across teams.
Step 2: Create a centralized tracking plan for your product
Once your data governance owner or team is in place, make sure that you have a shared tracking plan to document new events and properties. You should already have one if you worked through your initial analytics implementation, but if you don’t, feel free to copy our tracking plan template.
Step 3: Document new events and properties
Before launching a new product feature (whether in alpha, beta, or to all users), the product manager responsible for the launch should establish the right metrics (to hold him/herself accountable) and submit a request to the data governance owner or team. The data governance owner or team can then build out the events and properties required to measure progress against these metrics.
Step 4: Review these new events and properties
When documentation is complete, the data governance owner or team can review these new events and properties with the product manager. If you have a designated Mixpanel Professional Services account team, you can also have them review and provide feedback on the new events and properties.
Either way, get sign-off that the events and properties actually map back to quantifiable business metrics and are ready to implement!
Step 5: Implement the new phase
The data governance owner or team can now relay to the technical lead(s) that they can proceed with development, translating the events and properties in the tracking plan into triggers within the product’s source code. The process here may vary drastically depending on internal processes, but typically starts with the creation of an engineering ticket by the data governance owner or team.
Step 6: Conduct proper QA (in your development environment) before deploying to production
The data governance process doesn’t end once the track calls have been added to your product’s source code. Now’s the time to engage in quality assurance processes to ensure that the data being collected is accurate and aligns perfectly with the new events and properties documented in your tracking plan.
Once you’ve confirmed that the data is accurate, you can deploy to production!
Step 7: Document your event and property definitions
If you use Mixpanel, the data governance owner or team should add descriptions of all new events and properties in Lexicon and organize data for clarity and discoverability. This will help everyone across your organization (who may or may not have been part of the implementation process) understand what data is being collected, which will in turn empower them to run analyses within Mixpanel and make data-informed business decisions.
And last but not least,
Step 8: Repeat Steps 1 through 7!
Lexicon documentation
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.