Skip to content
Supermetry

Migrate from Amplitude

Import an Amplitude export into one Supermetry site, with a preview and undo.

Upload an Amplitude event export to rebuild daily traffic history in Supermetry. Nothing is stored until you confirm the preview.

  1. Export your events from Amplitude. The export is usually a ZIP of hourly .json.gz files; upload it unchanged. A single .json, .jsonl, .csv or .gz file also works. A JSON array is rejected; use JSON lines.

  2. Check each event has event_type, event_time and user_id or device_id.

  3. In Supermetry, open the target site and select Settings → Imports & export. Only owners and admins can import.

  4. Choose Amplitude (event export), select the file, and select Preview import.

  5. Review the counts, date range, skipped rows (with line numbers; inside a ZIP the message names the file) 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

Section titled “How events are read”
  • Used when present: $insert_id (or uuid) for de-duplication, page path or URL, referrer, country, region, city, platform and os_name.
  • 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. Page-view events fill pages, entry and exit pages and daily totals; other events become custom events. Session start and end events are ignored.
  • Events with the same name, time, user and insert id count once, across all files in a ZIP.

Privacy, overlap and limits

Section titled “Privacy, overlap and limits”
  • IP addresses, user agents and user or device ids are never stored. 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 are the same as for Mixpanel: 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.
Section titled “Related”