Import from Fathom

Bring daily Fathom Analytics history into your Seean website from a custom CSV export. You must own the Seean website. The import keeps your live events, orders, tracking token and saved reports intact and follows the same import modes (fill gaps, source-day selection, replace) as every file import.

Export the correct file

Seean needs one row per day with site-level totals. Fathom’s dashboard ZIP (Summary.csv, Pages.csv, …) contains period totals without dates and cannot be imported.

  1. In Fathom, open your site’s dashboard, click Export and choose Custom Export, or open Settings → your site → Exports. Click New export.
  2. Data type: Pageviews. Date range: the period you want to move; All Time is fine.
  3. Note the timezone shown for the export. Seean cannot read it from the file.
  4. Date grouping: Daily.
  5. Dimensions: none. Leave every dimension unselected so the file holds site-level totals; Fathom visitor counts cannot be added across dimension rows.
  6. Metrics: at least Pageviews and Visitors. Bounce Rate and Avg Time on Site may be included; they are kept as source text only.
  7. Preview, start the export and download the CSV. Keep your own original copy.

See Fathom’s export guide.

Upload in Seean

  1. Open your website, then Settings → Data → Import history.
  2. Source switches to Fathom automatically when the chosen CSV header contains Fathom’s metric names; you can also pick it yourself.
  3. Choose the CSV, select the Export timezone you noted in Fathom, then Upload and import. Keep the page open until the upload completes; validation continues in the background.
  4. Wait for ready and review days added and skipped. View rows shows the source day rows, including skipped days.

The limits from the Plausible guide apply: ten imports per website, one active import per website, three starts per hour, no demo websites, and one timezone per website.

What is imported

Per source day, Seean keeps visitors and pageviews and includes accepted complete days in the main unfiltered analytics. Fathom’s export has no visits metric, so full-period visits, bounce rate and duration show - when the range includes Fathom days. Bounce Rate and Avg Time on Site values remain unchanged as text under View rows; Seean does not invent visit counts or convert ambiguous units.

Daily visitor counts use Fathom’s definition and are summed into the selected period without cross-day deduplication. Pages, referrers, countries, devices, browsers and events are not imported from Fathom. See shared history behavior for filters, reports and API scope.

Limits and validation

  • Up to 25 MiB and 3,660 calendar days per file; one row per day.
  • Dates must be YYYY-MM-DD, optionally followed by a midnight time as produced by Daily grouping. Hourly, weekly or monthly exports are rejected.
  • Header names are matched to Fathom’s documented labels regardless of case and punctuation (Date/Timestamp, Pageviews, Visitors/Uniques, Bounce Rate, Avg Time on Site/Avg Duration). Any other column, including a dimension, fails with “Unsupported CSV columns”.
  • Counts must be non-negative integers. Duplicate days, invalid dates, ZIP or gzip files fail validation.

Fathom does not publish the exact header spelling of its CSV. If a genuine custom export is rejected, send the first line of the file (no data rows) to hello@seean.io.

Something unclear? Contact support.