Looker

Data

Looker

Business intelligence and data analytics platform for creating and sharing interactive dashboards and reports. Roiva runs your saved Looks and stores their numeric output as metric observations for ROI measurement.

What gets synced

Roiva writes these metric observations on each sync. Reference the key in a value formula to use this data in your ROI calculations.

Looks

looker.looks.field_value Per-Look field value (one row per Look column, the Look and the column in the row's dimensions) count
Common use cases
  • Use existing Looker Looks as the source for initiative outcome metrics
  • Track dashboard KPIs that already represent the business outcomes your initiative targets
  • Pull time-series data from Looks to build before/after comparisons in Roiva
How to connect

You connect Looker from inside Roiva, so you need a Roiva workspace first. Sign in to connect it now. New to Roiva? Take the free assessment and create your workspace at the end, or request an invite.

  1. In Looker: Go to Admin → Users, click Add → Service Account, and name it Roiva. Leave Create default set of API credentials on, and give it a role with see_looks on the models your Looks use
  2. In Looker: Open the service account from the Service Accounts tab, click Manage under API Keys, and copy the client ID and secret
  3. Back in Roiva: Enter your Looker API host in the Instance URL field: the API Host URL on Admin → API if one is set, otherwise your instance URL (e.g. https://yourcompany.cloud.looker.com), keeping :19999 if your instance uses it
  4. Back in Roiva: Paste the API credentials in the format client_id:client_secret and save the connection
  5. Back in Roiva: The connection page checks each step, including every Look an initiative link names, and says what's missing. Once it's all ticked, click Test Connection
  6. Back in Roiva: Link this connection to an initiative on the Initiatives tab, then add a Filter with key look_ids and the IDs of the Looks to sync (comma-separated, e.g. 42,57)
Tips for capturing value
  • Look IDs are found in the URL when viewing a Look — e.g. /looks/42
  • Each numeric column in a Look result becomes a separate metric observation; ensure your Looks return the columns you actually need
  • Looks that return a date or month dimension alongside numeric measures produce time-series observations — ideal for before/after comparisons
  • The service account needs see_looks (which includes access_data) on the models your Looks use, and View access to the folders that hold them — no admin access required
  • Since Looker 26.8, admins can't manage a standard user's API keys, so use a service account rather than a person's login
Need help?

Email hello@roiva.ai with what you're seeing, and you'll hear back within one business day.

Looker
Looker

Start with the free AI ROI exposure assessment, then connect Looker once your workspace is set up.

Get your exposure report → Sign in to connect