Build Professional Tables in Looker Studio — Setup, Styling & Best Practices – #7

I often build dashboards so they tell a story from headline numbers to detailed rows. Tables are the most detailed element in that journey: they move you from snapshot to drillable data. In this guide I walk you step by step through creating usable, readable tables in Looker Studio. You will learn setup, styling, and the key parameters I use every time I build a KPIs-by-channel table.

If you prefer a video walk-through, watch the full tutorial here:

Step 1: Add the table and choose the layout

Start by adding a table chart to your report. I typically place the table at the bottom of the page because the dashboard logic I use goes from high-level to detailed: scorecards, time series, then table. A simple table works for most use cases. You can always switch table variants later from the chart picker or the style panel.

When you add the chart, give it a clear title and center-align it in the layout. That small step improves visual balance and makes the table feel intentional, not accidental.

Step 2: Configure header and cell styles first

I always start with header styles because the header controls readability. Set the header background to either transparent or a subtle color that matches your dashboard theme. For my black-and-green theme I often use transparent headers so the table feels lighter and less cluttered.

Next, experiment with cell borders and row colors. In many reports I choose transparent borders and avoid alternating row colors if I plan to apply a heatmap later. Alternating row colors can help, but they compete with conditional styling, so choose one approach.

Row numbers can help with reference, especially when you present top-n lists. Enable them when you want a fixed index column. Tooltips rarely matter for raw tables, so they are lower priority.

Step 3: Avoid horizontal scrolling — split your table instead

Horizontal scrolling makes tables hard to read. If your dataset contains many metrics, split the information across two tables or reduce columns. When horizontal scroll becomes unavoidable, only use it as a last resort.

Freeze the first column when you want the dimension to stay visible during vertical scrolling. But don’t freeze too many columns — you want space for numbers to breathe.

Step 4: Pick dimensions and the right granularity

Decide how you want to group data. For channel-performance tables, I use user default channel group as the main dimension. Then I add drilldown dimensions such as first user source and first user medium so viewers can click into source and medium without crowding the initial view.

Use drilldown when you expect viewers to explore hierarchies. If you prefer a flat list, add second and third dimensions directly, but be careful: that increases row count fast.

Step 5: Add the most relevant metrics

Choose metrics you already use in scorecards for consistency. I include active users, new users, average session duration, conversions, total purchases, total revenue, and average revenue per user. Tables allow more metrics than scorecards, so take advantage of that to provide context and efficiency metrics all in one place.

Metric sliders and optional metrics can be useful for exploration. They let you toggle metrics on and off during analysis. I usually leave the slider visible on hover so the table stays clean but interactive when needed.

Step 6: Resize columns and enable header wrap text

After you populate columns, resize them with Fit to data. That step quickly fixes truncated values and makes titles readable.

I wrap text for headers only. If you wrap body cells you risk creating variable row heights and long cells that break scanning. So: header wrap text on, body wrap text off. This combination preserves readability and keeps columns compact.

Step 7: Align numbers and make the table scannable

I align numeric columns to the center when the dashboard design calls for it. For tables with mixed content, align dimensions left and metrics center or right. Consistent alignment helps readers scan rows quickly.

Use compact number formatting when necessary, but be careful: compact formats can hide important precision. Decide whether short numbers or exact numbers serve the audience best.

Step 8: Use heatmaps and color to direct attention

A flat table is hard to interpret. Heatmaps solve that. I apply a green heatmap for most metrics to signal positive performance. For a high-priority metric such as conversions, I use a contrasting color like purple so that the eye naturally gravitates to that column.

When you apply heatmap styling, adjust the heatmap text contrast until values remain readable. Pick font colors that maintain strong contrast with cell backgrounds. If a heatmap makes numbers illegible, switch to lighter hues or apply the heatmap to fewer columns only.

Step 9: Interpret colors carefully — consider sample size

Colors show magnitude, but you must check counts. A high average revenue per user in a channel with two purchases does not equal sustainable performance. I always check conversion counts alongside efficiency metrics. If you see an unusually large direct channel in a demo or unexpected account, investigate tracking issues in Google Tag Manager.

Step 10: Add sorting, pagination, and row limits

Sort by the metric the team uses to make decisions. For example, sort by conversions when handoffs go to acquisition teams. You can also add a secondary sort if you want stable ordering.

Pagination is useful for long lists or when you want to highlight the top N rows. Set a row limit to show the top five or top ten items when you need concise executive views.

Step 11: Enable cross-filtering for interactive exploration

Cross-filtering turns a table into an interactive control. When cross-filtering is enabled, clicking a row filters other charts on the page to that dimension. I use this frequently to let stakeholders click an email row and see all dashboard charts update for email traffic only.

Cross-filtering works like a click filter and removes the need to add separate filter controls for quick exploration.

Step 12: Add comparison columns for context

Comparisons add context. You can compare the selected date range to the previous period or prior year. I usually limit comparisons to one or two columns (for example revenue per user) to avoid clutter. Choose either absolute change or percent change and set the decimal precision to a level that makes sense for the audience.

Use comparisons sparingly. When too many columns show change arrows and percentages, the table becomes noisy.

Step 13: Final polish and performance considerations

Do a final resize pass, test on small screens, and remove horizontal scrolling by further trimming columns. If the table still becomes slow, reduce row counts or limit metric calculations. Keep the table as lean as possible while preserving the necessary detail.

Quick checklist I follow before publishing

• Header background set to transparent or subtle color
• Cell borders and odd/even rows configured consistently
• Header wrap text enabled, body wrap text disabled
• Columns resized using Fit to data
• Heatmap applied to main metrics, accent color for priority metric
• Drilldown or second dimension added where exploration is required
• Cross-filtering enabled if interactive selection helps viewers
• Pagination or top-n row limit applied for executive cards
• Comparison columns limited and formatted clearly

Practical examples and settings I recommend

Below are specific settings I use for a channel KPIs table:

1. Dimension: User default channel group
2. Drilldown: First user source, first user medium
3. Metrics: Active users, New users, Avg session duration, Conversions, Total purchases, Total revenue, Avg revenue per user
4. Header: Transparent background, wrap text on
5. Body: No wrap, center-align numeric columns
6. Heatmap: Green for most metrics, purple highlight for conversions
7. Sort: Primary by conversions (descending), secondary by active users
8. Pagination: Show top 10, allow viewer to change pages
9. Cross-filtering: Enabled for interactive exploration

When to use conditional formatting

Conditional formatting gives you full control and can combine thresholds, symbols, and colors. I use conditional formatting when stakeholders require strict thresholds (for example CPA limits or minimum conversion counts). It deserves a separate deep dive because rules can become complex quickly. If you want a focused tutorial on conditional formatting, I can create one with practical examples.

Wrap up — how this table fits into the dashboard

Tables complete the story that starts with scorecards and time series. They help you go from an at-a-glance snapshot to actionable rows that reveal which channels, sources, or campaigns need work. A well-styled table reduces cognitive load, highlights what matters, and invites exploration through drilldowns and cross-filtering.

If you implement the steps above you will end up with a table that communicates clearly: it will be readable at a glance, highlight priority metrics, and let users dive into the rows that matter.

Tools I Use

To connect any data source to Looker Studio, I use:
Windsor.ai — quick connector for GA4, Facebook Ads, Google Ads, and more.
You can get 10% off any plan with my promo code gaillereports.
Supermetrics — a powerful connector for agencies and large data projects.
It’s ideal for scaling Looker Studio reports or combining multiple data sources.

If you work with Meta Ads or want to compare connectors, check out this guide:
Top Facebook Ads Connectors for Looker Studio — How to Choose the Right One

Recommended Next Reads on Gaille Reports

• 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)
• Looker Studio Tutorial 2025: Clean Dashboards Made Easy (Lesson 2)
• How to Visualize Data Over Time in Looker Studio Reports

---

Tables are where dashboards become actionable. Keep them lean, consistent, and interactive. Limit columns, align your metrics, and use color only where it adds value. When styled and configured properly, a Looker Studio table can be both beautiful and functional — turning raw data into clear insight.

If you’d like me to show detailed examples of conditional formatting rules (for thresholds, icons, or color ranges), leave a comment and I’ll prepare a walkthrough using GA4 data.