Import Data

Bring your history with you. The import module backfills a Kitbase project with analytics from another platform so your dashboards show data from before you switched. The first supported source is Google Analytics 4 (GA4).

Imports are a one-time backfill over a date range you choose. They run in the background, survive restarts, and can be re-run after deleting the old data.

Connect Google Analytics

1. Open a project, go to Settings, and select the Import tab.
2. Click Connect Google Analytics and grant Kitbase read-only access (the analytics.readonly scope). Kitbase never writes to your GA4 account.
3. One Google account is connected per organization. Disconnect any time from the same page or from Organization → Integrations.

Run an import

1. Pick a GA4 property from the connected account.
2. Choose a start and end date. The end date must be before today — the current day is still incomplete in GA4.
3. Click Start import. Progress shows day-by-day; you can leave the page.

Imported data lands in the same tables as live tracking, so every existing dashboard (Web Analytics, top pages, sources, devices, countries) includes it automatically over the imported range.

What gets imported, and how accurate it is

GA4's API exposes aggregated reports (metrics grouped by dimensions per day), not raw events. Kitbase expands those aggregates into per-session events, one day at a time. That means:

Metric	Accuracy
Pageviews (per page, per day)	Exact — matches GA4's "Views".
Sessions (total, and per source / device / country)	Exact (within GA4's own rounding).
Unique visitors	Approximated. Per-day visitor counts are close; weekly/monthly uniques run slightly high because GA4 de-duplicates visitors across days and an aggregate import cannot.
Bounce rate, average session duration	Reconstructed from GA4's daily figures.
Referrers	Shown as GA4 source names (e.g. google), not full referring URLs.

A few things to know:

• Time zone. GA4 days are labelled in your property's time zone but stored in Kitbase as UTC days, so day boundaries can differ slightly from the GA4 UI if you view dashboards in another time zone.
• Speed. Google limits how fast historical data can be read. Multi-year imports can take a while and may pause and resume as quotas refill — this is normal; the import continues on its own.
• Billing. Imported events do not count toward your monthly event or session limits.

Delete imported data

Each import in the history list has a Delete data action. It removes every event and session that import wrote, and frees the date range to be imported again. Deletion runs in the background and can take a few minutes to reflect in dashboards.

To re-import a range you already imported, delete the existing import's data first — overlapping imports are rejected to avoid double-counting.

Permissions

• Connecting or disconnecting a source needs the integration create/delete permission (Owner, Admin).
• Starting, cancelling, or deleting an import needs dataimport.manage (Owner, Admin, Developer). Viewing imports needs dataimport.view (also Analyst).