Looker Studio Connector

Pull your AI-visibility metrics into Looker Studio (Google Data Studio) with the read-only community connector.

Last updated August 31, 2026

The Looker Studio community connector pulls your AI-visibility metrics - share of model, per-engine citations, competitor benchmarks, and keyword rankings - straight into Looker Studio (formerly Google Data Studio) so you can build custom dashboards and blend AEO Goal data with your other BI sources.

It reads the versioned, read-only /api/v1/metrics API. The numbers are byte-for-byte the same aggregations the AEO Goal dashboard shows, so your Looker reports never drift from the app.

Requirements

  • A plan that includes data export (Growth, Scale, Enterprise, or any Brands tier). The connector is a paid capability - a Free key is rejected with a 402.
  • A personal API key scoped to read:metrics.

1. Create a scoped API key

  1. Go to Settings → API and click Create new key.
  2. Name it “Looker Studio”.
  3. Under Scopes, select read:metrics (BI / metrics). This is all the connector needs - the key can only read the metrics API and can never write anything.
  4. (Optional) Under Brand restriction, limit the key to specific brands so the report can only ever surface those.
  5. Click Create and copy the key immediately - it’s shown only once.

See API Keys & Scopes for the full scope reference.

2. Add the connector in Looker Studio

  1. In Looker Studio, click Create → Data source.
  2. Find the AEO Goal connector (via the deploy/share link your account team provides).
  3. When prompted for credentials, paste your aeo_… API key and click Submit.
  4. Configure the data source:
    • Metric - which dataset to load (see below).
    • Brand ID (optional) - a specific tracked-brand id. Leave blank to use your active brand (or the first brand the key is allowed to see).
  5. Click Connect, then Create report.

Available datasets

Metric What it returns
Share of Model Daily share-of-model %, weighted SoM, mentions, average position, and period-over-period delta.
Citations (per engine) One row per AI engine (ChatGPT, Perplexity, Gemini, …) with mentions, average position, and your vs. competitor share.
Competitors Your brand vs. each tracked competitor - share of model, mentions, citations, average position.
Rankings Latest SERP position per tracked keyword, by device and location. (Requires traditional-SEO rank tracking; empty otherwise.)

Add a separate data source for each metric you want to chart.

Date range

The connector honors the report’s date range control. With no dates it defaults to the last 30 days; the API caps any single pull at 366 days. Larger ranges are paged automatically.

Troubleshooting

Symptom Fix
“Invalid credentials” when connecting The key is revoked, expired, or missing the read:metrics scope. Create a fresh key with that scope.
402 / “not available on your current plan” Your plan doesn’t include data export. Upgrade to Growth or above.
Empty Rankings Rank tracking (traditional SEO) isn’t enabled for your account.
A brand is missing The key has a brand restriction that excludes it - create an unrestricted key or add the brand to the allow-list.

Frequently asked questions

What do I need to use the Looker Studio connector?

You need a plan that includes data export (Growth, Scale, Enterprise, or any Brands tier) and a personal API key scoped to read:metrics. A Free key is rejected with a 402.

Which datasets can I pull into Looker Studio?

The connector offers Share of Model, Citations per engine, Competitors, and Rankings. Add a separate data source for each metric you want to chart, and note that Rankings requires traditional-SEO rank tracking or it stays empty.

Will my Looker reports match the numbers in the app?

Yes. The connector reads the read-only /api/v1/metrics API, and the numbers are byte-for-byte the same aggregations the AEO Goal dashboard shows, so your reports never drift from the app.

What date range does the connector use?

It honors the report's date range control, defaults to the last 30 days with no dates set, and caps any single pull at 366 days. Larger ranges are paged automatically.