What is Tableau Day?

If you’ve heard data analysts talk about their “Tableau Day,” you might be picturing a conference or a company-sponsored holiday. The reality is both more personal and far more significant for anyone working with data. "Tableau Day" is the slang term for the a-ha moment when a user finally understands Level of Detail (LOD) expressions, a fundamental yet powerful concept in Tableau that unlocks a new world of analysis. This article breaks down exactly what LOD expressions are in plain English and gives you practical examples of how to use the big three: FIXED, INCLUDE, and EXCLUDE.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Understanding 'Level of Detail' Before Anything Else

Before touching any LOD expressions, it’s vital to understand the concept of the “level of detail” of your view, or "Viz LOD." In Tableau, the level of detail is simply the combination of all the dimensions you’ve dragged onto your worksheet canvas. Each dimension you add slices your data into smaller, more granular pieces.

For example:

• If you just have SUM(Sales) on your sheet, the level of detail is completely aggregated - it’s just one number, your total sales.
• If you drag the Region dimension onto the Rows shelf, the level of detail is now Region. Tableau calculates SUM(Sales) for each unique region.
• If you then drag the Category dimension onto the Rows shelf, the level of detail becomes Region + Category. The calculation now shows the sum of sales for each category within each region.

Simple calculations in Tableau are always dependent on the dimensions in your view. The challenge arises when you need to perform a calculation at a different level of detail than what’s currently displayed in your worksheet. That’s exactly what LOD expressions were created to solve.

The Core of Tableau Day: The Three Types of LOD Expressions

LOD expressions give you the power to explicitly state the level of detail at which a calculation should be performed, overriding the dimensions present in your view. They always start with a curly brace { and end with one }.

The Syntax of an LOD Expression

Don't be intimidated by the syntax. Once you see the pattern, it becomes much easier to read and write. An LOD expression has three main parts:

{ KEYWORD [Dimension 1], [Dimension 2] : AGGREGATE([Measure]) }

• KEYWORD: This is where you put FIXED, INCLUDE, or EXCLUDE.
• Dimension Declaration: This is where you list the dimension(s) you want to use for the calculation. This is what sets the level of detail.
• Aggregate Expression: This is the calculation you want to perform, like SUM([Sales]) or COUNTD([Customer ID]).

Let's dive into each keyword with practical examples you might actually use.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

FIXED: Ground Your Calculation in Place

The FIXED LOD expression is the most powerful and common. It performs a calculation at the exact level of detail specified by the dimensions you list, completely ignoring most other dimensions and filters on your worksheet. Think of it as creating a permanent value attached to that specific-dimensional combination.

When to use FIXED:

• When you need a value that shouldn't change when users filter your dashboard.
• When you need to compare a value against a larger, fixed total (e.g., cohort analysis).
• Calculating things like a customer’s first purchase date or their total lifetime value.

Example: Finding Each Customer's Total Spending

Let's say you want to build a view that shows every order from every customer. But alongside each order, you also want to see that customer's total lifetime spend to easily identify high-value customers. The problem? If you add Customer ID to your view, SUM(Sales) will only give you the sales for that specific order.

The Calculation

Create a calculated field called "Total Customer Spend" with this expression:

{ FIXED [Customer ID] : SUM([Sales]) }

What It’s Doing:

This expression tells Tableau: “For every unique Customer ID, calculate the total sum of their Sales across all of their orders, and save that number.” This calculation happens behind the scenes, effectively creating an invisible table that looks something like this:

• Customer 101: $1,500
• Customer 102: $350
• Customer 103: $2,700

Now, when you drag this new "Total Customer Spend" field into a view that is detailed down to the individual Order ID, it will show the same total value for every order belonging to that same customer, allowing for powerful comparisons.

This lets you ask questions like "Show me all orders made by customers whose lifetime value is more than $10,000." without the view's level of detail getting in the way.

INCLUDE: Add a Dimension Just for This Calculation

As the name suggests, the INCLUDE LOD expression calculates a value at a level of detail that is more granular than your current view by adding a specified dimension to the calculation.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

When to use INCLUDE:

• When you want to find an average of subtotals. For example, “What is the average sales amount per customer for each region?” If you only have Region in your view, a regular AVG(Sales) will just give you the average of all individual sale amounts. But what you want is the average of each customer’s total.

Example: Calculating Average Customer Sales by Region

Imagine your worksheet shows Sales by Region. This gives you the total sales in the West, East, Central, and South regions.

Now, you want to know the average amount each customer spent within each of those regions. This requires a two-step thought process:

1. First, find the total sales for each individual customer within each region.
2. Then, average those totals up to the region level.

A simple AVG([Sales]) won't work because it averages every single transaction, not the customer-level sums.

The Calculation

Create a calculated field called "Average Customer Sales" with this expression:

{ INCLUDE [Customer ID] : SUM([Sales]) }

What It’s Doing:

This looks deceptively simple. When you bring this new field into your view which only contains Region, and set its aggregation to Average, here’s what Tableau does:

• Your view is at the Region level.
• For the calculation, it tells Tableau to "include" the Customer ID level, even though it's not in the view.
• It calculates the SUM(Sales) for each unique [Region], [Customer ID] combination.
• Then, when you set the calculation to Average in your view, it averages those SUM(Sales) values up to the Region level displayed in your viz.

This correctly gives you the "Average of each customer's total spend" for each region, a much more valuable insight.

EXCLUDE: Temporarily Ignore a Dimension

The EXCLUDE LOD expression is the opposite of INCLUDE. It is used when you want your calculation to be performed at a less granular level than your view by subtracting a dimension that is currently in your visual.

When to use EXCLUDE:

• It's most common when you need to compare values in your view to a subtotal or grand total without being affected by some of the detail. Think "percent of total" calculations where the "total" ignores one of the dimensions in your view.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Example: Comparing Regional Sales to the Category Total

Imagine a view that shows Sales with Category and Region on the Rows shelf. This gives you a detailed breakdown of sales for Office Supplies in the West, Technology in the East, etc.

Now you want to know: "For the Technology category, what percentage of its overall total sales came from the West region?" To do that calculation (Regional Technology Sales / Total Technology Sales), you need a calculation for the denominator that ignores the Region dimension in your view.

The Calculation

Create a calculated field called "Category Total Sales" with this expression:

{ EXCLUDE [Region] : SUM([Sales]) }

What It’s Doing:

For any row in your visualization, this expression tells Tableau: “Look at the dimensions currently defining this row (e.g., Category and Region), but for this calculation, temporarily remove Region and then perform a SUM(Sales).”

The result is a calculation that returns the total sales for the Category of that row across all regions. Now you can easily create one more calculated field - SUM([Sales]) / SUM([Category Total Sales]) - to get the percentage you were looking for.

Choosing the Right LOD at the Right Time

When you're first starting, it can be tough to know which one to pick. Here’s a simple cheat sheet:

• Use FIXED when you want to compute a value at a completely independent level of detail that is not affected by the dimensions in your view. It's great for unchanging attributes like a cohort acquisition date or total customer lifetime value.
• Use INCLUDE when you need to calculate at a finer level of detail than is present in your view. Think about calculating averages of sums or maximums of totals.
• Use EXCLUDE when you need to calculate at a coarser level of detail than is present in your view. It's perfect for "percent of total" scenarios where the total needs to ignore some of the details in your viz.

Final Thoughts

Your personal "Tableau Day" is a major milestone. Mastering FIXED, INCLUDE, and EXCLUDE moves you from simply visualizing data to performing truly sophisticated analysis that can answer much more complex business questions. It’s the difference between asking "what were our sales?" and "how do our top customers' individual purchases compare to their overall lifetime value?"

Mastering these calculations is incredibly rewarding, but it’s also a reminder of the steep learning curve present in many traditional BI tools. At Graphed we felt powerful analysis shouldn’t require such a long and technical journey. Instead of forcing you to learn complex functions and calculation syntax, we built a tool that understands your business questions in plain English. Just connect your data sources, and you can ask things like, "compare my ad spend versus my revenue for each campaign," and our AI data analyst builds the dashboard or generates the insight for you in seconds - live and ready to be shared, with no learning curve required.