How to Use Mixpanel to Track What Users Actually Do on Your Website

Go to mixpanel.com and sign up for a free account using your email or Google login. Once logged in, you'll be prompted to create your first project. Give it a descriptive name — for example, 'My Online Store' or 'Company Blog 2026' — so you won't confuse it with other projects later.

After creating the project, Mixpanel will display your Project Token. This is a unique string of letters and numbers that connects your website to your Mixpanel account. Copy it immediately and save it somewhere safe, like a password manager or a shared team document. You'll need it in the next step.

While you're in the project settings, take 5 minutes to review the privacy and data retention settings. If your website has users in Europe or California, you'll need to configure GDPR and CCPA compliance options. Mixpanel provides these controls under Project Settings > Data Privacy. Setting this up correctly from day one prevents legal headaches later.

The free Mixpanel plan includes 1 million events per month, which is more than enough for most small to medium websites starting out. You won't need to enter a credit card to get started.

Mixpanel gives you a small JavaScript code snippet that you paste into your website's HTML. Open your website's main HTML file or your CMS theme editor and locate the closing </head> tag. Paste the Mixpanel snippet just before that tag.

Once the base snippet is added, you need to initialize Mixpanel with your Project Token. The initialization code looks like this:

mixpanel.init('YOUR_PROJECT_TOKEN', { persistence: 'localStorage', track_pageview: true })

Replace YOUR_PROJECT_TOKEN with the token you saved in Step 1. The persistence: 'localStorage' setting makes tracking more reliable by storing user data locally in the browser. The track_pageview: true setting automatically records every page a user visits — more on that in Step 4.

If your site is built with React, Vue, or another JavaScript framework, Mixpanel also offers an npm package. Install it by running: npm install mixpanel-browser — then import and initialize it inside your app's root file.

After adding the code, open your browser's developer console (press F12), reload your site, and check for any error messages related to Mixpanel. If there are no errors, your SDK is working. This whole process typically takes 15 to 30 minutes.

Before you start tracking everything, stop and plan. This step saves you hours of cleanup work later. A tracking plan is simply a document — a spreadsheet works fine — that lists which user actions you'll track, what those actions are called, and what extra details (called properties) you'll record with each action.

Start with just 2 core events tied directly to your business goals. For example, if you run an e-commerce site, your two starting events might be 'Product Viewed' and 'Purchase Completed'. If you run a SaaS product, they might be 'Sign Up Started' and 'Feature Used'. Don't track every button click on the site — that creates noise that makes analysis harder, not easier.

For each event, also decide on properties. Properties are extra details recorded alongside the event. For a 'Purchase Completed' event, useful properties might include purchase_amount, product_category, and payment_method. These let you slice the data later — for example, seeing which product categories drive the most revenue.

Mixpanel provides a free Tracking Plan template you can download from their documentation. Fill it out with your event names, property names, who on your team owns each event, and a short description of why you're tracking it. Keep this document updated as your tracking grows. Teams that skip this step end up with dozens of inconsistently named events that are nearly impossible to analyze.

Mixpanel's auto capture feature automatically tracks 8 to 10 common user interactions without you writing any custom code. When you added track_pageview: true to your mixpanel.init() call in Step 2, you already enabled one of the most important auto-captured events: Page View.

Auto capture also records button clicks, form interactions, page scrolls, and element interactions — all without additional implementation. Each auto-captured event comes with built-in properties. Page View events include properties like the page URL, domain, and path. Click events include the text of the element that was clicked. This gives you immediate data to work with while you build out your custom tracking.

Auto capture also detects rage clicks — when a user rapidly clicks the same element repeatedly, which typically signals frustration or confusion. Spotting rage clicks helps you find broken buttons or confusing UI elements quickly.

Auto capture is especially valuable in the early days of your implementation because it starts collecting real behavior data immediately. However, it won't track the business-specific actions that matter most to you, like completed purchases or form submissions. Think of auto capture as your foundation layer — it handles the generic stuff so you can focus your custom tracking effort on the actions that are specific and meaningful to your goals.

Custom events let you track the specific actions that matter most to your business — the ones auto capture misses. You add custom tracking by calling mixpanel.track() in your JavaScript code at the exact moment a user completes an action.

Here's what a basic custom event looks like:

mixpanel.track('Purchase Completed', { purchase_amount: 49.99, product_category: 'Software', payment_method: 'Credit Card' })

The first argument is your event name. The second argument is an object containing your event properties. Add this code inside the function that runs when a user completes a purchase — for example, inside a form submission handler or after a successful API call.

Naming consistency is critical. Mixpanel is case-sensitive, meaning 'Purchase Completed', 'purchase completed', and 'PURCHASE COMPLETED' are treated as three completely different events. Decide on a naming convention — most teams use Title Case for event names and snake_case for property names — and stick to it across your entire team.

If a property value isn't available for a particular event, simply leave that property out of the tracking call entirely. Never send null, an empty string, or a placeholder like 'N/A' — these pollute your data and distort your reports.

After adding custom tracking, open Mixpanel's Live View (under the Reports section) and trigger the event on your site. If you see the event appear in Live View within a few seconds, your custom tracking is working correctly.

Events tell you what users do. User profiles tell you who they are. Combining both gives you a complete picture. User profiles store persistent information about each individual user — things like their email address, subscription level, location, account creation date, and any other details relevant to your business.

To set user properties, use the mixpanel.people.set() method. Here's an example:

mixpanel.people.set({ '$email': 'user@example.com', 'Subscription Plan': 'Pro', 'Signup Date': '2026-03-15', 'Country': 'United States' })

Call this after a user logs in or signs up, when you have their information available. Properties starting with a dollar sign (like $email and $name) are Mixpanel's reserved properties that get special treatment in the interface.

Once user profiles are in place, you can segment your event data by user properties. For example, you could compare conversion rates between users on a free plan versus a paid plan, or see which countries have the highest purchase rates. This kind of segmentation turns raw event counts into actionable business intelligence.

Update user properties whenever something significant changes. If a user upgrades from free to paid, update their Subscription Plan property immediately so your segments stay accurate.

Before capturing any personal information like email addresses, review Mixpanel's privacy documentation and ensure your privacy policy is updated to reflect what data you collect and why.

With events and user profiles flowing into Mixpanel, you're ready to analyze the data. Mixpanel's three core report types each answer different questions.

Insights shows you trends over time. Open Insights from the left navigation menu, click 'Add Metric', and select one of your custom events — for example, 'Purchase Completed'. You'll immediately see a line chart showing how often that event occurred each day. Switch between 'Total Events' and 'Unique Users' depending on whether you want to see total purchases or unique buyers. This is your go-to report for tracking growth and spotting unusual drops.

Funnels show you where users drop off in a multi-step process. Click 'Funnels' in the navigation, then define your steps in order — for example: Step 1: Page Viewed (product page), Step 2: Sign Up Started, Step 3: Purchase Completed. Mixpanel will calculate the percentage of users who complete each step and show exactly where the largest drop-offs happen. If only 10% of users who view a product page complete a purchase, your funnel pinpoints which step loses the most people.

Flows reveal how users actually navigate your site — including unexpected paths you didn't anticipate. Select a starting event and Flows shows you all the different places users went next. This is excellent for discovering navigation problems and optimization opportunities.

Start with one Insights report and one Funnel focused on your 2 core events. Expand from there once you're comfortable.

Good tracking data requires ongoing maintenance, not just a one-time setup. Without governance, your Mixpanel account will gradually fill with duplicate events, abandoned properties, and inconsistent names that make analysis unreliable.

Mixpanel's Lexicon tool (found under Data Management in the left navigation) is your primary governance tool. Open Lexicon and you'll see every event and property your site has sent. For each event, add a plain-English description explaining what it means and when it fires. Assign an owner — the team member responsible for that event. If you rename or retire an event, mark it as deprecated in Lexicon rather than deleting it, so historical data remains intact.

Keep your tracking plan document updated every time you add, change, or remove an event. Treat it like a changelog. If a new developer joins your team in 6 months, your tracking plan should tell them everything they need to know about your implementation without having to dig through code.

Schedule a quarterly review of your Mixpanel data. Look for events with very low volume that might be duplicates or broken implementations. Check for properties that are inconsistently populated. Remove or merge anything that's creating confusion.

Finally, stay current on privacy regulations. In 2026, GDPR and CCPA requirements continue to evolve. Mixpanel's Privacy Hub provides updated guidance on data minimization, user deletion requests, and opt-out mechanisms — review it at least once per year.