# Build an AI Search Traffic Dashboard in Looker Studio (Free 2026 Guide) **URL:** https://organikpi.com/blog/technical-seo/ai-search-traffic-dashboard-looker-studio/ **Published:** 2026-06-10 **Modified:** 2026-06-26 **Author:** Daniel Shashko > A free Looker Studio dashboard isolates the AI search traffic GA4 buries under Direct and Referral: 70.6% of AI visits carry no referrer header (Loamly, 446,405 visits), while AI visitors sign up at 1.66% versus 0.15% for organic search (Microsoft Clarity, 1,200 sites). The build takes about 15 minutes: connect the GA4 connector, add an AI Engine calculated field (CASE on Session source), apply one reusable AI Traffic Only RegExp filter, then add scorecards, a time series, an engine donut, and a landing page table. On a real B2B SaaS property, 90 days showed 441 AI sessions: ChatGPT 52.8%, Gemini 15.6%, Perplexity 15.2%, Claude 11.3%. --- > A free Looker Studio dashboard isolates the AI search traffic GA4 buries under Direct and Referral: 70.6% of AI visits carry no referrer header (Loamly, 446,405 visits), while AI visitors sign up at 1.66% versus 0.15% for organic search (Microsoft Clarity, 1,200 sites). The build takes about 15 minutes: connect the GA4 connector, add an AI Engine calculated field (CASE on Session source), apply one reusable AI Traffic Only RegExp filter, then add scorecards, a time series, an engine donut, and a landing page table. On a real B2B SaaS property, 90 days showed 441 AI sessions: ChatGPT 52.8%, Gemini 15.6%, Perplexity 15.2%, Claude 11.3%. GA4 hides most AI search traffic inside Direct and Referral. A free Looker Studio dashboard fixes that in about 15 minutes. This guide builds one from scratch on a real B2B SaaS property, with a screenshot for every step, the exact AI source regex, and a calculated field that splits sessions by engine. The finished dashboard: 90 days of AI search traffic on a real B2B SaaS property (site anonymized) The measurement gap is large. [Loamly’s benchmark of 446,405 visits](https://www.loamly.ai/blog/state-of-ai-traffic-2026-benchmark-report) found that 70.6 percent of AI visits arrive with no referrer header. GA4 files those sessions under Direct. Meanwhile [Microsoft Clarity’s study of 1,200 publisher sites](https://clarity.microsoft.com/blog/ai-traffic-converts-at-3x-the-rate-of-other-channels-study/) measured AI visitor sign-up conversion at 1.66 percent versus 0.15 percent for organic search. AI traffic converts 11 times better than organic search. Reporting that channel as “Direct” is a budget allocation error, as we showed in our [GEO ROI analysis](https://organikpi.com/blog/seo-strategy/geo-roi-ai-traffic-revenue/). ## What you will build The dashboard takes 15 minutes and costs nothing. It contains four blocks: - **Three scorecards:** AI sessions, AI users, engaged AI sessions. - **A time series:** daily AI sessions over 90 days. - **A donut chart:** traffic split by AI engine ([ChatGPT](https://organikpi.com/blog/technical-seo/ga4-ai-search-referral-attribution/), [Perplexity](https://organikpi.com/blog/seo-strategy/perplexity-vs-google-market-share/), Gemini, [Claude](https://organikpi.com/blog/geo-ai-search/claude-ai-citation-strategy/), Copilot). - **A landing page table:** which pages AI engines actually send people to. We built this walkthrough on a live GA4 property of a B2B SaaS client (name blurred in every screenshot). Over 90 days the property logged 441 AI sessions from 285 users. Every number you see is real. ## Why GA4 hides your AI search traffic GA4’s default channel report routes most AI clicks into Referral or Direct. Here is the same client property in the standard Traffic acquisition report. Seven channels, no AI anywhere: 90 days of traffic, 441 AI sessions, and not a single AI row in the default channel report The traffic exists. Switch the dimension to Session source and search for chatgpt, and 231 sessions appear: chatgpt.com alone sent 231 sessions in 90 days, all buried under Referral and Direct Google did ship a native “AI Assistant” channel in late 2025. It helps, but it has three problems: - **It is not retroactive.** Historical AI sessions stay in Direct and Referral. - **It does not fire on every property.** The client property above still shows zero AI channel rows. - **The recognition list lags.** Newer engines and regional assistants are missing. The full fix on the GA4 side is a custom channel group, which we covered step by step in [AI Search Referral Attribution in GA4](https://organikpi.com/blog/technical-seo/ga4-ai-search-referral-attribution/). The Looker Studio dashboard in this guide works without touching GA4 admin settings, and it gives you a view you can share with clients and executives. ## Step 1: Connect GA4 to Looker Studio - Go to **lookerstudio.google.com** and click **Create, then Report**. - The “Add data to report” panel opens. Pick the **Google Analytics** connector. The Google Analytics connector sits first in the connector gallery - Select your GA4 **account**, then the **property**, and click **Add**. Pick the account and GA4 property, then confirm with Add - Optional but recommended: rename the data source. Go to **Resource, then Manage added data sources, then Edit**, and give it a clean name. Charts, filters, and tooltips will all display this name. ## Step 2: Create the AI Engine calculated field GA4 reports sources as raw hostnames: chatgpt.com, perplexity.ai, gemini.google.com, copilot.com. A calculated field groups them into readable engine names. One engine can also have several hostnames (chatgpt.com and openai.com both carry ChatGPT clicks), and the field merges those for you. - While editing the data source, click **Add a field, then Add calculated field**. - Name it **AI Engine**. - Paste this formula and click **Save**: CASE WHEN REGEXP_CONTAINS(Session source, "(?i)(chatgpt|openai)") THEN "ChatGPT" WHEN REGEXP_CONTAINS(Session source, "(?i)perplexity") THEN "Perplexity" WHEN REGEXP_CONTAINS(Session source, "(?i)(gemini|bard)") THEN "Gemini" WHEN REGEXP_CONTAINS(Session source, "(?i)copilot") THEN "Copilot" WHEN REGEXP_CONTAINS(Session source, "(?i)claude") THEN "Claude" WHEN REGEXP_CONTAINS(Session source, "(?i)grok") THEN "Grok" WHEN REGEXP_CONTAINS(Session source, "(?i)deepseek") THEN "DeepSeek" WHEN REGEXP_CONTAINS(Session source, "(?i)(mistral|lechat)") THEN "Mistral" ELSE "Not AI" END The AI Engine calculated field: one CASE statement turns raw hostnames into engine names Why split by engine at all? Because the engines behave differently. When we [decoded 42,971 AI citations](https://organikpi.com/blog/geo-ai-search/decoded-42971-ai-citations-google-research/), ChatGPT and Google’s AI surfaces shared almost no cited domains, and each engine picked sources by different rules. Engine level reporting tells you where your [citation velocity](https://organikpi.com/blog/seo-strategy/citation-velocity-measurement-framework/) is actually building. ## Step 3: Create the AI Traffic Only filter The filter is the heart of the dashboard. It keeps sessions whose source matches a known AI platform and drops everything else. - Select any chart, scroll to **Filter** in the Setup panel, and click **Add filter, then Create a filter**. - Name it **AI Traffic Only**. - Set the clause to **Include, Session source, RegExp Contains** and paste this pattern: (?i)(chatgpt|openai|perplexity|gemini|bard|copilot|claude|grok|deepseek|mistral|lechat|meta.ai|poe.com|you.com|phind) One reusable filter: Include, Session source, RegExp Contains, and the 2026 AI source pattern Save it once and reuse it everywhere. Every later chart attaches the saved filter with two clicks. Revisit the pattern quarterly: new engines launch, and a stale regex silently undercounts. This is the June 2026 list. ## Step 4: Add the four report blocks Use **Add a chart** from the toolbar and draw each block on the canvas. Configure them like this: BlockChart typeDimensionMetricFilter KPI cards (x3)ScorecardnoneSessions / Total users / Engaged sessionsAI Traffic Only TrendTime seriesDateSessionsAI Traffic Only Engine splitDoughnut chartAI EngineSessionsAI Traffic Only Cited pagesTableLanding page + query stringSessionsAI Traffic Only Two shortcuts save time. Build one scorecard fully, then copy and paste it twice and swap the metric; the copies keep the filter. And the doughnut’s dimension is the **AI Engine** field you created in Step 2. All four blocks wired up in the editor, every chart carrying the AI Traffic Only filter ## Step 5: Set a 90 day date range and read the results AI referral volumes are still small for most sites, so a 28 day window looks noisy. Select all charts, set **Default date range to Custom**, and use Advanced with **Today minus 90 days**. Here is the finished dashboard on the client property: The finished AI search traffic dashboard: 441 sessions, 285 users, five engines What 90 days of real data showed: - **ChatGPT drove 52.8 percent of AI sessions.** Below its 74.78 percent global share measured by [SE Ranking](https://seranking.com/blog/ai-traffic-research-study/) across 101,574 websites, because this client ranks well in Gemini and Perplexity. - **Gemini took 15.6 percent and Perplexity 15.2 percent.** Gemini referrals grew 388 percent year over year per [Similarweb data via Digiday](https://digiday.com/media/in-graphic-detail-the-state-of-ai-referral-traffic-in-2025/), so that slice will keep widening. - **Claude contributed 11.3 percent.** Worth watching if your audience is technical. - **The cited pages were almost all deep guides.** Not the homepage. AI engines send visitors to specific answers, which is exactly the behavior we map in our [zero-click strategy](https://organikpi.com/blog/geo-ai-search/zero-click-ai-search-strategy/) and [AI Overviews CTR analysis](https://organikpi.com/blog/seo-strategy/ai-overviews-ctr-impact/). ## What this dashboard still misses Referrer based tracking has a hard ceiling, and you should know where it is. Loamly’s February 2026 data puts 70.6 percent of AI visits in the “dark” bucket: no referrer header, classified as Direct. Mobile AI apps strip referrers, and many users copy URLs from answers instead of clicking. [SE Ranking’s study of 101,574 websites](https://seranking.com/blog/ai-traffic-research-study/) pegs visible AI referrals at just 0.15 percent of global traffic in 2025, up from 0.02 percent in 2024, a sevenfold rise. So treat the dashboard as your floor, not your ceiling. To close the gap: - Run [AI crawler log file analysis](https://organikpi.com/blog/technical-seo/ai-crawler-log-file-analysis-citation-optimization/) to see [GPTBot](https://organikpi.com/blog/technical-seo/ai-crawler-log-file-analysis-citation-optimization/), ClaudeBot, and PerplexityBot activity that never appears in GA4. - Track [brand visibility across the AI engines](https://organikpi.com/blog/seo-strategy/ai-brand-visibility-tracking-metrics/) directly, since citations precede clicks. - Measure [AI search share of voice](https://organikpi.com/blog/seo-strategy/ai-search-brand-share-of-voice/) against competitors, not just your own sessions. - Watch Direct traffic growth. If Direct grows faster than brand awareness, dark AI traffic is the usual cause. ## The 15 minute investment that reframes your reporting AI search traffic is small, fast growing, and converts far above organic. A dashboard that isolates it changes the conversation from “why is Direct up” to “ChatGPT sent 231 visitors to our pricing guides”. If you are new to the discipline, start with [what GEO is](https://organikpi.com/blog/geo-ai-search/what-is-geo-generative-engine-optimization/) and the [GEO KPI framework](https://organikpi.com/blog/seo-strategy/geo-kpi-measurement-framework/). And if you would rather have the whole measurement stack built for you, that is literally [what we do for clients](https://organikpi.com/services/geo-optimization/). ## Frequently Asked Questions ### Is the Looker Studio AI traffic dashboard free? Yes. Looker Studio is free, the GA4 connector is free, and the dashboard uses only native features: a calculated field, a regex filter, and standard charts. Total cost is zero, and the build takes about 15 minutes. ### Do I need a custom GA4 channel group before building the dashboard? No. The dashboard filters raw session sources directly in Looker Studio, so it works on any GA4 property without touching admin settings. A custom GA4 channel group is still worth adding separately for clean reporting inside GA4 itself. ### Which AI sources should the regex include in 2026? ChatGPT, OpenAI, Perplexity, Gemini, Copilot, Claude, Grok, DeepSeek, Mistral, Meta AI, Poe, You.com, and Phind. New engines launch regularly, so review the pattern quarterly; a stale regex silently undercounts the channel. ### How accurate is referrer based AI traffic tracking? It captures only the visible minority of AI visits. About 70.6 percent arrive without a referrer header and land in Direct, because mobile AI apps strip referrers and many users copy URLs instead of clicking, leaving under a third measurable this way. Treat the dashboard as a directional floor and pair it with AI crawler log analysis. ### Which metrics matter most on an AI search traffic dashboard? Engaged sessions and the landing page table. AI referral volume is still small for most sites, so quality and destination are the real signals: AI engines send visitors to specific deep guides, not the homepage, and those visitors convert far above organic search.