Conditional Formatting in Data Studio Tables Without Making Them Noisy

• Format one thing per table
• Use colour for meaning, not decoration
• Prefer bars and heatmaps for magnitude
• Base rules on calculated fields
• Test with real ranges

Conditional formatting is the fastest way to draw attention to a number in Data Studio (formerly Looker Studio), and the fastest way to make a table unreadable. I’m Harsh Khubchandani, an independent Data Studio consultant based in New Delhi, and these are the rules I follow on client reports.

§Format one thing per table

If every column has colour, nothing stands out. I pick the single metric the reader must act on, usually a variance against target, and format only that.

§Use colour for meaning, not decoration

• Red for below target, green for on or above target, and nothing for everything in between.
• Keep the same colours on every page so readers learn them once.
• Avoid red and green as the only signal for colour-blind readers. Add an arrow or a “+/-” value next to it.

§Prefer bars and heatmaps for magnitude

For “how big” rather than “good or bad”, I use the table’s bar or heatmap display on a metric column instead of rules. It shows scale without implying judgement.

§Base rules on calculated fields

Rather than writing complex conditions inside the formatting panel, I create a calculated field such as a status label (On track, At risk, Off track) and format on that. It is easier to explain, easier to change and reusable across charts.

§Test with real ranges

Before handing over, I switch the date range to a bad month and a good month to check that the formatting still makes sense. Rules that look fine on one period often paint the whole table red on another.

Simple formatting is one of the things I look at in a free 30-minute report review. Details at https://datastudioconsultant.com/