Quri

Google Analytics 4

Last updated 2026-06-14

What this unlocks

Connect Google Analytics 4 and Quri reads your traffic and active-user trends — sessions, channels, and conversions — so it can answer "how did acquisition move this week?" and alert you when traffic drops, without you building a GA4 report.

Connect it in Quri

  1. Open /app/connect in Quri and choose Google Analytics 4 from the list of sources.
  2. Click Connect to start Google sign-in, then approve read-only access to your Analytics data in the Google window.
  3. You land back in Quri at /app/connect/google-analytics-4/select — pick the GA4 property you want Quri to read from the discovered list.
  4. Save the connection. Quri keeps a refresh token, so you authorize once and it stays connected.
  5. For per-user journey stitching in Atlas, also turn on the BigQuery export (see the provider steps) — the standard connection returns aggregated reports, while the export gives Quri raw event rows.
  6. Wait for the first sync — your GA4 traffic and active-user metrics appear in Quri once it completes.

Get your credentials

  1. You connect GA4 through Google sign-in, so there is no key to copy — but the Google account you sign in with needs at least Viewer access to the GA4 property.
  2. In Google Analytics, open Admin → Property → Property access management and confirm your account has a role on the property you plan to pick in Quri.
  3. If you run your own Google Cloud OAuth app instead of Quri-hosted sign-in, enable the Google Analytics Data API in Google Cloud Console under APIs & Services → Library, then add your account to the OAuth consent screen.
  4. BigQuery export option (for Atlas journeys): in Google Cloud Console enable the BigQuery API, then in Google Analytics open Admin → Product links → BigQuery links → Link, choose your Cloud project and a data location, and turn on Daily export. You need Editor or above on the property and Owner on the BigQuery project; GA4 takes up to 24 hours to write the first export tables and does not backfill history.

Access Quri reads with

  • https://www.googleapis.com/auth/analytics.readonly — read-only access to your GA4 reporting data. Quri never writes to or changes your Analytics configuration.
  • https://www.googleapis.com/auth/bigquery.readonly — read-only access to the export dataset, used only when you enable the BigQuery export for per-user journeys.
  • Quri requests offline access so it can refresh the token in the background; you do not have to re-authorize each sync.

Troubleshooting

After I sign in, Quri shows no GA4 properties to pick.
The Google account you authorized with has no access to any GA4 property. In Google Analytics, open Admin → Property access management and grant that account at least Viewer on the property, then reconnect at /app/connect.
My GA4 numbers in Quri do not exactly match the GA4 dashboard. Why?
GA4 applies data thresholding and sampling on large or low-volume date ranges, and it measures client-side — ad blockers and consent choices mean some sessions never get recorded. Quri reads the same Data API GA4 serves its own reports from, so it inherits those limits. Treat the figures as directional, not a hard ledger.
I linked the BigQuery export but no per-user journey data shows up.
GA4 takes up to 24 hours to write its first export tables and never backfills history, so right after linking there may be nothing to read. Confirm in BigQuery that the dataset (named analytics_<property-id>) has events_ tables, and that the BigQuery API is enabled on the project, then let Quri sync again.

Related guides