Looker Studio Tutorial #8 — How to Use Conditional Formatting in Tables

Looker Studio Tutorial #8 — How to Use Conditional Formatting in Tables

I walk through practical ways to make Looker Studio tables speak louder. Conditional formatting helps you surface problems, celebrate wins, and guide attention toward what matters. Below, I show step-by-step how I set up rules, combine OR and AND logic, use color scales instead of heatmaps, and add a consistent footer across pages.

Step 1: Locate Conditional Formatting in your table

Open the table you already added to the report and switch to the Style panel. You will see an option called Conditional formatting. Click Add formatting to begin.

Looker Studio KPIs by Channel table with the Style panel open showing Conditional formatting and Add formatting

This opens two core choices: Single Color and Color Scale. Single Color is best for binary or threshold-driven signals. Color Scale works well for gradients and relative performance across rows.

Step 2: Create a Single Color rule to flag problem rows

I usually start by selecting a metric that represents value per user, like Average revenue per user. For a quick health check I set a threshold such as < 5. That highlights channels delivering low revenue per user so I can prioritize optimization.

Single color conditional rule configured with ARPU, 'LESS THAN' selected and an input threshold value.

When creating a Single Color rule you can:

  • Choose the field to evaluate (for example, Average revenue per user)
  • Pick a comparison operator (less than, equal to, greater than)
  • Select whether to color the entire row or just that metric column

I prefer coloring the metric column when I want compact, visual signals without overwhelming the table. If you want a stronger visual cue, color the entire row.

Looker Studio table 'KPIs by Channel' showing conditional formatting with green and red column highlights and the Properties panel

Step 3: Use OR and AND to combine conditions

Not all problems are one-dimensional. Often, I want to flag rows where revenue per user is low and traffic is meaningful. That avoids highlighting tiny channels with zero purchases.

Conditional formatting supports both OR and AND logic. Use OR when a row should qualify if any single condition is true. Use AND to require multiple conditions to be true at once. Think of it like formulas in Sheets or SQL logic.

Looker Studio conditional formatting showing ARPU less than 5 and Active users greater than 101 with the text style preview.

Example I use often:

  • Average revenue per user < 5 AND active users > 100

This ensures I only flag materially impactful channels with poor monetization rather than tiny outliers.

Step 4: Add a complementary positive rule

One rule showing problems is useful, but complementary rules make interpretation instant. After creating a red rule for low revenue per user, I add a green rule for values above a healthy threshold.

Looker Studio conditional formatting style showing a light green color swatch selected

Create a second Single Color rule with the same field and choose a different color. I use a light green background and white text for good performance. Keep colors consistent across the report so readers learn the visual language quickly.

Step 5: Use Color Scale for gradient insights

Color Scale converts a metric distribution into a gradient. This is excellent for metrics like conversions, CTR, or engagement where relative position matters more than a hard cutoff.

Looker Studio color scale presets palette open showing multiple gradient options and the gradient preview

When you choose Color Scale you can set the low, midpoint, and high colors. I often use:

  • Low: muted gray or light red
  • Mid: neutral green
  • High: dark green

You can treat the scale as a heatmap alternative and tune percentiles or absolute values. This gives more nuanced visual cues than a strict red/green split.

Step 6: Control intensity, thresholds, and rule order

Two small but powerful controls live inside conditional formatting:

  • Percentage/number settings — for Color Scale you can choose whether the bounds are percentiles or fixed numbers and set those values precisely.
  • Rule order — when multiple rules target the same column or row, the order determines which rule applies. Drag rules up or down to prioritize the most important condition.
Looker Studio KPI table with the Table properties panel open showing 'Conditional formatting' with '3 rules applied' and related settings.

Keep in mind: conditional formatting overrides a heatmap. If you have a heatmap applied to a column, conditional formatting will take precedence for that column. If you need alternating row colors or other style features, remove the heatmap first.

Looker Studio KPIs by Channel table with the Table properties panel open; the Chart title settings and Conditional formatting section are visible.

Step 7: Combine heatmap-style visuals with conditional formatting carefully

Heatmaps and conditional formatting both aim to visualize magnitude, but they interact. If you rely on heatmaps for an entire metric column, conditional rules may not display as expected. I generally pick one visual approach per metric—either a full heatmap or targeted conditional rules—so the table stays clear.

Looker Studio conditional formatting 'Create rules' dialog with 'Conversions' selected and a color scale gradient bar.

Step 8: Add a footer and make it report-level

A footer is a small design choice that improves usability. I add a footer to display contact info, links, or author credits and make it report-level. That way the same footer appears on every page automatically.

Right‑click menu in Looker Studio showing the 'Make report-level' option over a table

To create a footer:

  1. Draw a rectangle at the bottom of the page and style it (dark gray works well).
  2. Add text elements for contact info or a LinkedIn profile.
  3. Right-click the footer and set it to be report-level so it repeats on new pages.

I like a subtle border color for report-level elements so I can spot and edit them later without accidentally changing page-level content.

Practical checklist before you publish

  • Validate thresholds against real distributions — avoid highlighting tiny sample sizes.
  • Use consistent color rules across similar reports.
  • Keep rule order logical: critical alerts first, softer signals later.
  • Prefer column-only coloring for compactness; use full-row coloring for urgent issues.
  • Test how conditional formatting behaves alongside heatmaps and alternating row colors.

Conditional formatting is one of the fastest ways to make tables actionable. With well-chosen rules you can instantly scan a traffic table and know where to probe next.

Tools I Use

Windsor.ai — my go-to connector for GA4, Google Ads, Facebook Ads, and more.
Use promo code gaillereports for 10% off any plan.
Supermetrics — a robust connector for agencies or teams managing multiple data sources.

If you compare connectors for Facebook Ads or multi-channel setups, read this:
Top Facebook Ads Connectors for Looker Studio — How to Choose the Right One


More Articles You Might Like

How to Set Theme and Layout in Looker Studio and Connect Your GA4 Data
How to Make Your Looker Studio Dashboard Look Professional (Header Setup Guide)
Looker Studio Report Tutorial #5 — Add Scorecards with KPIs (Setup, Styling & Metrics Explained)
Build Professional Tables in Looker Studio — Setup, Styling & Best Practices
How to Visualize Data Over Time in Looker Studio Reports


Final Notes (closing paragraph)

Conditional formatting is one of the most powerful tools for turning raw data into insight. With a few simple rules, your tables can instantly highlight what’s working and what’s not. Combine color logic with thoughtful thresholds, consistent styling, and report-level footers — and you’ll turn static tables into interactive decision tools.

Looker Studio report edit view showing the table, right-side Table properties panel and 'Conditional formatting — Add formatting' option

Leave a Reply

Your email address will not be published. Required fields are marked *

*