Connecting Google Analytics 4 on Clarisights

Google Analytics 4 (GA4) is Google's property-based, event-driven analytics platform that replaced Universal Analytics on 1 July 2023. Connecting GA4 to Clarisights pulls session, engagement, and conversion data — including event-level revenue and custom events — through the GA4 Data API v1, so you can blend on-site behaviour with paid media performance in the same report.

This article covers the Google Analytics 4 integration. If you're still on legacy Universal Analytics (UA) and have a UA property ID (e.g. UA-12345-1) rather than a GA4 numeric property ID, see Integrating Google Analytics on Clarisights for the UA connector.

At a glance

Authentication	Google OAuth 2.0 with the https://www.googleapis.com/auth/analytics.readonly scope
Permissions needed	Viewer role or higher on every GA4 property you want to connect
Account discovery	Automatic — every GA4 account → property your Google user can access is offered for selection
Data freshness	Daily, with a 3-day rolling refresh to catch late-attributed sessions and events
Lookback window	3 days on every refresh; deeper backfills available on request
Backfill on connect	Last 3 days by default — contact support for a longer historical backfill
Timezone	Property-level timezone (configured in GA4 admin)
Currency	Property reporting currency (configured in GA4 admin)
Levels supported	Account / Property · Source · Medium · Campaign · Ad Group (sessionManualTerm) · Ad (sessionManualAdContent)
Limited rollout	No

Prerequisites

• An active GA4 property in Google Analytics with a numeric property ID (visible under Admin → Property Settings)

• A Google account with at least Viewer access on every GA4 property you want to connect

• Permission on your Google account to authorize third-party apps (some Workspace policies block this)

• UTM tagging on your paid traffic if you want Clarisights to dereference GA4 sessions back to Campaign / Ad Group / Ad in your ad-channel reports

Steps to Connect

Step 1 — Sign in with Google from Clarisights

In Clarisights, go to Integrations → Google Analytics 4 and click Connect. You'll be redirected to Google to authenticate. Sign in with the Google account that has access to the GA4 properties you want to connect.

[TODO: Screenshot needed — Integrations page Google Analytics 4 row]

Step 2 — Authorize Clarisights

Google will show a permission screen requesting the analytics.readonly scope. Click Allow.

⚠ "Access blocked" / "This app is blocked" → Your Google Workspace admin restricts third-party apps. Ask the admin to allowlist Clarisights, or sign in with a Google account whose organisation permits OAuth to external apps.

Step 3 — Select GA4 properties

After authorization, Clarisights lists every GA4 account and property your Google user can access. Pick the properties you want to connect, optionally rename them, and click Create Accounts.

⚠ "Property not visible" / property missing from the list → The Google user does not have access to that GA4 property. Ask the property's admin to grant Viewer role and reload the integration. Note: GA4 properties are different from Universal Analytics views — if you only see UA views in the list, you signed in to the wrong integration. Use this Google Analytics 4 connector for GA4 properties.

Step 4 — Configure dimensions, metrics, and source / medium mapping

Clarisights pre-configures GA4 to pull session-level dimensions (sessionSource, sessionMedium, sessionCampaignName, sessionManualTerm, sessionManualAdContent) plus date. Confirm the source / medium values that should map to each ad channel (e.g., google / cpc → Google Ads, facebook / paid → Facebook Ads). This is what lets Clarisights dereference GA4 sessions and conversions back to your paid-media campaigns and ads.

Verify the connection

• Go to Integrations → Google Analytics 4. Each connected property should show a "Connected" status with its property ID.

• First data appears at the next scheduled refresh (within ~24 hours).

• Quick start: create a new report, add Google Analytics 4 as the data source, and add Source · Medium · Campaign · Sessions · Total Revenue.

Data available

Hierarchy

GA4 doesn't have ad-style account / campaign / ad group / ad levels natively — data is event-based. Clarisights uses GA4's session-level traffic dimensions to map onto the standard Clarisights levels:

Native field (GA4)	Clarisights level
Property (numeric ID)	Account
sessionSource	Source
sessionMedium	Medium
sessionCampaignName	Campaign
sessionManualTerm	Ad Group
sessionManualAdContent	Ad
Event Name (e.g. purchase, sign_up, custom events)	Event-level metric in event reports

Because GA4 uses session-scoped attribution, dereferencing back to your paid campaigns relies on accurate UTM tagging in your ad URLs.

Dimensions

Dimension	Level	Description
Property ID / Property Name	Account	GA4 numeric property ID and configured name
Date	All	Day of session
Session Source	Source	sessionSource
Session Medium	Medium	sessionMedium
Session Campaign Name	Campaign	sessionCampaignName (mapped from UTM utm_campaign)
Session Manual Term	Ad Group	sessionManualTerm (mapped from UTM utm_term)
Session Manual Ad Content	Ad	sessionManualAdContent (mapped from UTM utm_content)
Event Name	Event report	Event identifier (standard GA4 events plus your custom events)
Additional dimensions	Configurable	Any GA4 Data API dimensions you add to the channel config (e.g., deviceCategory, country, landingPage)

Metrics

Base session metrics

Metric	Description
Sessions	sessions — total sessions
Engaged Sessions	engagedSessions — sessions meeting the engagement threshold
New Users	newUsers — users in their first session
Total Revenue	totalRevenue — aggregate revenue from purchases and other monetised events
Transactions	transactions — ecommerce transaction count

Event-level metrics

Metric	Description
Event Count	eventCount — total events of the named type
Event Value	eventValue — total value associated with the event (where set)

Custom metrics

Any GA4 metric you add in the Clarisights channel configuration is included in the daily report — up to 10 metrics per request (Clarisights batches more than 10 automatically).

Limitations & known constraints

• Different from Universal Analytics: GA4 properties are not interchangeable with UA views. Use this connector for GA4 numeric property IDs only; UA views (UA-...) require the legacy Google Analytics integration.

• 10 metrics per Data API request: GA4 Data API limits each runReport call to 10 metrics. Clarisights splits larger metric sets into multiple batched calls; this can extend ingest time on properties with many custom metrics.

• Concurrent request limit: GA4 enforces a concurrent request limit of 10 per project. Clarisights caps DAG parallelism at 3 to stay well within quota.

• Data sampling and thresholding: GA4 may sample or apply thresholds (especially when Google Signals is enabled or for low-volume queries). Sampled rows are returned as GA4 reports them.

• UTM tagging required for dereferencing: GA4 attribution to paid-media campaigns / ad groups / ads relies on utm_source, utm_medium, utm_campaign, utm_term, and utm_content. Untagged or auto-tagged-only traffic won't dereference reliably.

• Token revocation: revoking the Clarisights connection in your Google account stops all syncing until you re-authenticate.

Operating notes

• Refresh schedule: daily, with a today + 3-day lookback to catch late-attributed events.

• Lookback: 3 days on every run.

• Adding new properties: when a new GA4 property is created in Google Analytics, return to Integrations → Google Analytics 4 and re-discover. Existing properties are not re-prompted.

• Source / medium mapping: review the source / medium → ad-channel mapping after connecting a new property so GA4 sessions dereference correctly into your paid-media reports.

• Currency conversion: amounts are pulled in the GA4 property's reporting currency and converted to your Clarisights reporting currency.

• Credential rotation: OAuth tokens auto-refresh. You only need to re-authenticate if you change your Google password or revoke the Clarisights connection.

Need help?

When contacting support from the in-app messenger, please include:

• The integration name and GA4 property ID (Integrations → Google Analytics 4)

• The exact error message or screenshot

• The step where the issue occurred

• When the issue started