Numative

Import & export

Bring history from Plausible, Fathom or GA4 exports, import event CSVs, and export everything back out.

Import and export live under your site's Import tab and work on standalone sites (data flows into Numative's own event store). Sites in GA4 mode keep their data in Google Analytics, so the tab is hidden there.

Supported imports

Two shapes are supported. Event files carry one row per hit and keep full detail. Aggregate files carry per-day totals; Numative synthesizes pageview events from them that reproduce your visitor, pageview and bounce-rate numbers, but detail dimensions are only as rich as the file.

SourceFormatNotes
Numative (JSON)EventsThe file produced by Export events (JSON) on this tab, or any JSON with an events array. Full fidelity, including props, revenue and bot flags.
Events CSVEventsGeneric per-hit CSV; also fits Umami event exports.
Plausible (CSV)AggregateThe visitors.csv per-day export.
Fathom (CSV)AggregateFathom's aggregate export.
Google Analytics (CSV)AggregateA GA4 daily export with date, users and pageviews columns.

For events CSVs, columns are matched by header name. Recognized headers include timestamp, path, name, referrer, session_id, visitor_hash, country, browser, os, device, UTM columns and revenue. A minimal file works:

events.csvcsv
timestamp,path,name,referrer
2026-05-01T09:14:00Z,/pricing,pageview,https://news.ycombinator.com
2026-05-01T09:16:30Z,/signup,Signup,

Run an import

  1. 1

    Pick the source

    On the site's Import tab, choose the source that matches your file. The choice decides how the file is parsed, so pick Plausible, Fathom or Google Analytics for those exports rather than the generic CSV option.

  2. 2

    Choose the file and import

    Select the .csv or .json file and click Import. The import runs inline and reports how many events were created.

  3. 3

    Check the history

    Every run appears in the import history table with its status, row count and date. Failed imports show the error; a file with no usable rows is marked failed rather than silently importing nothing.

Imports are reversible

Every imported event is tagged with the import's id, and imported events are never counted as bot traffic. To undo an import, click the undo button on its row in the history table: all events carrying that import id are deleted from the event store and the import is marked reverted. This makes it safe to try an import, inspect the result and redo it with a cleaner file.

Limits

  • Up to 200,000 events per import; rows beyond that are cut off. Split very large histories into multiple files.
  • Uploaded files can be up to about 40 MB of text.

Export

The Import tab's export card downloads your site's all-time data:

  • Export events (JSON): every raw event, ordered by time, with path, referrer, session and visitor identifiers, location, device, UTM fields, custom props, revenue and bot flags. The file re-imports into Numative at full fidelity using the Numative (JSON) source, so you can move a site between accounts or keep an offline backup.
  • Export timeseries CSV: one row per day with visitors, visits and pageviews.

Events exports are capped at 200,000 events per file, matching the import ceiling. A capped file has "truncated": true in its metadata.

Individual reports elsewhere in the dashboard, such as the Search tab, have their own CSV export buttons scoped to the selected date range.