Build a GA4 marketing dashboard in Looker Studio

#01Page plan

Optional page 4 becomes the AI visibility board in lesson 13.

#02Recommended fields

Scorecards: Sessions, Engaged sessions, Key events, Session key event rate, AI Assistant sessions (filtered scorecard or calculated split).

Dimensions: Date, Session default channel group, Session source, Session medium, Landing page + query string, Device category, Country.

Metrics: Sessions, Engaged sessions, Engagement rate, Key events, Total users (use carefully with thresholds), Event count for specific events if needed.

Avoid high-cardinality custom dimensions on large tables in the shared report. Put those in a separate exploration-style page for analysts only.

#03Setup steps

1. Reuse GA4 — Brand Prod (owner) from lesson 4.
2. Credentials: owner. Freshness: 12 hours.
3. Overview page with date control default last 28 days + comparison previous period if your stakeholders understand comparisons.
4. Acquisition page: table of Session default channel group with sessions, engaged sessions, key events, rate.
5. Add secondary table for Session source filtered to Session default channel group = AI Assistant.
6. Behaviour page: landing pages sorted by key events.
7. Footer on every page with freshness and "GA4 UI may differ within the day".
8. Share as viewer to the marketing group.

Link Search Console and Google Ads in GA4 itself (guide) even though this dashboard reads GA4 only — it keeps definitions aligned when you add blends later.

#04AI Assistant versus Organic Search

Google's default channel group documentation states the AI Assistant channel covers visits from sources like ChatGPT, Gemini, Deepseek, Copilot or Grok, and excludes Google's AI Overviews and AI Mode. Those remain Organic Search. So:

#05Quota hygiene (summary)

From Google's troubleshooting guide and Academy's GA4 lesson:

• Prefer owner credentials so viewers share cache.
• Reduce charts; avoid embedding on high-traffic intranet pages.
• Consolidate duplicate GA4 data sources.
• Extract data for stable weekly snapshots.
• Move heavy analysis to BigQuery (lesson 18).
• Analytics 360 raises limits if you already pay for it — do not buy 360 only for Looker Studio.

Right-click the canvas or a chart and open Google Analytics token usage to see which charts cost the most.

#06Field and chart budget (detail)

#07Worked example: Ledgerline

Ledgerline is a fictional accounts-payable software company. Details are illustrative.

Walkthrough

1. First draft had 18 charts and failed for sales viewers at Monday standup.
2. Ops cut vanity metrics, switched to owner credentials, set freshness to 12 hours.
3. AI Assistant scorecard stopped leadership from calling all organic growth "AI".
4. Landing-page table highlighted /integrations/netsuite rising with AI sessions (illustrative).
5. They linked this report from the GA4 monthly AI measurement routine.

#08Suggested calculated / filtered metrics

#09Internal traffic and thresholds

If internal traffic still pollutes marketing numbers, fix it in GA4 Admin (data filters) rather than asking every Data Studio chart to exclude it. Thresholding can zero thin segments — verify in the GA4 UI before filing a Data Studio bug.

#10Pairing with GTM and measurement lessons

• GTM AI referral traffic to GA4
• Track AI traffic in GA4
• GA4 monthly AI measurement routine

The dashboard visualises what tagging and channel rules already collect. It cannot invent referrals that never hit GA4.

#11Landing page table hygiene

• Show top 25 by key events, not top 1,000 by sessions.
• Strip PII-looking query parameters in GA4 redaction settings upstream when possible.
• Add a secondary page for analysts with longer lists and secondary dimensions.
• Do not put "Landing page + query string" next to a high-cardinality custom dimension on the shared page — that combination is a timeout classic.

#12Common mistakes

• Labelling all Google traffic as AI.
• Viewer credentials on a company-wide link.
• Hourly freshness "just because".
• Huge landing-page tables with secondary dimensions that timeout.
• Ignoring token usage until the week of a board meeting.

#13Try it yourself

Build the three-page GA4 report. Add an AI Assistant sessions scorecard. Open token usage and note the top three charts. Remove or simplify one.

#14Quick quiz

1. Which channel holds ChatGPT web referrals in GA4's default group?

Answer: AI Assistant.

2. Where do AI Mode visits show up?

Answer: Organic Search (not AI Assistant).

3. Name two quota mitigations.

Answer: Any two of: owner credentials, fewer charts, shared data sources, extracts, BigQuery, less embedding, longer freshness.

#15What should you check before the next lesson?

• Three-page GA4 report shared.
• AI Assistant separated from Organic.
• Token usage checked once on a cold load.

Previous: Themes and layouts for Looker Studio reports. Next: Build a Google Ads dashboard in Looker Studio. Or return to the Looker Studio for Marketers track. Related: GA4 Looker Studio reporting, GA4 AI Assistant channel regex, Track AI traffic in GA4, GTM AI referral traffic.

#16Common questions

Why does my GA4 Looker Studio report show quota errors? Reports that connect to GA4 are subject to Google Analytics Data API quotas. Too many charts, viewer credentials, embeds or short freshness windows burn tokens. Use owner credentials, fewer charts, extracts or BigQuery.

Should AI Mode traffic appear in an AI Assistant scorecard? No. GA4 puts AI Overviews and AI Mode in Organic Search. The AI Assistant channel covers assistants like ChatGPT, Gemini, Perplexity and others. Report them separately.

Is this the same as the Academy GA4 Looker Studio lesson? That page is the GA4-track deep dive on quota-safe reporting. This lesson builds the multi-page marketing dashboard and links there for quota detail.