OrcLink
← Help Center

Data out

Looker Studio

A community connector that reads OrcLink report rows and daily ad spend with a read-only API key.

Built, not yet tested liveBuilt. Not yet run in a live Looker Studio account; deploying the connector to Google is an owner or customer action.

Live: shipped in OrcLink's production release before this one. Built, not yet tested live: built and tested with sample data, not yet run against a live account of the vendor. Coming soon: listed, not available to connect yet.

Without this connector: the Google Sheets export (Data out > Sheets) writes one report view to a Google Sheet once a day, and Looker Studio can read that sheet with its own Google Sheets connector (the export runs while the scheduled jobs export and jobs run; your OrcLink operator schedules them).

A Looker Studio community connector (Apps Script) that reads the OrcLink public API with a read-scoped API key. Files: Code.gs, appsscript.json. Nothing here is deployed; deploying is an owner action.

Deploy

  1. Go to https://script.google.com, New project, name it "OrcLink connector".
  2. Project Settings: check Show "appsscript.json" manifest file in editor. Paste appsscript.json over the manifest, and Code.gs over Code.gs. Save.
  3. If the API runs on another host (staging), change BASE_URL in Code.gs and the urlFetchWhitelist entry in the manifest to it.
  4. Deploy > New deployment > Add-on / Looker Studio connector (UNVERIFIED wording in the current Apps Script UI; older UI: "Deploy from manifest"). Copy the deployment id.
  5. Open https://lookerstudio.google.com/datasources/create?connectorId=<deployment id>, authorize, paste an API key made in Data out > API with the read scope only.
  6. Pick Data: attribution report rows (by channel, source, campaign, campaign group, ad group or keyword, with a model and a currency) or ad spend by day. The report's date range is used. Both are aggregates: the connector offers no person-level data.

To share it with other Google accounts in the organisation, share the Apps Script project with them (each user adds their own key). A public listing in the Looker Studio gallery needs Google's review: owner action.

Privacy

  • The key stays in the user's own Apps Script user properties and is sent only in the Authorization header.
  • Report rows and spend are aggregates. The connector reads no person-level data (no outcome rows, no journeys, no calls). In HIPAA mode report rows are by channel only unless the owner turned on "Include campaign names in data out".
  • Credited revenue and conversions are OrcLink attribution: a claim. The source system owns each outcome and its value.

Limits

  • At most 10,000 rows per request (pages of 200). With more, the chart shows an error ("More than 10,000 rows for this date range: use a shorter date range.") instead of a partial total.
  • API rate limits per key: 120 reads per minute, 30 report requests per minute; per workspace, for all its keys together: 600 reads and 60 report requests per minute. One report per key runs at a time. Looker Studio caches results; avoid many charts on one key.