Integration

TriRank in Looker Studio

A community connector you deploy into your own Apps Script project.

It reads what TriRank has already stored for a list of domains and hands it to Looker Studio as a data source. No probe runs because you opened a report.

What it gives you

One row per domain: the AI-engine citation score, Domain Rating, and the SEO and GEO audit scores, each beside a state field saying whether there is a reading at all.

The full field list, and the notes on the ones that are easy to misread, are in the connector's README.

A missing reading is null, never zero

Nobody probed the domain, or not every engine reported, or there is no stored Domain Rating: in all three cases the metric arrives empty.

Looker excludes a null from averages and leaves a gap in a time series. A zero would be included, and would pull a portfolio average down as though the domain had been measured and scored nothing. Put the matching state field somewhere you can see it.

Setting it up

  1. Create an Apps Script project and paste in the connector's Code.gs and appsscript.json.
  2. Deploy it and copy the deployment ID.
  3. Open Looker Studio with that ID, authorise the script, paste your TriRank API key and list the domains you want.

The exact URLs, the manifest steps and the Apps Script execution ceiling are in integrations/looker-studio/README.md, which ships with the connector.

What a refresh costs

One API request per domain, per refresh. Your daily allowance is 60 for an anonymous caller, 200 on a free account and 1000 on a paid one.

Nothing here spends our vendor money: the endpoint reads what is already stored and never triggers a probe, an audit or a Domain Rating fetch. Refreshing often is rude to your quota, not to the budget.

Read the API documentation

Where this stands

The Apps Script deployment is yours to make. There is no hosted version to point you at, and nothing in this repository can do it for you (read 2026-09-07).

It is not published in Looker Studio's gallery. A listing needs Google's review against their connector policies; everything above works from a private deployment without one (read 2026-09-07).