Migrate from Google Analytics 4

trckable imports GA4's events one row at a time, from the BigQuery export. It does not import GA's reports or its Data API summaries: those are totals, and totals cannot become visits. The general order (run both for a week, import, compare, switch) is on Migrating.

GA4 keeps its events to itself, except through its BigQuery export, which has every pageview and event one row at a time. That is what trckable imports.

1. In GA4, open Admin → Product links → BigQuery links and link a Google Cloud project, with the daily export on. The free BigQuery sandbox is enough.

2. Export the events as newline-delimited JSON to a bucket:

   EXPORT DATA OPTIONS (uri = 'gs://your-bucket/ga4-*.json', format = 'JSON') AS
   SELECT event_timestamp, event_name, event_params, user_pseudo_id,
          device, geo, collected_traffic_source
   FROM `your-project.analytics_123456789.events_*`

3. Stream it straight in:

   gcloud storage cat 'gs://your-bucket/ga4-*.json' | trckabled import tkb_a1b2c3d4 -

What comes across:

Two things to know first:

• The BigQuery export is not retroactive. It starts on the day you link it, so history from before then exists only as GA's own summaries, which cannot become real events. Link it now, even if you import later.
• Money stays with your payment provider. A GA4 purchase arrives as a goal; revenue comes from connecting Stripe and the others, which is where the real amounts, refunds and currencies live.

GA4 records no time-on-page per pageview in a form that survives the export, so imported days show bounces as single-page visits, the same as any tool without engagement data.

Then

Run both scripts for a week, compare, and remove the Google tag (and, if the banner was only there for GA, your cookie banner: see Privacy). Why GA's numbers and trckable's differ is explained on Migrating.