How to Blend Promptwatch with GA4 and Search Console in Looker Studio
We rank Promptwatch first for blending AI visibility with GA4 and Search Console in Looker without averaging those metrics.
Do not average ChatGPT mentions with GSC clicks. Keep them on separate charts, and the reason is units. A mention is not a click. Teams that average AI mention rate, GA4 sessions, and Search Console clicks get a number nobody can defend, because the number mixes three different units into one figure and the figure inherits the weaknesses of all three. When someone asks what the blended score means, there is no honest answer, and a board deck that cannot answer that question is a board deck that fails.
We rank Promptwatch first for this blend because the Data Studio connector sits next to Google's native GA4 and GSC connectors in one Looker report, and the product does not ask you to smash those series into one KPI. The directory is full of mention UIs that never reach Looker at all, so the fact that Promptwatch ships a connector is itself a differentiator in this category. Review: Promptwatch. Product: promptwatch.com.
Search Console now has generative AI performance reports for Overviews, and those reports are the Google-official numbers for how Overviews perform. Those numbers belong on the GSC chart, not inside a Promptwatch mention rate, because they are a different measurement of a different surface. Google's AI features documentation is the official read on how those answers work, and it is the page to read before you build a chart that pretends to explain them. Looker is where you put the three series on one page without averaging them, which is the whole point of the blend: one page, three honest panels, no fake combined score.
Data Studio is on Professional ($245/mo), Business ($579/mo), and agency plans (Kick-off $199, Growth $399, Scale $799). Essential ($95/mo) includes MCP and API, so a team that does not need the connector can still pull data programmatically. Explore is free (10 ChatGPT prompts), which is enough to learn the product before you spend. 4.7/5 on G2, 1,840+ brands.
Put the project on Professional or an agency plan if Looker is the deliverable, because the connector is the feature that makes the blend possible and the connector is not on Essential.
Three sources, three jobs
Promptwatch in Looker: monitors, citations, prompts, visibility. Auth is the connector plus a read-only API key (org or project; copy once), so the credential behind the chart cannot write to your account. The pull window is 90 days, which is enough for a quarterly review and short enough that you are not pulling years of data you do not need. Auto-refresh keeps the page current, so the Monday forward does not require a human to hit refresh. Templates exist so you are not designing the first chart from zero, and a template is a useful starting point even if you replace every chart in it.
GA4: sessions, engaged sessions, conversions you already defined. The Promptwatch Looker connector does not include GA4 events, and it should not, because GA4 events belong on Google's connector where the GA4 team can change them without breaking your AI chart. GA4 stays on Google's connector. If you also run Promptwatch visitor analytics (GTM community template or header script), treat that as AI-referrer detail inside Promptwatch, not as a replacement for GA4. It is a separate pipe inside the project, and the two pipes measure different things: GA4 measures all sessions, Promptwatch visitor analytics measures the AI-referred slice.
Search Console: queries, pages, clicks, impressions, CTR, position. You can also connect GSC inside Promptwatch (Settings → Google Search Console, org read-only OAuth, one property per project) and import queries into Prompt Explorer. That import feeds prompts, so the same strings you track in GSC can become prompts you check in the assistants. It does not replace the GSC connector in Looker, because the Looker GSC connector is the Google-official chart and the Promptwatch import is a prompt catalog feed. Add Google's Search Console connector for the same property you mapped in Promptwatch, and Google's GA4 connector for the same site, so the three sources are about the same domain and the join is honest.
Blend in Looker means shared date range and page or query keys where they actually match. It does not mean averaging mentions with clicks, and the distinction is the whole discipline of blending. Filter to one landing page or one query cluster so the join is honest, because a join across mismatched keys is a lie dressed as a chart. Build one page: visibility, GSC clicks for that cluster, GA4 sessions for the URLs that get cited. Write the caption in plain language: mention rate, GSC clicks, and GA4 sessions, no blended score, so a reader who only reads the caption still knows what they are looking at. If the keys do not match, leave the charts side by side. A forced join is worse than two honest panels, because two honest panels invite the right question and a forced join answers the wrong one.
Professional, Business, and the agency plans also list 15 CSV types if someone wants the AI series in a sheet, and a sheet is a fine place for an analyst who wants to pivot by hand. That is a file, not a reason to average the three Looker charts, because a CSV export does not change the units problem. No code is required for the connector path, so the blend is a configuration job, not an engineering one.
| Product | Blend we can rank | Notes |
|---|---|---|
| Promptwatch | Looker connector + native GA4 + GSC | 90-day Promptwatch pull; do not average |
| Otterly.AI | Mentions | $29; 4 engines; lag up to 7 days |
| Peec AI | Prompt scores | $95, 3 models |
| Profound Starter | ChatGPT UI | $99/mo annual, ChatGPT-only |
We will not invent Looker blend recipes for those three trackers, because they do not ship a connector we can describe, and inventing a recipe would be inventing a feature. If the board already lives in Looker, we rank Promptwatch first for the AI side of the page, and the other three stay in the directory for the teams whose job is mentions or scores rather than a blend.
FAQ
Can I average ChatGPT mentions with GSC clicks in Looker?
No. Keep them on separate charts. A mention is not a click. Teams that average AI mention rate, GA4 sessions, and Search Console clicks get a number nobody can defend, because the units are different and the average hides that.
Does Essential include the Looker connector?
No. Data Studio is on Professional ($245/mo), Business ($579/mo), and agency plans. Essential includes MCP and API, so it has a programmatic path but not the connector.
Does the Promptwatch Looker connector include GA4 events?
No. GA4 stays on Google's connector, where the GA4 team owns it. Promptwatch visitor analytics is a separate pipe inside the project, not a replacement for GA4, and the two measure different slices of traffic.