Moving average in Tableau - Step-by-Step Guide

Introduction

A moving average smooths out data by calculating the average of a set number of points over time. It helps you see trends clearly by reducing random ups and downs in your data.

When you want to show sales trends over months without daily fluctuations.

When analyzing website traffic to see overall visitor patterns instead of daily spikes.

When comparing stock prices over time to identify general movement.

When your dashboard needs to highlight seasonal patterns by smoothing data.

When you want to reduce noise in customer satisfaction scores collected weekly.

Steps

Step 1: Open your Tableau workbook

- Tableau Desktop main window

Your data and worksheets are visible

Step 2: Drag the date field to the Columns shelf

- Columns shelf

Dates appear along the horizontal axis

Step 3: Drag the measure you want to analyze (e.g., Sales) to the Rows shelf

- Rows shelf

A line chart or bar chart shows the measure over time

Step 4: Click the measure pill on the Rows shelf to open the menu

- Rows shelf measure pill

A menu with options appears

Step 5: Select 'Quick Table Calculation' then choose 'Moving Average'

- Quick Table Calculation submenu

The chart updates to show the moving average line smoothing the data

Step 6: Click the measure pill again and select 'Edit Table Calculation' to customize

- Rows shelf measure pill menu

The Table Calculation dialog opens where you can set the number of periods for the moving average

💡 Adjust the number of previous values to average for smoother or more detailed trends

Before vs After

Before

Line chart shows daily sales with many ups and downs, making it hard to see the overall trend

After

Line chart shows a smooth curve representing the moving average of sales, making the trend clear

Settings Reference

Calculation Type

📍 Quick Table Calculation menu

Choose the type of calculation to apply to your measure

Default: None

Moving Average Period

📍 Edit Table Calculation dialog

Set how many data points to include in the moving average calculation

Default: 2

Compute Using

📍 Edit Table Calculation dialog

Define the direction or dimension over which the calculation is performed

Default: Table (Across)

Common Mistakes

Applying moving average without setting the correct compute direction

The calculation may average data incorrectly across wrong dimensions, causing misleading results

Use 'Edit Table Calculation' to set 'Compute Using' to the correct dimension, usually the date field

Using too few periods for moving average

The line remains too jagged and does not smooth the data effectively

Increase the number of periods in the moving average to better smooth fluctuations

Summary

Moving average smooths data to reveal trends by averaging values over time.

Use Tableau's Quick Table Calculation to add moving averages easily.

Remember to set the correct compute direction and period length for accurate results.

Practice

1. What is the main purpose of using a moving average in Tableau visualizations?

easy

A. To smooth out short-term fluctuations and highlight longer-term trends

B. To count the total number of data points in a dataset

C. To filter out all data except the latest value

D. To create a pie chart from time series data

Solution

1. Step 1: Understand moving average concept

   A moving average calculates the average of data points over a specific number of periods to reduce noise.

2. Step 2: Identify its purpose in visualization

   This smoothing helps reveal underlying trends by minimizing short-term ups and downs.

3. Final Answer:

   To smooth out short-term fluctuations and highlight longer-term trends -> Option A

4. Quick Check:

   Moving average = smoothing trends [OK]

Hint: Moving average smooths data to show trends clearly [OK]

Common Mistakes:

• Confusing moving average with total sum
• Thinking it filters data instead of smoothing
• Assuming it creates categorical charts

2. Which of the following is the correct Tableau calculation syntax to compute a 3-period moving average of SUM(Sales)?

easy

A. WINDOW_AVG(SUM([Sales]), 0, 2)

B. WINDOW_AVG(SUM([Sales]), -1, 1)

C. WINDOW_AVG(SUM([Sales]), -2, 0)

D. WINDOW_AVG(SUM([Sales]), -1, 2)

Solution

1. Step 1: Understand WINDOW_AVG parameters

   WINDOW_AVG(expression, start, end) averages values from start to end relative to current row.

2. Step 2: Define 3-period window around current row

   For 3 periods centered on current row, use -1 (previous), 0 (current), and 1 (next), so range is -1 to 1.

3. Final Answer:

   WINDOW_AVG(SUM([Sales]), -1, 1) -> Option B

4. Quick Check:

   3-period window = -1 to 1 [OK]

Hint: Use negative and positive offsets to set window range [OK]

Common Mistakes:

• Using incorrect window range that doesn't cover 3 periods
• Confusing start and end parameters
• Omitting SUM aggregation inside WINDOW_AVG

3. Given the following data points for Sales over 5 days: [100, 120, 140, 160, 180], what is the 3-day moving average value for day 3 using WINDOW_AVG(SUM([Sales]), -1, 1)?

medium

A. 120

B. 160

C. 130

D. 140

Solution

1. Step 1: Identify the 3-day window for day 3

   Day 3 includes day 2 (120), day 3 (140), and day 4 (160) because window is from -1 to +1 relative to day 3.

2. Step 2: Calculate average of these values

   (120 + 140 + 160) / 3 = 420 / 3 = 140

3. Final Answer:

   140 -> Option D

4. Quick Check:

   Average of 120,140,160 = 140 [OK]

Hint: Average values one before, current, and one after [OK]

Common Mistakes:

• Including wrong days in the window
• Calculating sum instead of average
• Using only previous days without current or next

4. You wrote this Tableau calculation for a 5-day moving average: WINDOW_AVG(SUM([Sales]), -2, 2). However, the moving average is not showing correctly on the first two days. What is the likely issue?

medium

A. The window range includes days outside the data, causing NULLs to affect the average

B. SUM aggregation is missing inside WINDOW_AVG

C. WINDOW_AVG requires only positive offsets for the window

D. The calculation should use WINDOW_SUM instead of WINDOW_AVG

Solution

1. Step 1: Analyze window range impact on edge rows

   Window from -2 to 2 means for first two days, some offsets point to non-existent previous days (before data starts).

2. Step 2: Understand effect of NULLs in window

   These NULLs can cause the average to be incorrect or missing because Tableau includes them in calculation.

3. Final Answer:

   The window range includes days outside the data, causing NULLs to affect the average -> Option A

4. Quick Check:

   Edge rows have incomplete windows causing NULL impact [OK]

Hint: Check window range near data edges for NULLs [OK]

Common Mistakes:

• Assuming WINDOW_AVG ignores NULLs automatically
• Confusing aggregation functions inside WINDOW_AVG
• Thinking window offsets must be positive only

5. You want to create a 7-day moving average of daily sales but only for weekdays (Monday to Friday). Which approach correctly handles this in Tableau?

hard

A. Use WINDOW_AVG(SUM([Sales]), -3, 3) and filter out weekends before calculation

B. Use WINDOW_AVG(SUM([Sales]), -6, 0) ignoring weekends in data

C. Create a calculated field that excludes weekends, then use WINDOW_AVG over consecutive weekdays

D. Apply WINDOW_AVG on all days and manually remove weekend values from the result

Solution

1. Step 1: Understand weekday filtering impact

   Simply filtering weekends after calculation or ignoring them breaks the consecutive window needed for moving average.

2. Step 2: Use calculated field to exclude weekends before averaging

   By creating a field that removes weekends, the WINDOW_AVG function works on consecutive weekdays only, producing accurate 7-day averages.

3. Final Answer:

   Create a calculated field that excludes weekends, then use WINDOW_AVG over consecutive weekdays -> Option C

4. Quick Check:

   Exclude weekends before WINDOW_AVG for correct weekday moving average [OK]

Hint: Filter weekends before applying moving average [OK]

Common Mistakes:

• Applying WINDOW_AVG including weekends causing wrong averages
• Using wrong window size ignoring missing days
• Filtering weekends after calculation instead of before