Importing data
Bring past analytics into your site's dashboard from a Plausible or Fathom export. The import uses your chosen timezone to interpret the source dates.
Open Import
Select your site, then open Site settings → Import. New imports require a Growth or Business plan. If your account is on Starter after importing data, you can still view the import history and delete imported data; the upload controls are gated. Select the site that should receive the history before you upload.
Choose and upload files
Choose Plausible or Fathom, select the export files, and set the import timezone that matches the source data. The timezone starts with the site's setting, but you can change it for this import. Then submit. The form needs a vendor and at least one file; Simple Analytics is not an upload choice. An invalid file, conflicting dates or timezone, or an import already in progress can stop the upload. Read the error shown in the panel before trying again.
Read the import history
After submitting, check Import history for the job's status, date range, imported rows and skipped rows. A completed import can have warnings and be marked done (partial); review those warnings before treating the history as complete. A failed job shows its error. If the connection fails while the panel checks the result, reload the history to confirm the job's final state before submitting another import.
Imported history is stored as daily aggregates. It can contribute to dashboard totals, but it is separate from live tracked event rows and is not included in the current CSV or JSON export.
Delete imported data and understand usage
Use a completed job's delete action to remove that batch's imported data, or use Delete all imported data to remove imported history for the site. Confirm the scope in the dialog; these actions do not remove live tracked events. See deleting data for the other deletion paths.
The monthly event quota counts billable events across all sites in your account and resets by UTC calendar month, not on your Stripe billing anniversary or local month boundary. page_exit is an internal enrichment event and does not consume that quota, even when stored. Imported daily aggregates are separate from the live event rows counted by the ingest quota.