Why did my event count jump in Mixpanel?
The Mixpanel help pages give 3 common reasons. The first to rule out: Events sent through Mixpanel's import API without their own insert ID get one from Mixpanel but cannot be matched as duplicates, so the same event imported twice can be counted twice.
What causes it?
Events sent through Mixpanel's import API without their own insert ID get one from Mixpanel but cannot be matched as duplicates, so the same event imported twice can be counted twice.
In the Mixpanel help:
If an event arrives without one, Mixpanel generates a value for it, but it will not qualify for the deduplication process.
Duplicate events appearing in reports, read 2026-11-12.If a retry sends the event again with a new timestamp, Mixpanel can treat it as a new event, so retries can raise the count.
In the Mixpanel help:
Because the key includes `time`, a retry must resend the identical event for deduplication to work.
Duplicate events appearing in reports, read 2026-11-12.A raw export keeps every copy that arrived, so its event count can be higher than the count in Mixpanel's reports.
In the Mixpanel help:
Raw event export will contain all data as they were ingested, without any deduplication.
Duplicate events appearing in reports, read 2026-11-12.
How do I check it myself?
When comparing counts, compare a report with a report, since reports remove duplicates and raw exports do not.
In the Mixpanel help:
Query-time deduplication is visible in the Mixpanel UI and reports, but not in raw data exports.
Duplicate events appearing in reports, read 2026-11-12.To count unique events in an export, match rows on event name, user ID, time and insert ID, as Mixpanel does.
In the Mixpanel help:
Apply the same four-part key (`event`, `distinct_id`, `time`, `$insert_id`) to exported data yourself.
Duplicate events appearing in reports, read 2026-11-12.
How does Mixpanel work with Feder?
- Connect Mixpanel to Feder and it joins your Visits apps.
- When you connect Mixpanel, Feder checks the connection straight away and shows Connected only when that check passes. If a reading cannot be taken later, Feder shows it as not read, never as zero.
Some numbers are too quiet to judge daily, such as a form filled in a few times a week. Until there is enough of your own history to judge a change, Feder says it is still learning and scores nothing, rather than guessing.
See whether you can trust the numbers in Mixpanel, one of your Visits apps. Feder only reads. It never changes anything in Mixpanel.
What else goes wrong with these numbers?
- Why did my event count drop in Mixpanel?Mixpanel
- Why did my unique users jump in Mixpanel?Mixpanel
- Why did Google Analytics stop collecting data?Google Analytics
- Why aren't my key events showing in Google Analytics?Google Analytics
- Why does Google Analytics show (not set)?Google Analytics
See every question.
Where do these answers come from?
Every cause and check on this page comes from the Mixpanel help pages, quoted above with the date we read them. Last reviewed 2026-11-12. We read them again by 2027-11-12. If one changes, this page changes or comes down.