Migrate from Mixpanel

Import a Mixpanel raw event export into one Supermetry site, with a preview and undo.

Upload a Mixpanel raw event export to rebuild daily traffic history in Supermetry. Nothing is stored until you confirm the preview.

Export raw events from Mixpanel as JSON lines (one event per line) or CSV. You can upload the file as is, gzipped, or in a ZIP of such files. A JSON array is rejected; export JSON lines instead.
Check each event has event, time and distinct_id. time can be Unix seconds, Unix milliseconds or an ISO timestamp. In JSON lines these fields can sit under properties. In CSV, a header row must name the fields.
In Supermetry, open the target site and select Settings → Imports & export. Only owners and admins can import.
Choose Mixpanel (event export), select the file, and select Preview import.
Review the counts, date range, skipped rows (with line numbers) and any overlap warnings, then select Confirm import.

What you should see: the history lists the file as Completed, and the imported days appear in supported dashboard totals and breakdowns.

How events are read

Used when present: $insert_id for de-duplication, page path or URL, referrer, mp_country_code, $region, $city, $browser and $os.
Times without an offset are read as UTC. Each event is counted on the site’s local day.
Each visitor on each day becomes one visit. A visit with exactly one page view is a bounce; its duration runs from the first to the last event.
Page-view events fill pages, entry and exit pages and daily totals. All other events become custom events. Identity and session bookkeeping events such as $identify and $create_alias are ignored.
Events with the same name, time, user and insert id count once, including across files in a ZIP.

IP addresses, user agents and user or device ids are never stored. Ids are hashed in memory only to group events while the file is read. URLs keep only their path, and only a two-letter country code is kept.
The newest completed import wins for each day; live tracking data always wins. Re-importing an overlapping range does not double count, and Undo in the history removes an imported batch.
Limits: 512 MB per upload, 5,000,000 event rows, 2,000,000 visitor-days, 1 MiB per line, 1,000 ZIP entries, and 2 GiB per file and 8 GiB in total after decompression.