Looker Studio
Pull live Trakkr visibility, citation, competitor, perception, crawler, and visitor data into Google Looker Studio through the community connector.
The Looker Studio connector puts Trakkr data into the same reports as your GA4, Search Console, and ad-platform numbers. It is a Google community connector: you authenticate with a Trakkr API key, pick a brand and one dataset per data source, and build charts the way you would with any other Looker connection.
Set it up once, in about ten minutes, from /exports/looker-studio. It needs the Scale plan, and it carries a Beta badge in the product.
Before you start
You need a Scale subscription, at least one brand with data, a Google account with access to Looker Studio, and a Trakkr API key. Each person builds with their own key, and the brands they see are the brands their Trakkr permissions already allow.
Setup
1. Generate an API key
On the Looker Studio page, click Generate API key. Copy it straight away, because the full value is shown only once. You can also manage keys at /exports/api-keys.
2. Open the connector
Click Open in Looker Studio. If you need to paste the connector into Looker yourself, the same page has a Deployment ID button that copies the ID to your clipboard.
3. Authenticate
Paste your Trakkr API key when prompted. Keys start with sk_live_. The connector validates it against the live Trakkr API before storing it, so a wrong or revoked key fails immediately rather than producing empty charts later.
4. Pick a brand, then a dataset
The configuration is stepped. Choose a brand first, then one dataset. One data source holds one dataset, so a report that combines visibility and citations uses two data sources.
Time-scoped datasets turn on Looker Studio's own date range control. There is no separate days dropdown.
5. Build the report
Looker maps Trakkr's fields to dimensions and metrics automatically. Start with Visibility Over Time as a time series with date on the X axis: if that draws correctly, your key, brand, and date handling are all working.
The seventeen datasets
These are the labels exactly as they appear in the connector's dataset dropdown.
| Group | Datasets |
|---|---|
| Visibility | Visibility Over Time, Visibility by AI Model, Visibility by Prompt |
| Citations | Citations, Citation Analytics, Citations by AI Model |
| Competition | Competitive Rankings, Competitor Heatmap |
| Perception and prompts | Perception Metrics, Model Performance, Prompts |
| Crawlers | Crawler Visits Over Time, Crawler Visits by Bot, Crawler Top Pages |
| Visitors | Live Visitors Over Time, Live Visitors by AI Source, Live Visitors Top Landing Pages |
Two of those groups need something else connected first. The crawler datasets need crawler tracking set up, and the three visitor datasets read from a connected Google Analytics 4 property. In the product these two surfaces are Traffic > Crawlers and Traffic > Visitors; the connector still uses its original dataset names.
A few field notes worth knowing before you design a chart. Perception Metrics carries twenty dimension scores plus an overall, all as averageable metrics. Citations is the row-level list, paginated up to 5,000 rows, with URL, domain, source type, model, sentiment, appearance count, and first and last seen. Competitor Heatmap and Prompts are the two datasets that ignore the date range, because they describe current state rather than a series.
Date ranges and refresh
The connector fetches from Trakkr every time Looker Studio queries it, so a chart is as fresh as the last completed Trakkr check. It does not run a new AI check.
Looker Studio's date range maps to a day count between 7 and 365. Anything outside that is clamped. Crawler data is the exception: those endpoints support at most 90 days, so a six or twelve month Looker range still returns 90 days of crawler visits.
The brand list is cached for five minutes so that stepping through the config does not burn requests. The Trakkr API allows 60 requests a minute. A report with five data sources makes five calls on refresh, which is comfortably inside that, but many data sources refreshing on the same schedule can trip it. Stagger the schedules if you see rate limit errors.
If Trakkr adds fields to a dataset, open your data source in Looker Studio and click Refresh fields to pick them up.
Sharing and key rotation
Looker reports can be shared with anyone who has a Google account. Viewers do not need Trakkr access: the data is fetched with the report owner's API key, so treat a shared report the same way you would treat any export of that brand's data.
Regenerating your API key in Trakkr invalidates the old one immediately. Every Looker data source built on it stops returning data until you edit each one and enter the new key. Rotate deliberately, and rotate when someone with a key leaves.
Teammates should each connect with their own key rather than sharing one. Brand access follows their Trakkr permissions, not the key, so a teammate who cannot see a brand in Trakkr cannot pull it in Looker either.
Troubleshooting
Access denied. The key is invalid, expired, or was regenerated. Generate a new one and update the data source. If the message names the brand rather than the key, that brand is outside your permissions.
A plan or upgrade message. The connector passes Trakkr's own entitlement errors straight through. Looker Studio needs Scale, crawler datasets need crawler tracking, and visitor datasets need a connected GA4 property.
Fields look stale or missing. Click Refresh fields in the data source editor.
Rate limit errors. Too many data sources refreshed at once. Stagger their schedules or reduce the count.
Empty charts with no error. The connector returns what the API returns. Check the brand has active prompts and recent research data, and that your date range covers a period with runs in it.
Common questions
Which plan do I need?
Scale. The connector is gated to a Scale-equivalent subscription, and the Looker Studio card in the Integrations hub carries a Scale badge.
Can several teammates use the connector?
Yes, and each should generate their own API key. Brand access comes from their Trakkr permissions, so two people with different brand access will see different brand lists in the same connector.
How often does the data refresh?
Every time Looker Studio queries the connector, which is on chart load and on any scheduled refresh you configure in Looker. Trakkr caches the brand list for five minutes, but the data itself is fetched fresh.
Why does Google warn that the app is unverified?
Community connectors go through a separate Google review process, and Trakkr's is not through it. The warning describes OAuth review status, not the safety of your key or data. Click Advanced and continue.
Can I put two datasets on one chart?
Not in one data source. Create a data source per dataset and add them to the same report, then place their charts side by side or blend them in Looker Studio.
My crawler chart stops at 90 days. Why?
The crawler endpoint supports 1 to 90 days, and the connector clamps longer Looker ranges to 90 rather than failing. Visibility and citation datasets go back up to 365 days.