How to Blend Promptwatch with GA4 and Search Console in Looker Studio
How we put Promptwatch, GA4, and Search Console in one Looker Studio report without averaging AI mentions with clicks.
One Looker file. Three sources. Promptwatch for assistant mentions and citations. Native GA4 for sessions and conversions. Native Search Console for clicks, impressions, CTR, and position. We blend the page so a client can see the week in one tab. We do not blend the metrics into one average.
If Promptwatch is not in Looker yet, start with how to load AI search data. This post assumes the connector already works. Load Promptwatch with a read-only key and a template first. Confirm the 90-day window. Then add native GA4 and native Search Console to the same report.
Three connectors, not one soup
Promptwatch: Looker connector plus a read-only API key. Templates for monitors, citations, prompts, visibility. 90-day pull. Data Studio is listed on Professional ($245/mo) and up. Kick-off at $199/mo is the agency plan we use (unlimited projects and prompts, 10 seats). Business is $579/mo. Essential at $95/mo has MCP and API but we do not treat it as the Looker plan. Explore is free, 10 ChatGPT prompts. G2: 4.7/5.
GA4: the Google connector they already have. We keep the same conversion events the account already trusts. If visitor analytics for AI referrers is in the SOW, that is a separate Promptwatch script or GTM tag. We still keep GA4. Setup notes: visitor analytics with GTM.
Should we drop GA4 because Promptwatch has visitor analytics? No. Keep GA4. Promptwatch visitor analytics is for AI referrers and the pages those visits hit. It does not replace the site's existing analytics program. Clients who already trust a conversion event in GA4 will not thank you for swapping the definition mid-retainer.
Search Console: native Looker connector, not the Promptwatch GSC pipe. Promptwatch can sync GSC performance into the project (up to a year) and import queries. That is for Prompt Explorer. The Looker GSC chart is still Google's connector, including generative AI performance reports when those are in the property. Two pipes, two jobs. See connect Search Console.
The rule we write on the slide
Do not average mentions with clicks. A mention is a model saying the name. A click is a person in Google. An AI-referred session in GA4 (or in Promptwatch visitor analytics) is a third thing. If you average them you get a number nobody can defend in a QBR. We have been asked for that number. We refuse it.
We place them side by side. Same date range when the ranges overlap. Promptwatch stops at 90 days in this connector. GSC and GA4 can go longer. We do not stretch the Promptwatch series to match a year of impressions. Align dates only where the windows overlap. Leave older GSC/GA4 on their own charts.
We also do not average ChatGPT mentions with AI Overview rows. Engine columns stay split. Label units on every scorecard. Mentions, clicks, and sessions never share a formula.
How the page is laid out
Top: date control. Then three scorecards that are labeled as different units: GSC clicks, GA4 sessions (or the conversion the client already uses), Promptwatch mentions and citations.
Middle: a prompt table from the Promptwatch template. A GSC query table. We do not join them on query string as if they were the same index. Some overlap. Plenty will not.
Can Looker join Promptwatch prompts to GSC queries automatically? You can build a join on the text if you want a matching exercise. We treat matches as a hint, not a rank. Many assistant prompts never appear as GSC queries. Many GSC queries never get asked to ChatGPT in the same wording. I would rather show two tables than a join that pretends they are the same list.
Bottom: one URL table if we have citations plus GA4 landing pages. Useful for "this URL got cited and this URL got sessions." Still not a blended rank.
Local businesses still need the local SEO playbook for map pack. This Looker page will not show pack positions.
Review the page on the same cadence as the rest of the retainer. No instant alerts.
FAQ
Should we drop GA4 because Promptwatch has visitor analytics?
No. Keep GA4. Promptwatch visitor analytics is for AI referrers and the pages those visits hit. It does not replace the site's existing analytics program.
Can Looker join Promptwatch prompts to GSC queries automatically?
You can build a join on the text if you want a matching exercise. We treat matches as a hint, not a rank. Many assistant prompts never appear as GSC queries.
Do we average mentions with clicks?
No. A mention is a model saying the name. A click is a person in Google. If you average them you get a number nobody can defend in a QBR. We refuse it.
If you want us to rebuild an existing Looker file, hello@1001seomedia.com. Send the GA4 property and the Promptwatch project name.