Every mature Mixpanel project I audit has the same symptom: a new analyst opens the event dropdown, sees 400 events, and asks on Slack which one is the real signup. Nobody answers with confidence.
That’s not a tracking problem. It’s a governance problem, and Lexicon is where you fix it.
What Lexicon is
Lexicon is Mixpanel’s data dictionary. Every event and property in your project appears there, and you can add descriptions, display names, tags and owners, plus control what’s visible, what’s merged and what’s collected at all.
It’s the first place I go in an audit, and the last place most teams maintain.
Step 1: Set up ownership first
Mixpanel’s own governance guide starts with people, not tools: name a governance owner (often the analytics lead), plus a backup, and decide who reviews new events. Without an owner, any cleanup decays within a quarter.
Step 2: Audit and document
Go through Lexicon and, for every event and property that matters:
- Write a plain-language description, including what triggers it.
- Set a display name people will recognize.
- Tag events by domain or team (
checkout,onboarding,billing) so ownership is visible.
Start with the 20 events used in your most important dashboards. Perfect coverage of 400 events can wait.
Step 3: Understand hide, drop, merge and block
These four actions look similar but do very different things. Getting them confused is the most expensive Lexicon mistake.
| Action | What it does | Reversible? | Who can do it |
|---|---|---|---|
| Hide | Removes the item from menus and reports; data is still collected and counts toward your allowance | Yes, unhide | Admins and owners |
| Drop | Stops storing new incoming data for that event or property | You can undrop, but data dropped in the meantime is gone for good | Project owners only |
| Merge | Treats several events or properties as one name in reports | Check current docs before relying on it | Project owners only |
| Block | Prevents an event from being ingested at all | Check current docs | See Mixpanel’s Lexicon docs |
A few details worth knowing:
- Hiding doesn’t save money. Hidden events still ingest and still count toward your data allowance.
- Dropping is the emergency brake for sensitive data. If a password or card number slips into a property, dropping it stops new values being stored. For data already stored, use Mixpanel’s data deletion tooling.
- User profile properties can’t be merged, only events and event properties.
- Events that haven’t fired in 30 days disappear from report dropdowns automatically, which can make old events look “missing” when they’re just inactive.
Step 4: Clean up duplicates with merge
Remember the four versions of signup? Merge is how you fix that without rewriting history. Pick the canonical name, merge the variants into it, and every report sees one event.
Mixpanel also points out an alternative: custom events, which group several distinct raw events into one analytical concept without merging them. Use merge when events are truly the same thing with different names. Use a custom event when they’re different actions you want to analyze together.
Then fix the source. A merge in Lexicon doesn’t stop your code from sending the wrong name tomorrow.
Step 5: Stop the mess coming back
On plans that include them, Mixpanel offers features that make governance enforce itself:
- Data Standards to require naming formats (like snake_case) and descriptions.
- Event Approval to review unplanned events before they appear in the project.
- Verified data, on Enterprise plans, so owners and admins can badge trusted events and metrics.
If your plan doesn’t include these, a monthly 30-minute review of new events in Lexicon does most of the same job.
Speeding it up with Claude and Mixpanel MCP
This is where AI genuinely saves time. With Mixpanel’s MCP server connected to Claude, you can ask in plain language to find events with no description, find duplicate or near-duplicate event names, tag all checkout events, or hide events that haven’t fired in 90 days. The MCP server includes bulk edit tools for up to 50 events or properties at once, plus tools to find and merge duplicate groups.
My rule: always ask Claude to list the planned changes first, review them, then apply. Every change made through MCP is recorded in the audit log under the connected account.
Mistakes to avoid
- Dropping when you meant to hide. Dropped data cannot come back.
- Hiding to cut costs. It doesn’t reduce volume.
- Merging without fixing the code, so new duplicates appear next week.
- Descriptions written for developers only. “Fires on POST /api/v2/orders” helps nobody in marketing. Add the business meaning.
- No owner. Governance without a name attached is a wish.
Final thoughts
A clean Lexicon is what turns Mixpanel from “the tool only the analyst understands” into something the whole company trusts. Start with ownership, document the events that matter, and learn the difference between hide and drop before you click either.
Sources
- Mixpanel: Govern Your Mixpanel Data for Long-Term Success
- Mixpanel: Lexicon
- Mixpanel: Data Governance overview
- Mixpanel: MCP Server
GET EXPERT ANALYTICS HELP
Need help getting reliable answers from Mixpanel?
Tell us about your tracking, funnels, retention, or reporting challenge. Optizent can help you implement, audit, and use Mixpanel with confidence.
We will use these details to respond to your request. Please do not include passwords, account access, or customer data.
