Skip to content
Start in Cloud

Import Simple Analytics Data

HitKeep imports Simple Analytics history from the raw datapoints CSV. In Simple Analytics, open the website settings, choose Export data, click Go to our export page, then export All data as CSV for the date range you want to migrate. In HitKeep, use the Imports page for the destination site.

You need access to the Simple Analytics website you are moving and site.manage_data access for the destination HitKeep site.

HitKeep accepts any .csv file whose header matches the Simple Analytics raw datapoints schema. The filename is only used for display, validation warnings, and import history.

  1. Open Simple Analytics and select the website.
  2. Go to Website settings.
  3. Open Export data.
  4. Click Go to our export page.
  5. Set the export type to All.
  6. Pick the date range you want to import.
  7. Set the format to CSV.
  8. Click Export and download the datapoints CSV.
Simple Analytics website settings page with the Website settings button highlighted
Start from the website settings for the Simple Analytics site you want to move.
Simple Analytics Export data settings showing the Go to our export page link
The website settings export panel links to Simple Analytics’ dedicated export page.
Simple Analytics export page with All data selected and CSV chosen as the export format
Choose All data and CSV so HitKeep receives the raw datapoints file.

Use All rather than a single report export. HitKeep expects the raw datapoints CSV with fields such as added_iso, datapoint, path, document_referrer, device_type, country_code, is_unique, and duration_seconds. If the export includes optional fields such as browser_name, browser_version, lang_language, and lang_region, HitKeep imports those into browser and language reports too.

  1. In HitKeep, select the destination site.
  2. Open Imports from the left navigation.
  3. Choose Simple Analytics as the importer.
  4. Upload the downloaded datapoints CSV.
  5. Run validation and review the date range, row counts, accepted rows, skipped rows, and warnings.
  6. Start the import after the validation summary matches what you expect.
HitKeep Imports page with Simple Analytics selected and the CSV upload drop zone visible
Open Imports in HitKeep, choose Simple Analytics, then upload the datapoints CSV.

The import writes to the currently selected HitKeep site. If you manage multiple sites, check the site switcher before uploading the CSV. HitKeep uses that selected site’s domain to suppress self-referrers from the imported source breakdown.

The CLI reuses HITKEEP_PUBLIC_URL when it is already set, and otherwise talks to http://localhost:8080. Pass --url only when running the command from a different machine.

You can validate the same file from the command line:

Terminal window
hitkeep import validate simpleanalytics --site <site-id> --file simple-analytics-export.csv

Start the import after reviewing the manifest:

Terminal window
hitkeep import simpleanalytics --site <site-id> --file simple-analytics-export.csv --wait

HitKeep imports Simple Analytics pageview history into compatible aggregate reports:

Simple Analytics fieldHitKeep report data
added_isoDaily traffic date
is_uniqueVisitors and visits
datapoint=pageviewPageviews
duration_secondsVisit duration totals
pathTop pages
document_referrerTop sources
device_typeDevice breakdown
country_codeCountry breakdown
browser_name / browser_versionBrowser breakdown when present
lang_language / lang_regionLanguage breakdown when present
utm_sourceUTM source breakdown

Simple Analytics datapoints exports do not include everything HitKeep can track natively. Bounce counts and native HitKeep event relationships are not invented during import. Browser and language dimensions are imported only when the CSV includes the relevant fields. If the CSV contains unsupported datapoint types, validation reports them as skipped rows so you can review the coverage before importing.

Open the destination site’s dashboard and select the imported date range. The imported pageviews, visitors, pages, sources, devices, countries, browser names, language codes, and UTM source data appear in compatible historical reports when those fields exist in the CSV.

For API automation, use the import endpoints under the Imports API reference.