Skip to content

Adventive — Looker Studio Connector SOP

Owner: Adventive Platform Engineering Scope: The Adventive Community Connector for Google Looker Studio (formerly Google Data Studio), deployed and maintained via Google Apps Script. Status: Living document. Propose changes via pull request against the BitBucket repository.

Purpose

This Standard Operating Procedure (SOP) defines how Adventive maintains, deploys, and operates the Looker Studio connector. It exists so that any engineer — current or future, internal or contracted — can:

  1. Understand what the connector does, how it is structured, and where the known failure points are.
  2. Deploy an update to the connector from scratch in under 30 minutes using the clasp CLI.
  3. Diagnose and resolve the most common operational failures without escalation.
  4. Assess future code changes against the issues already identified and the standards they should meet.

Contents

Section What it covers
01 — Architecture Assessment Module inventory, data flow, API schema, and a complete issues register from the 2026 audit.
02 — Code Updates Every change required to bring the connector to current Looker Studio standards — with before/after code and rationale for each fix.
03 — Deployment & Management How to deploy using clasp, how to publish to the Looker Studio marketplace, versioning, rollback, and credential management.
04 — Runbook Operational runbook: ownership, failure modes, observability, and break-glass procedures.
05 — V8 Runtime Migration Triage against Google's V8 migration CSV, incompatibility review against this codebase, migration procedure, best practices, and rollback caveats.
connector-rewrite/ Drop-in replacement source files (browse on GitHub) implementing every change from §02 and the V8 runtime flip from §05. Copy to the repository and deploy.

Quick reference

  • Runtime: Google Apps Script, V8 engine
  • Deploy tool: clasp push from the repository root
  • Auth type: USER_PASS — Integration Key maps to username, API Key maps to password
  • API base: https://api.adventive.com/v2.0/
  • Cache TTL: 30 minutes (CacheService.getUserCache)
  • Logging: Cloud Logging (exceptionLogging: "CLOUD" in appscript.json)
  • Environments: One Apps Script project per environment is the recommended pattern (see §03)
  • Never deploy directly from the Apps Script IDE to the production deployment without staging verification first.

How to use this package

Applying the rewrite:

# From the repository root:
cp connector-rewrite/appscript.json ./appscript.json
cp connector-rewrite/Code.gs ./Code.gs
cp connector-rewrite/Auth.gs ./Auth.gs
cp connector-rewrite/DataCache.gs ./DataCache.gs
clasp push

Then follow §03 — Deployment & Management to publish the new version.

Auditing future changes: Read sections 01–02 to understand the existing issue register. Any new change should be checked against the same categories: runtime correctness, security (credential handling), Looker Studio API compliance, and Apps Script best practices.

Changing this SOP: These documents are the source of truth. If reality diverges from what is written here, update the document. All changes go through pull request review.

Last reviewed: 2026-04-22