Google Data Studio · FinOps Profile

Google Data Studio Finops

FOCUS-aligned FinOps for Looker Studio / Looker: Looker Studio Pro is a per-user subscription billed via Google Cloud; Looker editions (Standard / Enterprise / Embed) are annual instance-based commitments with included user allocations and API call buckets; Conversational Analytics adds a token meter starting October 2026. Indirect cost flows through the underlying data source (often BigQuery), which dominates total dashboarding spend.

Google Data Studio Finops is the FinOps profile for Google Data Studio on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 8 billable meters, billed in USD, on a monthly cycle, and pricing category subscription + usage (tokens).

The profile maps 7 FOCUS columns for cost-allocation reporting.

Tagged areas include Business Intelligence, Reporting, Dashboards, Google Cloud, and FinOps.

Category: Business Intelligence / Analytics Pricing: Subscription + Usage (tokens) Billing: Monthly FOCUS v1.3
Business IntelligenceReportingDashboardsGoogle CloudFinOpsFOCUS

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

Charge Categories

UsagePurchaseTaxAdjustment

FOCUS Columns

BillingCurrency
USD
ChargeCategory
Usage
InvoiceIssuerName
Google LLC
ProviderName
Google Cloud
PublisherName
Google LLC
ServiceCategory
Business Intelligence
ServiceName
Looker Studio / Looker

Meters

looker_studio_pro_seats
Unit: seat-month
Active Looker Studio Pro per-user licenses
looker_instance
Unit: instance-month
Looker production instance under annual commitment (Standard / Enterprise / Embed)
looker_user_licenses
Unit: seat-month
Looker per-user licenses by class (Developer / Standard / Viewer)
query_api_calls
Unit: request
Looker Query API calls
admin_api_calls
Unit: request
Looker Admin API calls
data_tokens_input
Unit: token
Conversational Analytics input tokens
data_tokens_output
Unit: token
Conversational Analytics output tokens
underlying_data_source_cost
Unit: USD
Cost incurred at the connected data source (e.g., BigQuery bytes-scanned) when dashboards run queries

Sources