Updated 2026-10-24

GA4 Looker Studio template guide (including AI referral traffic)

Google Analytics 4 has plenty of data, but its built-in reports are hard to share with people who don’t live in GA4. A Looker Studio (now Data Studio) report fixes that. You get one link, one layout, and the numbers your team or clients care about. This guide covers what a GA4 Looker Studio template should include, how to connect it, how to measure visits from AI assistants such as ChatGPT and Perplexity, and how to avoid the quota errors that break many GA4 dashboards.

Our free GA4 Starter template uses the structure described here.

Connecting GA4 to Looker Studio

Google’s native Google Analytics connector is free. According to Connect to Google Analytics, you need at least Read & Analyze (Viewer) access to the GA4 property. The steps:

  1. Click Create → Data source and choose Google Analytics.
  2. Select the account and the GA4 property, then click Connect.
  3. Review the fields and click Create report, or add the source to a copied template.

Two limits from Google’s documentation are worth knowing before you design anything:

The metrics that matter

GA4’s names changed several times after Universal Analytics, so use the current field names as they appear in the connector:

MetricWhat it tells you
Active usersPeople who engaged during the period (GA4’s main “Users” count).
New usersFirst-time visitors.
SessionsVisits.
Engaged sessions / Engagement rateVisits that lasted longer than 10 seconds, had a key event, or had 2+ page views. This replaces bounce rate as the quality signal.
Average engagement time per sessionHow long people actually paid attention.
Key eventsWhat GA4 used to call “conversions”. Mark your important events as key events in GA4 Admin.
Session key event rateShare of sessions with a key event.
Total revenueFor ecommerce or anything with a monetary value.

Show the headline metrics as scorecards compared with the previous period, as you would in any Looker Studio report.

A five-page structure

1. Overview

Scorecards for the metrics above, plus a time series of Sessions and Key events by Date.

2. Acquisition

Use session-scoped dimensions (Session source, Session default channel group) with session metrics. Mixing user-scoped “First user…” dimensions with session metrics is a common reason dashboards look wrong.

3. Pages

4. Events

Event name × Event count and Key events. This page is where you check whether tracking still works: a form-submit event that drops to zero usually means a broken tag, not a sudden lack of interest.

5. Audience

Country (geo map), Device category and New / established.

Put a date range control and a data control (to switch GA4 property) at the top of every page, plus filters for channel group, device and country. The data control is what lets someone preview the template with their own property (Data control).

Tracking traffic from AI assistants

More and more teams want to know how many visits come from ChatGPT, Perplexity, Gemini, Claude, Copilot and similar tools. GA4 has no dedicated AI channel in its default channel group: check Google’s current Default channel group definitions, because the list changes. These visits usually land in Referral, sometimes Direct, and sometimes elsewhere when the link carries UTM tags.

Option 1: a filtered table in Looker Studio (no GA4 changes)

Add a table with Session source, Sessions, Engaged sessions and Key events. Then add a filter:

Or create a calculated field so you can group the sources:

CASE
  WHEN REGEXP_MATCH(Session source, "(?i).*(chatgpt|openai).*") THEN "ChatGPT"
  WHEN REGEXP_MATCH(Session source, "(?i).*perplexity.*") THEN "Perplexity"
  WHEN REGEXP_MATCH(Session source, "(?i).*(gemini|bard).*") THEN "Gemini"
  WHEN REGEXP_MATCH(Session source, "(?i).*(claude|anthropic).*") THEN "Claude"
  WHEN REGEXP_MATCH(Session source, "(?i).*copilot.*") THEN "Copilot"
  ELSE "Other"
END

Filter out “Other”, and you have an AI-referral breakdown you can chart over time.

Source strings vary (for example chatgpt.com as a referrer, or chatgpt.com as a utm_source added by the assistant). Before you trust the regex, open GA4’s Traffic acquisition report, look at your actual Session source values, and adjust the pattern to match them.

Option 2: a custom channel group in GA4

GA4 lets admins create custom channel groups with rules based on source, medium and other fields. Add an “AI assistants” channel above Referral, using a source regex like the one above. The new channel group then shows up as a dimension in Looker Studio, and the AI traffic appears next to Organic Search and Paid Search in every channel table.

Be honest about the limits

Avoiding GA4 quota errors

Since late 2022, Looker Studio reports on GA4 data have been subject to Google Analytics Data API quotas. Busy or chart-heavy reports can show errors like “This property has issued too many requests in the last hour” or “Exhausted concurrent requests quota” (Looker Studio troubleshooting).

What helps, based on Google’s guidance:

Common reasons GA4 dashboards look “wrong”

  1. Comparing with Explorations. The connector matches standard reports.
  2. Mixing scopes. A user-scoped dimension with session metrics gives confusing totals.
  3. Unmarked key events. If a key event wasn’t marked in GA4 Admin yet, it won’t appear for earlier dates.
  4. Thresholding. With Google signals on, GA4 may hide rows with small counts.
  5. Time zone. Reports use the property’s time zone.

Checklist

Get the template

The free GA4 Looker Studio template includes all five pages and the AI-referral table. Preview it on your own property through the data control, then make a copy. If you manage several properties or clients, the multi-client pack adds a cross-property roll-up and white-label client pages for $39 one-time, with a 14-day refund.