Looker Studio
The Vercatus connector for Looker Studio gives a dashboard the citations recorded by the site audit’s engine checks and the prompts your workspace saved: for every week, site, answer engine and domain (the site, its named competitors, and optionally the domains cited most instead), the asks and how many of them cited the domain. Answer Share itself is in the app and the API.
Connect
Section titled “Connect”- In Vercatus, Settings, API & webhooks: Create key with the Export scope only, limited to the sites the dashboard should show. Copy the key.
- Open the Vercatus connector deployment supplied by your administrator in Looker Studio and authorize it with the key. If you do not have a deployed connector link, use the JSON endpoint below or ask your administrator for the connector setup.
- Pick a site (or all sites the key can see) and how many other cited domains to include, then Connect.
The report’s date range is the period read (a year at most). Data is cached for five minutes.
Fields
Section titled “Fields”| Field | |
|---|---|
| Week | Monday of the ISO week |
| Site, Engine, Domain | Dimensions. Role says whether a domain is the site (own), a named competitor or an other domain cited instead |
| Competitor domain | The domain on competitor and other rows, empty on the site’s own |
| Asks | Times a question was put to the engine and it answered |
| Cited asks | Asks whose answer cited the domain |
| Cited share | Cited asks ÷ asks, calculated from the totals of whatever the chart groups, so a monthly or all-engines view is right |
| Questions asked, Questions cited | Distinct questions a week; summed across weeks, a question counts once per week |
| Named, not cited | Answers that named the site without linking it |
| Competitor cited share | The same ratio for competitor and other rows |
Always show a share beside its asks: a share over a handful of asks moves a lot from week to week. A Google results page without an AI Overview is no answer and is not an ask.
Without Looker Studio
Section titled “Without Looker Studio”The connector reads GET /api/export/visibility.json?siteId=&from=&to=&others=; any BI tool or script can
read it with the same key. See the API reference.
BigQuery and other destinations
Section titled “BigQuery and other destinations”The supported JSON endpoint can feed a pipeline you maintain. A native BigQuery destination is not part of this workflow: your pipeline handles loading, schema, refresh and warehouse access. Use an Export-scoped key restricted to the required sites, and preserve raw asks and cited asks for correct aggregation. See integrations and exports.