BI connectors and bulk exports
Move stable Sight datasets into Looker Studio, a warehouse, or another reporting workflow.
Bulk exports create organization-scoped CSV or newline-delimited JSON artifacts for project, scan, score, report, prompt, answer, source, domain, URL, action, alert, credit, and crawl-insight datasets. Project and time filters support bounded recurring extraction.
The Looker Studio connector source uses those exports, declares stable fields, stores its API key in user properties, and applies report date ranges and selected fields. Google Apps Script deployment and any marketplace review remain controlled by the deploying customer.
Validate recurring exports against a small known project before publishing a dashboard. Preserve identifiers, timestamps, denominators, filters, nullability, and row counts so external reporting can be reconciled with the Sight workspace.
Export datasets
Create organization-scoped CSV or newline-delimited JSON artifacts. Optional project and time filters keep recurring extracts bounded.
| Dataset group | Resources |
|---|---|
| Configuration and runs | Projects, scans, scores, reports, and prompts |
| GEO evidence | Answers, sources, domains, URLs, and actions |
| Operations | Alerts, credit ledger entries, and crawl requests |
const job = await sight.createExport(
{
resource: "crawl_insights",
format: "jsonl",
site_id: "site_123",
from: "2026-07-01T00:00:00Z",
to: "2026-08-01T00:00:00Z",
},
{ idempotencyKey: "crawl-july-site-123" },
);
const content = await sight.downloadExport(job.data.id);Looker Studio connector
The connector source declares stable schemas, stores the API key in user properties, validates the connection, requests JSONL exports, and applies the report's selected fields and date range.
Deployment remains customer-controlled
Copy the connector source into a Google Apps Script project, set the deployment API origin, authorize it, and complete Google's community connector deployment or review flow.