Looker Studio calculated fields
Calculated fields let you derive new fields with formulas — arithmetic, CASE logic, text and date functions — at the data-source or chart level. The decisive subtlety is aggregation: a formula's result depends on whether it is computed per-row then aggregated, or on already-aggregated values, which differs between field-level and chart-level calculations.
What this means
A calculated field is a formula that produces a new dimension or metric. Looker Studio offers arithmetic operators, CASE for conditional logic, and text, date, and aggregation functions. Fields can be defined at the data-source level (reusable) or on a single chart.
Aggregation decides the number
The same formula can give different answers depending on aggregation order. A metric like sum(revenue)/sum(sessions) aggregates first; a row-level revenue/sessions then summed averages ratios, which is usually wrong. Looker Studio distinguishes calculated fields that operate on aggregated inputs from those evaluated per row. When a calculated ratio looks off, the cause is almost always this aggregation context — fix the formula to aggregate the numerator and denominator before dividing.
- Operators, CASE, text/date/aggregation functions
- Data-source fields reusable; chart fields local
- Aggregate then divide, not divide then aggregate
How it appears in analytics and logs
A calculated field's value reflects where in the aggregation it runs. A ratio that looks wrong is often a row-level vs aggregate-level computation issue, not a formula typo.
Diagnostic use case
Create a derived dimension (group pages into sections) or metric (conversion rate, margin) inside Looker Studio without changing the underlying source.
What WebmasterID can help detect
WebmasterID's first-party fields can be reshaped with calculated fields in a report without third-party data or cross-site identity.
Common mistakes
- Averaging row-level ratios instead of aggregating first.
- Duplicating a chart-level field that should be source-level.
- Using a non-aggregated field where an aggregate is needed.
Privacy and accuracy notes
Calculated fields transform aggregated data; keep them off personal identifiers. They don't expand what the source collects.
Related pages
- Looker Studio connectors
A connector is the bridge between Looker Studio and a data source — Google connectors (GA4, BigQuery, Sheets, Ads) and community/partner connectors for everything else. The connector defines available fields, default aggregations, and data freshness/caching behavior, all of which shape what a report can show and how current it is.
- Custom and calculated metrics in reports
GA4 lets you define custom metrics (registered from numeric event parameters) and calculated metrics (formulas combining existing metrics, like revenue per user). They extend reporting beyond the built-ins, but calculated metrics inherit the scope and null-handling of their inputs, which is where formulas go wrong.
- Looker Studio data blending
Data blending in Looker Studio combines fields from up to several sources into one logical table by joining on configured keys. It supports join types (left outer, inner, full outer, cross). The common failure is join-key cardinality: a one-to-many key fan-out multiplies metric rows, so blended totals can silently overcount.
- Agency analytics
Derive client metrics inside reports.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.