How to set up event properties on Mixpanel

intermediate 8 min read Updated 2026-03-18
Quick Answer

Setting up event properties in Mixpanel involves defining custom properties that track specific user actions and behaviors. You'll need to configure these properties in your code implementation and then manage them through the Mixpanel dashboard for analysis.

Prerequisites

  • Active Mixpanel account
  • Admin or Owner permissions
  • Basic understanding of event tracking
  • Access to your application's codebase

Step-by-Step Instructions

1

Access Your Mixpanel Project

Log into your Mixpanel account and navigate to your project dashboard. Click on Settings in the left sidebar, then select Project Settings to view your project token and configuration options.
Make sure you're in the correct project environment (Development, Staging, or Production) before proceeding.
2

Define Your Event Properties Schema

Go to Data Management > Lexicon in the left navigation. Click + Add Event to create a new event or select an existing event. Define your event properties by clicking + Add Property and specify the property name, data type (string, number, boolean, datetime), and description.
Use consistent naming conventions like snake_case or camelCase across all properties for better organization.
3

Implement Event Properties in Your Code

In your application code, use the Mixpanel SDK to track events with properties. For JavaScript: mixpanel.track('Button Clicked', {'button_name': 'signup', 'page': 'homepage', 'user_type': 'premium'});
For Python: mp.track(user_id, 'Button Clicked', {'button_name': 'signup', 'page': 'homepage'})
Always validate that property values match the expected data types defined in your schema.
4

Set Up Super Properties

Navigate to your code implementation and set up super properties that should be sent with every event. Use mixpanel.register({'app_version': '2.1.0', 'platform': 'web'}) to automatically include these properties with all future events for that user session.
Super properties are ideal for user attributes like subscription status, device type, or app version that rarely change.
5

Configure Property Data Types

Return to Data Management > Lexicon and click on each property to set the correct data type. Choose from String, Numeric, Boolean, Datetime, or List. This ensures proper filtering and analysis in reports.
Datetime properties should be sent in ISO 8601 format for consistent timezone handling.
6

Test Your Event Properties

Use the Live View feature in Mixpanel to monitor events in real-time. Navigate to Events > Live View and perform the actions in your app to verify that events and properties are being tracked correctly with the expected values and data types.
Test with different user scenarios and edge cases to ensure your properties capture all necessary data.
7

Create Property Descriptions and Tags

In the Lexicon, add detailed descriptions for each property explaining what it tracks and when it's used. Apply relevant tags like 'revenue', 'user_behavior', or 'feature_usage' to help team members find and understand properties easily.
Good documentation prevents duplicate properties and ensures consistent implementation across your team.
8

Verify Data in Reports

Create a test report by going to Insights and selecting your tracked event. Use the Breakdown feature to segment by your custom properties and confirm the data appears correctly. Check that numeric properties can be used for calculations and string properties show expected values.
Create a dashboard with key property breakdowns to monitor data quality over time.

Common Issues & Troubleshooting

Properties not appearing in Mixpanel dashboard

Check that events are being sent correctly using Live View. Verify your project token is correct and that property names match exactly between your code and Lexicon (case-sensitive).

Property values showing as wrong data type

Ensure you're sending the correct data type from your code. Go to Lexicon and update the property's data type setting. Note that changing data types only affects new incoming data.

Super properties not being included with events

Verify that mixpanel.register() is called before tracking events. Check that you're not accidentally clearing super properties with mixpanel.unregister() or mixpanel.clear_super_properties().

Events sending but properties missing values

Add null/undefined checks in your code before tracking events. Ensure all required properties have fallback values and that property names don't contain special characters or spaces.

Prices mentioned in this guide are pulled from current plan data and may change. Always verify on the official Mixpanel website before purchasing.