Tooltip customization in Tableau - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ visualization

intermediate

Customize Tooltip to Show Sales and Profit

You have a sales dashboard in Tableau. You want the tooltip to show both Sales and Profit values when hovering over a data point.

Which tooltip customization will correctly display both values?

A <p>Sales: <code><SUM([Sales])></code><br>Profit: <code><SUM([Profit])></code></p>

B <p>Sales: <code><SUM([Sales])></code></p>

C <p>Sales: <code><b><SUM([Sales])></b></code><br>Profit: <code><b><SUM([Profit])></b></code></p>

D <p>Sales: <code><SUM([Sales])></code><br>Profit: <code><SUM([Profit])></code><br>Discount: <code><SUM([Discount])></code></p>

💡 Hint

Remember to use the correct syntax for inserting field values inside tooltips.

Option A correctly uses the syntax to insert aggregated values in the tooltip. Option A uses invalid tags. Option A adds an extra field not requested. Option A only shows Sales.

🧠 Conceptual

intermediate

Purpose of Tooltip Customization in Tableau

Why is customizing tooltips important in Tableau dashboards?

A To filter data permanently based on user clicks.

B To change the color of the dashboard background.

C To add more detailed information about data points without cluttering the main view.

D To export data directly from the tooltip.

💡 Hint

Think about what tooltips do when you hover over data.

Tooltips provide extra details on demand, helping users understand data points better without adding clutter. Options A, B, and D describe unrelated features.

❓ dax_lod_result

advanced

Calculate Average Sales per Category in Tooltip

You want to show the average sales per product category in a tooltip using a Level of Detail (LOD) expression in Tableau.

Which LOD expression correctly calculates this?

A AVG({ FIXED [Category] : SUM([Sales]) })

B { INCLUDE [Category] : SUM([Sales]) }

C { EXCLUDE [Category] : AVG([Sales]) }

D { FIXED [Category] : AVG([Sales]) }

💡 Hint

LOD expressions use FIXED, INCLUDE, or EXCLUDE to control aggregation levels.

Option D fixes the calculation at the category level and averages sales correctly. Option D sums sales and includes category, which is not average. Option D excludes category, changing the level incorrectly. Option D averages category totals instead of sales per category.

🔧 Formula Fix

advanced

Fix Tooltip Showing Incorrect Profit Values

Your tooltip shows profit values that are too high. You suspect the aggregation is wrong.

Which of these tooltip expressions is causing the error?

A <p>Profit: <code><ATTR([Profit])></code></p>

B <p>Profit: <code><SUM([Profit])></code></p>

C <p>Profit: <code><AVG([Profit])></code></p>

D <p>Profit: <code><MIN([Profit])></code></p>

💡 Hint

ATTR returns a single value if all rows have the same value, else it shows an asterisk.

Using ATTR([Profit]) in a tooltip aggregates incorrectly when multiple rows exist, causing misleading values. SUM or AVG are appropriate aggregations for profit. MIN is valid but shows minimum, not total.

🎯 Scenario

expert

Design Tooltip to Show Dynamic Text Based on Sales Threshold

You want a tooltip that shows the text "High Sales" if sales are above 100,000 and "Low Sales" otherwise.

Which calculated field expression will produce this dynamic tooltip text?

A IF [Sales] > 100000 THEN 'High Sales' ELSE 'Low Sales' END

B IF SUM([Sales]) > 100000 THEN 'High Sales' ELSE 'Low Sales' END

C CASE WHEN SUM([Sales]) > 100000 THEN 'High Sales' ELSE 'Low Sales' END

D IF AVG([Sales]) > 100000 THEN 'High Sales' ELSE 'Low Sales' END

💡 Hint

Remember to aggregate sales before comparing to a threshold in Tableau calculated fields.

Option B correctly aggregates sales with SUM before comparison. Option B compares row-level [Sales], which may be invalid in tooltip context. Option B uses CASE WHEN syntax, which Tableau does not support. Option B uses AVG which changes logic.

Practice

1. What is the main purpose of customizing tooltips in Tableau dashboards?

easy

A. To export data to Excel

B. To change the color of the chart elements

C. To filter data automatically

D. To provide additional information when users hover over a visual

Solution

1. Step 1: Understand tooltip functionality

   Tooltips appear when hovering over visuals to show extra details.

2. Step 2: Identify customization purpose

   Customizing tooltips helps add meaningful info to improve user understanding.

3. Final Answer:

   To provide additional information when users hover over a visual -> Option D

4. Quick Check:

   Tooltip purpose = extra info on hover [OK]

Hint: Tooltips show info on hover, not change colors or export [OK]

Common Mistakes:

• Confusing tooltips with chart color settings
• Thinking tooltips filter data automatically
• Assuming tooltips export data

2. Which of the following is the correct way to insert a field value into a tooltip in Tableau?

easy

A. Type the field name directly without brackets

B. Insert the field using <<Field Name>> syntax

C. Use <Field Name> tags

D. Use double quotes around the field name

Solution

1. Step 1: Recall Tableau tooltip syntax

   Tableau uses double angle brackets to insert fields in tooltips.

2. Step 2: Match syntax to options

   Only <<Field Name>> matches Tableau's field insertion style.

3. Final Answer:

   Insert the field using <<Field Name>> syntax -> Option B

4. Quick Check:

   Field insertion = <<Field Name>> [OK]

Hint: Use double angle brackets <<Field>> to insert fields in tooltips [OK]

Common Mistakes:

• Typing field names without brackets
• Using HTML tags instead of Tableau syntax
• Putting field names in quotes

3. Given this tooltip text in Tableau:

Sales: <<SUM(Sales)>>
Region: <<Region>>

What will the tooltip show when hovering over a mark with Sales = 5000 and Region = 'West'?

medium

A. Sales: SUM(Sales)\nRegion: Region

B. Sales: <<SUM(Sales)>>\nRegion: <<Region>>

C. Sales: 5000\nRegion: West

D. Sales: 5000 Region: West

Solution

1. Step 1: Understand field insertion in tooltip

   Tableau replaces <<SUM(Sales)>> with the sum value and <<Region>> with the region name.

2. Step 2: Interpret line breaks and values

   \n creates a new line, so values appear on separate lines with actual data.

3. Final Answer:

   Sales: 5000\nRegion: West -> Option C

4. Quick Check:

   Tooltip shows actual values with line breaks [OK]

Hint: <<Field>> shows actual data; \n creates new line in tooltip [OK]

Common Mistakes:

• Thinking <<Field>> stays as text
• Ignoring line breaks in tooltip
• Confusing field names with values

4. You customized a tooltip but it shows the literal text <<Profit>> instead of the profit value. What is the most likely cause?

medium

A. The field name is misspelled or does not exist

B. You forgot to add a line break

C. The tooltip is disabled in the worksheet

D. You used single angle brackets instead of double

Solution

1. Step 1: Check field name correctness

   If Tableau shows <<Profit>> literally, it means it cannot find the field to replace.

2. Step 2: Rule out other causes

   Line breaks or tooltip enablement do not cause literal text display; wrong brackets cause syntax errors.

3. Final Answer:

   The field name is misspelled or does not exist -> Option A

4. Quick Check:

   Literal <<Field>> means field missing or misspelled [OK]

Hint: Check field spelling if tooltip shows <<Field>> literally [OK]

Common Mistakes:

• Assuming line breaks cause literal text
• Thinking tooltip must be enabled to show fields
• Using single < > instead of << >>

5. You want to create a tooltip that shows the product name, sales amount formatted as currency, and a custom message on separate lines. Which tooltip text will achieve this correctly in Tableau?

hard

A. Product: <<Product Name>>\nSales: $<<SUM(Sales)>>\nThank you for your interest!

B. Product: <<Product Name>>Sales: $<<SUM(Sales)>>Thank you for your interest!

C. Product: <<Product Name>>
Sales: <<SUM(Sales, '$')>>
Thank you for your interest!

D. Product: <<Product Name>>
Sales: $<<SUM(Sales)>>
Thank you for your interest!

Solution

1. Step 1: Use correct line break syntax

   Tableau tooltips use \n (backslash n) for line breaks, not HTML <br> tags or literal \n in text.

2. Step 2: Format sales as currency

   Prepending $ before <<SUM(Sales)>> formats sales as currency in tooltip text.

3. Step 3: Verify custom message placement

   Custom text can be added as plain text on its own line.

4. Final Answer:

   Product: <<Product Name>>\nSales: $<<SUM(Sales)>>\nThank you for your interest! -> Option A

5. Quick Check:

   Use \n for lines and $ before sum for currency [OK]

Hint: Use \n for new lines and $ before <> for currency [OK]

Common Mistakes:

• Using HTML
  tags inside tooltip text
• Trying to format currency inside <>
• Using literal \n instead of escape sequence