How to Blend Promptwatch with GA4 and Search Console in Looker Studio

Mention share and clicks do not share a population. Average them and you invent a KPI nobody can debug. It will look stable while one of the real series is on fire. That is why this blend is useful only when each chart stays honest, and a mess when someone presents a single "AI SEO" number. The single number is the temptation, and resisting it is the whole skill of building this board.

One Looker Studio report can hold the three sources teams already argue about in Slack: AI visibility from Promptwatch, sessions from GA4, and clicks from Search Console. The connector setup is short. The judgment call is what not to merge. The setup is an afternoon. The judgment is the part that takes longer, because it is the part where you decide what each number means.

Site: promptwatch.com. Data Studio is listed on Professional ($245/mo), Business ($579/mo), and agency Kick-off $199 / Growth $399 / Scale $799. Essential is $95/mo (7-day trial) with MCP and API if you skip Looker. Explore is free (ChatGPT, 10 prompts). Promptwatch is 4.7/5 on G2, 1,840+ brands. The plan list is the gate. If the seat you hold is not on it, the connector will not authenticate, and the build stops at the first step.

Confirm Looker access on Professional, Business, or an agency plan before you promise this board to anyone. Promising a board on a plan that does not include it is how an analyst spends a day and a procurement lead spends a week apologizing.

Three connectors on one page

Add the Promptwatch connector and authenticate with a read-only project key. Org keys see all projects. Project keys see one. Copy the key once. The key scope decides how much of the account the report can read, and a project key is the safer default for a single-brand board.

Add GA4 and Search Console with Google's own connectors as separate data sources on the same report. Promptwatch can also connect GSC inside the app (Settings → Google Search Console, read-only OAuth, one property per project) if you want that data next to prompts. For this Looker board, the native GSC connector is the usual source for clicks and impressions. The two GSC paths give you the same numbers in different surfaces, and the native connector is the one that refreshes on Google's schedule rather than Promptwatch's pull.

Start from Promptwatch templates for monitors, citations, prompts, or visibility. Drop GA4 sessions and GSC clicks on the same page as separate scorecards. Place visibility, GSC clicks, and GA4 sessions as three charts, not one calculated field. Auto-refresh follows Data Studio settings. Each Promptwatch pull is a 90-day window, so chunk longer history instead of assuming a two-year join. The 90-day window is the constraint that shapes the whole layout, because any chart that pretends to span two years is really spanning two years of GSC and 90 days of Promptwatch.

You can put Promptwatch rows and GSC in one report and filter to the same hostname. Do not treat a joined average as a rank. Page-level GSC position and page-level citations are still different events. Joining them on hostname is fine for filtering. Joining them into one metric is the mistake this section exists to prevent.

No code is required. If you hate Looker, REST API and MCP still exist. CSV exports across 15 data types are on Professional and above if a stakeholder wants a sheet they can break. The sheet option is for stakeholders who need to sort and filter their own way, and it is the honest fallback when a live board is too much for the audience.

Keep the units separate

Promptwatch mention share is how often a brand appears in tracked AI answers. GSC clicks are Google web search. GA4 sessions are whatever you tagged, including AI-referred visits if you also run Promptwatch visitor analytics. Each unit is a count of a different event on a different surface, and that is why they do not average.

Those can move together. They often do not. A citation in ChatGPT can rise while GSC clicks fall. An AI Overview impression in GSC is still not a ChatGPT mention. Google's generative AI performance reports are the official impression series for Overviews and AI Mode. Keep that series on the GSC connector. Do not fold it into Promptwatch mention share. Folding them is how a board reports a single "AI SEO" number that nobody can attribute when it moves.

Better layout: Promptwatch for visibility, citations, and the prompt list. GSC for clicks, impressions, CTR, and average position for the same site. GA4 for sessions and the conversions you already defined. A note under the report that says these are different surfaces (AI mentions are not Google clicks) will save you a quarterly argument. The note is small and does more work than any calculated field, because it tells the reader how to read the page before they start averaging.

If you also run Promptwatch visitor analytics (header script or GTM template), put AI-referred visits in their own row. Do not add them to GA4 All Users and call it double confirmation. You may be counting the same visit twice. The same visit in two rows is a data error dressed up as a confidence boost.

An agency that already sends Looker links should blend here instead of pasting three CSV exports. A team that only needs Cursor asking about prompts can stay on MCP and skip the blend. The blend is for a reader who wants all three surfaces in one tab; MCP is for an analyst who wants to ask a question and get an answer.

Semrush AI Toolkit at $99/domain keeps SEO and AI columns in Semrush. Ahrefs Brand Radar from $199/mo plus an Ahrefs plan is mention research, not this three-source Looker file. Method: how we rank. Tools list.

FAQ

Can I average mention share with GSC clicks in one field?

No. They do not share a population. Place visibility, GSC clicks, and GA4 sessions as three charts.

Which Promptwatch plan includes Looker Studio?

Data Studio is listed on Professional ($245/mo), Business ($579/mo), and the agency plans. Essential has MCP and API if you skip Looker.

Should I add Promptwatch visitor analytics on top of GA4 All Users?

Put AI-referred visits in their own row. Adding them to GA4 All Users can count the same visit twice.