How to Load AI Search Data in Looker Studio with Promptwatch
Add the Promptwatch Looker Studio connector, authenticate with an API key, and start from the monitor and citation templates.
A CMO will not live in a GEO app. They will live in the Looker Studio report someone already shares on Monday. Loading AI search data there is how mention share and citations show up next to the charts finance already trusts. You do not need an engineer to keep that report fresh. The Promptwatch connector is no-code. Auto-refresh follows whatever refresh you set in Data Studio. An engineer is optional later if you want the REST API or MCP instead. The CMO's habit is the part that decides where the data has to live, and the data has to live where the CMO already looks. A report that lives in a tool the CMO never opens is a report the CMO never reads, and a report the CMO never reads is a report that does not change any decision.
Site: promptwatch.com. Data Studio is listed on Professional ($245/mo), Business ($579/mo), and the agency plans: Kick-off $199, Growth $399, Scale $799. Essential is $95/mo with a 7-day trial and still includes MCP and the API if you would rather skip Looker. Explore is free (ChatGPT, 10 prompts). Promptwatch is 4.7/5 on G2 across 1,840+ brands.
Confirm you are on Professional, Business, or an agency plan if you want the Looker connector. Data Studio is not listed on Essential. Essential can still pull the same kinds of data through MCP and API. The tier check is the part that decides whether the connector is in scope, and a promise of a Looker deck on Essential is a promise of a feature the tier does not list. A team that promises the deck on Essential will deliver the deck on Essential, and the deck will not connect, and the disconnect is the part that erodes trust in the rest of the report.
Authenticate, then open a template
In Looker Studio, add the Promptwatch connector and authenticate with an API key. Create that key in Promptwatch first. Use a read-only key, project-level if the report is for one brand. Org-level keys see every project. Project-level keys see one project. One-click copy is there so you are not retyping a secret. The key scope is the part that decides what the report can see, and the read-only flag is the part that decides what the report can do. A read-only key is the safe default for a shared deck, because a shared deck is a view, and a view should not be able to publish.
Looker only needs to pull series. A write-capable key in a shared report is how someone later wires MCP with the same secret and publishes a draft they did not mean to send. If an agency board needs every client, use an org key and filter in Looker, or make one report per project. Mixing clients in one unfiltered org pull is how a screenshot leaks. A leaked screenshot is the part that turns a convenience into a breach, and the per-project report is the part that prevents it. The cost of a leaked screenshot is not the screenshot, it is the client call that follows it, and the per-project report is the cheap control that avoids the call.
Templates exist for monitors, citations, prompts, and visibility. Open one of those before you design a custom canvas. The first job is confirming the connector returns the project you think it does. A blank custom report wastes a morning on layout while the key is still pointed at a sandbox. The template is the part that confirms the connection before the layout work, and the sandbox is the part that wastes the morning. A template loads in a minute and proves the key works, and a custom canvas takes an hour and proves nothing until the data arrives.
Auto-refresh is not a Promptwatch-specific schedule. It follows Data Studio settings. If the board is stale, check Looker's refresh. Each data pull is a 90-day window. If you need a longer history, chunk the range. Do not expect a single pull to dump two years of prompt checks. The 90-day window is the part that limits a single pull, and the chunk is the part that builds a longer history. A two-year trend is a series of 90-day chunks, not one pull, and a report that pretends otherwise breaks the day someone changes the date range.
On Professional and above you also get CSV exports across 15 data types. That is the escape hatch when someone wants a sheet instead of a live report. A sheet is a different deliverable from a live report, and the CSV is the path to it. A stakeholder who wants a sheet is a stakeholder who wants to do their own pivots, and the CSV is the deliverable that lets them.
Shared charts, not a write desk
Looker is for shared charts. It is not the place to manage prompts, generate articles, or publish to Webflow. Those write actions stay in the app, in MCP with a write key, or in Content Agent. The split between read and write is the part that keeps the report safe, and the write desk is the part that lives in the app. A report that can write is a report that can miswrite, and the read-only split is the part that removes the risk.
You can blend Promptwatch with GA4 and Search Console in the same Looker report. Do that as side-by-side charts. Do not average mention share with GSC clicks and call it a GEO score. Those measures do not share a denominator. Google's generative AI performance reports belong on the GSC connector if you want Overview impressions in the same file. A blended score is a number nobody can defend, and a side-by-side chart is a number each reader can explain. The defense is the part that matters in a QBR, because a number no one can defend is a number that gets cut, and a number that gets cut is a number that took the whole report with it.
Semrush AI Toolkit at $99/domain already reports inside Semrush. Stay there if the only audience is people who live in Semrush. Otterly.AI from $29/mo will not give you this connector. REST API and MCP exist if you skip Looker entirely and build in a notebook. Method: how we rank. Tools list.
FAQ
Is Looker on Essential?
No. Data Studio is listed on Professional ($245/mo), Business ($579/mo), and the agency plans. Essential still includes MCP and the API.
How far back does one Promptwatch pull go?
Each data pull is a 90-day window. Chunk longer history. Do not expect a single pull to dump two years.
Can Looker publish Webflow drafts?
No. Looker is for shared charts. Write actions stay in the app, in MCP with a write key, or in Content Agent.