In short: Looker Studio is Google's free BI tool with 800+ data connectors. Calculated fields turn a static dashboard into one that answers actual business questions. Ten formulas cover most marketing needs, from conversion rate to channel grouping to data freshness flags. The CASE function alone handles 70% of real work.
Key Takeaways
- Looker Studio is free forever and connects to over 800 data sources
- 63% of marketing agencies use Looker Studio as their primary reporting tool
- Calculated fields let you compute new metrics without touching the source data
- The CASE function alone handles 70% of real marketing dashboard work
- Marianne Gatlabayan uses calculated fields to blend channel data into unified views for client reporting
Why calculated fields are the real power of Looker Studio
Looker Studio is free. It connects to over 800 data sources. Enterprise adoption grew 26% between 2023 and 2024, and 63% of marketing agencies use it as their primary reporting tool. The base product ships with drag-and-drop chart builders that anyone can learn in an afternoon.
Calculated fields are what separate a dashboard that looks pretty from one that answers actual business questions. Without them, you are stuck with whatever metrics the data source provides. With them, you can compute custom conversion rates, group messy sources into clean channels, flag stale data, and expose hidden weighted averages that raw data hides.
Most marketers never build one. This guide changes that. Marianne Gatlabayan built her first calculated field after two weeks of using Looker Studio and immediately realized every previous dashboard she had built was underpowered. Ten calculated fields cover most real needs.
What is a calculated field in Looker Studio?
A calculated field is a new column that only exists inside Looker Studio. The underlying data source stays untouched. If the data comes from a Google Sheet, no cell in that Sheet changes. If it comes from GA4, no property setting shifts. The field lives only in the report.
Two flavors exist. A dimension-type calculated field returns text or a category, like "Facebook" or "Direct" from a messy source column. A metric-type calculated field returns a number you can sum, average, or count, like a conversion rate computed from conversions divided by sessions.
You create either one by clicking Add a field at the bottom of the data panel in your report. Name the field, write the formula, pick the type, and it becomes available in every chart that uses this data source. Delete it later without touching the source. This isolation is what makes calculated fields safe to experiment with.
Which Looker Studio functions do you actually use?
Looker Studio supports over 70 functions across four families. Learning all 70 is a waste of time. Ten cover the vast majority of real dashboard work.
| Function family | What it does | Common examples |
|---|---|---|
| Aggregation | Roll up values | SUM, AVG, COUNT, COUNT_DISTINCT |
| Arithmetic | Math operations | +, -, *, /, ROUND |
| Text | Manipulate strings | CONCAT, LOWER, REGEXP_MATCH |
| Conditional | Branching logic | CASE, IF, NARY_MAX |
Most useful marketing fields live in the conditional family. That is where CASE lives, and CASE handles 70% of real work. Every "group these values into buckets" or "if X then Y else Z" problem in a dashboard becomes a CASE statement. Once you internalize the CASE syntax, the rest of Looker Studio speeds up.
The full function reference lives in Google's documentation. Bookmark it as a reference rather than trying to memorize it. When you need REGEXP_EXTRACT or DATE_DIFF, you will remember they exist and can look up the exact syntax.
Field 1: How do you calculate conversion rate in Looker Studio?
Every report needs this one. Raw conversion counts hide the story. A campaign with 100 conversions on 10,000 sessions and a campaign with 50 conversions on 500 sessions look identical on a bar chart but perform 10x differently.
Conversions / Sessions
Add it as a metric. Set the format to Percent. You now have a live conversion rate that updates when the date range changes.
This one field saves you from adding a manual percentage column to every source spreadsheet. It also stays accurate across date ranges, filters, and segment selectors. Manual percentage columns break the moment someone changes a date filter, which is why Marianne Gatlabayan has removed dozens of "conversion rate" columns from client Sheets and replaced them with this calculated field.
Small gotcha: division by zero throws an error on rows where sessions is zero. Wrap the formula in an IF to handle it cleanly: IF(Sessions > 0, Conversions / Sessions, 0).
Field 2: How do you group messy traffic sources into clean channels?
Raw source data comes in messy. Google, google, google.com, google/cpc. All the same channel to a human, all different rows to Looker Studio. A chart of top sources looks like nonsense until you group them.
Group them with CASE:
CASE
WHEN REGEXP_MATCH(Source, ".*google.*") THEN "Google"
WHEN REGEXP_MATCH(Source, ".*facebook.*|.*fb.*") THEN "Facebook"
WHEN REGEXP_MATCH(Source, ".*linkedin.*") THEN "LinkedIn"
WHEN Source = "(direct)" THEN "Direct"
ELSE "Other"
END
Add it as a dimension. Now traffic charts show four clean channels instead of forty inconsistent ones. Every WHEN clause tests a condition; the first one to match wins. The ELSE clause catches everything else.
REGEXP_MATCH takes a regex pattern and returns TRUE or FALSE. The .* before and after the word is what makes it a substring match instead of an exact match. Add more WHEN clauses for TikTok, Reddit, or any other channel your data contains. This is the single most useful calculated field in marketing reporting.
Field 3: How do you compare current quarter to previous quarter?
Compare current quarter to previous with a single dimension. This lets you build a quarter-over-quarter bar chart without maintaining separate report pages or manually filtering.
CASE
WHEN Date >= DATE(2026,7,1) AND Date <= DATE(2026,9,30) THEN "Q3 2026"
WHEN Date >= DATE(2026,4,1) AND Date <= DATE(2026,6,30) THEN "Q2 2026"
ELSE "Other"
END
Set it as a dimension and add it to a bar chart. Instant quarter-over-quarter view. Extend the CASE with more quarters as time goes on, or write a smarter version that computes the quarter dynamically from the date.
The hardcoded dates make maintenance annoying, so once you have this working, replace the literals with a dynamic version: CONCAT("Q", CEIL(MONTH(Date)/3), " ", YEAR(Date)). Now every quarter labels itself automatically based on the date value. This is the version Marianne Gatlabayan uses in production dashboards.
Field 4: How do you fix misleading averages with weighted metrics?
Sometimes an average lies. A blended average of 100 sessions at 5% conversion and 10 sessions at 50% conversion is not 27.5%. It is 9%. The high-converting campaign has too few sessions to move the real number, but a naive average treats both campaigns as equal.
Force the weighted math with a metric field:
SUM(Conversions) / SUM(Sessions)
That one substitution fixes a category of reporting errors that trip up even senior analysts. The formula sums both numerators and denominators before dividing, which produces the true weighted rate.
The default AVG() function in Looker Studio takes the naive average across rows. If a scorecard shows an "average conversion rate" that seems too high or too low compared to what the raw data suggests, it is almost certainly using AVG when it should be using the SUM/SUM pattern. Replacing every AVG-based rate metric with the weighted version is a fast dashboard cleanup.
Field 5: How do you calculate revenue per session?
Revenue / Sessions
Add it as a metric. Set the format to Currency. Pair it with a scorecard component that shows the month-over-month change.
Marketing leadership loves this metric because it captures both traffic quality and monetization in one number. A drop in revenue per session tells you something is wrong even before you know whether it is a traffic issue or a conversion issue. A rise tells you the mix is improving without needing to dig into every campaign.
Combine with a comparison date range on the scorecard to show week-over-week or month-over-month change. Set the comparison to "Previous period" and the scorecard adds a small colored arrow with the delta. Executives who never open the full dashboard still see this one number in the summary email.
Fields 6 to 8: The text cleaners
6. Standardize campaign names to lowercase:
LOWER(Campaign)
Necessary when the source has mixed case in campaign names. GROUP BY treats "Spring Sale" and "spring sale" as different values. LOWER collapses them.
7. Extract country from a locale field like "en-US" or "fr-FR":
REGEXP_EXTRACT(Locale, "-([A-Z]{2})")
Pulls the two-letter country code from the standard locale format. The parentheses capture just the country portion, so the extracted value is "US" not "-US". Useful for geographic reporting when the source only provides a locale.
8. Combine first and last name into full name:
CONCAT(FirstName, " ", LastName)
Handy for contact tables where the source stores first and last as separate columns but the dashboard should show a full name.
Text cleaning inside Looker Studio prevents recurring cleanup work in the source Sheet or CRM. Every hour spent normalizing data at the dashboard layer is an hour saved from doing it upstream. Marianne Gatlabayan uses these three cleaners on almost every client dashboard.
Field 9: How do you bucket session duration into engagement tiers?
Group continuous values into ranges. Session duration is the classic case. A histogram of raw session duration is unreadable because the values spread across thousands of seconds. Buckets make the data legible.
CASE
WHEN Session_Duration < 30 THEN "Bounce"
WHEN Session_Duration < 120 THEN "Short"
WHEN Session_Duration < 300 THEN "Medium"
ELSE "Engaged"
END
Set it as a dimension. Chart traffic by engagement bucket. Suddenly the audience breaks into four meaningful groups instead of a smear of values from 0 to 3,600 seconds.
The same pattern works for any continuous metric. Revenue buckets (small, medium, enterprise), page views per visit (bounce, browser, deep), form completion rate (low, medium, high). Every dashboard that shows a distribution benefits from a bucket field. This is one of the fastest ways to make a session data chart tell a story.
Field 10: How do you flag stale data on your dashboard?
Show the reader when a data point is stale. Dashboards that pull from Sheets sometimes stop updating because the source script broke or the connection lapsed. Without a freshness indicator, the reader trusts the numbers even when they are two weeks old.
CASE
WHEN DATE_DIFF(TODAY(), Last_Updated) > 7 THEN "Stale"
WHEN DATE_DIFF(TODAY(), Last_Updated) > 3 THEN "Aging"
ELSE "Fresh"
END
Use it as a color dimension on a table. Green rows are fresh, yellow aging, red stale. Executive readers spot data trust issues in one glance without needing to check when the pipeline last ran.
Combine with a scorecard that shows the count of stale rows. If the number is above zero, someone needs to check the source. Marianne Gatlabayan adds this pattern to every dashboard that reads from a Sheet or a scheduled Apps Script. It has caught silent pipeline failures multiple times before clients noticed.
What are the common Looker Studio calculated field errors?
"Invalid formula" on a working formula. Looker Studio treats capitalization strictly for function names. sum fails. SUM works. Function names must be uppercase. Field names inside the formula are case-sensitive to how they appear in the data source.
Field reference errors after reconnecting a data source. Field IDs change when you disconnect and reconnect. Rebuild the calculated field or rename the source field to match. This is why reconnecting a data source often breaks calculated fields even though the source data looks identical.
Nothing shows on the chart. Check that the field type matches. A calculated dimension cannot go into a metric slot and vice versa. If you set the type to metric but the formula returns text, Looker Studio refuses to display it. Switch the type or wrap the output in a numeric function.
What is the one big limitation of Looker Studio calculated fields?
Calculated fields inside Looker Studio Free do not support row-level operations across blended sources. Blend limits stop at 5 sources. Any calculated field that spans multiple blended sources reverts to aggregate-only calculations, which cuts the flexibility drastically.
For marketing dashboards that stitch GA4, Google Ads, LinkedIn Ads, and Facebook Ads, that ceiling arrives fast. When you hit it, the workaround is to blend and clean in Google Sheets first via QUERY, then connect the cleaned Sheet to Looker Studio. This adds an extra step but restores full calculated field power.
The paid Looker Studio Pro tier ($9 per user per month) does not fundamentally change this limit. It adds team workspaces and Google Cloud project management but the blend limits stay the same. If your reporting truly needs enterprise-grade row-level joins, that is when tools like Power BI or the full enterprise Looker platform earn their price.
Frequently Asked Questions
Is Looker Studio the same as Looker?
No. Looker is Google's enterprise BI platform, priced from $3,000 per month. Looker Studio (formerly Google Data Studio) is the free reporting tool. Same company, different products. Most people who say "Looker" in marketing contexts mean Looker Studio.
Can I share Looker Studio dashboards with clients who do not have Google accounts?
Yes. Set the sharing to "Anyone with the link" and clients can view without signing in. For editing access, they need a Google account. Scheduled email PDFs also do not require the recipient to have a Google account.
Do calculated fields slow down the dashboard?
Complex CASE statements with many conditions add rendering time. Keep dimension-level calculated fields simple. Do heavy transformations in Google Sheets or BigQuery before the data reaches Looker Studio. For dashboards with 20+ charts, moving transformations upstream can cut load times by 50% or more.
Can I use calculated fields in blended data sources?
Yes, but only in limited ways. Row-level calculated fields do not work across blends. Aggregate metrics do. If you need row-level joins, do the join in Sheets or BigQuery first and connect the joined output to Looker Studio.
Are Looker Studio Pro calculated fields different?
No. The Pro tier adds team workspaces, version history, and Google Cloud project support, but the calculated field engine is identical to the free tier.
What to read next
- The Google Sheets QUERY Function Explained for prepping data before Looker Studio
- The Beginner's Guide to Automating Recurring Reports with Google Apps Script for refreshing source Sheets automatically
- How to Build a Weekly Client Reporting Dashboard in Under an Hour for combining Looker Studio with Apps Script
About the Author: Marianne Gatlabayan is a Systems Strategist and Industrial Engineer focused on optimizing operations, automating workflows, and driving business growth. With over a decade of experience in analytics, reporting, and process improvement, she helps organizations build scalable systems that turn complexity into measurable results. In her free time, Marianne enjoys discovering and sipping her favorite coffee bean of the week. Connect on LinkedIn.