If an event is not showing up in Mixpanel, first determine where it disappears: before the tracking call, during delivery, or inside the report. Changing a dashboard filter will not repair a tracking call that never ran.
Start with one event you can reproduce. For example, use a test account to create one workspace, record the approximate time, and follow that action through the collection process.
1. Confirm the destination project
Check that the application is configured for the project you are viewing. A staging build may correctly send data to a development project while you inspect production. Also review the configured regional endpoint for your project.
Record the environment, project name, and SDK version in the investigation. You do not need to paste credentials into a support ticket to explain the problem.
2. Confirm the action actually triggers tracking
Ask your developer to verify that the tracking function executes on the intended success condition. A button click and a successfully created workspace are different actions.
Test a successful submission and a failed submission separately. If neither produces a tracking call, investigate the application or tag trigger before investigating Mixpanel reporting.
3. Inspect delivery
For browser tracking, inspect the relevant network request and its response. For backend tracking, use application logs and the SDK’s documented error handling. A browser console message saying “tracked” is not proof that the receiving service accepted the event.
Possible delivery issues include a script error, a blocked request, consent rules that prevent collection, an incorrect destination, or a process ending before a queued event is sent. Preserve intended consent behavior while testing.
4. Look for the event in Events
Mixpanel’s Events view lets you inspect incoming events and their properties. Search using your test user’s identifier and the exact event name. Names are case-sensitive, so “Workspace Created” and “workspace created” should not be assumed equivalent.
If the event arrives here, narrow the investigation to report configuration. If it does not, return to the sending pipeline and check any event-blocking or governance rules your organization uses.
5. Check time and report conditions
Review the event timestamp, selected dates, timezone, filters, and data view. An incorrectly supplied timestamp may place an event outside today’s reporting period. A property filter may exclude an event that arrived without that property.
Temporarily build a simple report with just the event and a suitable date range. Add each condition back individually until the discrepancy returns.
A useful troubleshooting record
| Observation | Next investigation |
|---|---|
| No tracking call | Application trigger or tag configuration |
| Call runs, delivery fails | Request, response, endpoint, or collection rules |
| Event arrives, report is empty | Dates, filters, data view, and metric definition |
After a fix, repeat the same test and confirm both the raw event and the intended report. Avoid adding a second tracking trigger simply to make the number increase; that can create duplicates without solving the original problem.
Need help with your Mixpanel setup?
Optizent helps teams plan, implement, and troubleshoot analytics. Contact Optizent to discuss your Mixpanel tracking or reporting needs.
References
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.
