Skip to main content
A treemap chart displays hierarchical data as a set of nested rectangles, where each branch of the hierarchy is represented by a colored rectangle containing smaller rectangles representing sub-branches. The size of each rectangle is proportional to a specified measure.

Use cases

Treemap charts are particularly useful for visualizing:
  • File system structures and disk space usage
  • Organizational hierarchies and headcount distribution
  • Budget breakdowns across categories and subcategories
  • Market share analysis by company, product line, and region
  • Portfolio composition showing asset allocation
  • Website analytics showing page hierarchy and traffic volume

Data structure

Treemap charts require hierarchical data with categories and values:
  • Hierarchy levels - One or more dimensions that define the nested structure (e.g., category, subcategory)
  • Values - A measure that determines the size of each rectangle
When setting up your query, keep the following in mind:
  • Treemap charts work best when there is a clear hierarchy in your data with multiple levels
  • Each level of the hierarchy should have a reasonable number of categories to maintain readability
  • The measure used for sizing should have meaningful variation across categories to create visual distinction

Hierarchical structure

Treemaps naturally represent parent-child relationships. For example, a budget dataset might include:
  • Level 1: Department (Sales, Marketing, Engineering)
  • Level 2: Category (Salaries, Travel, Software)
  • Value: Budget amount
The chart will display departments as large rectangles, with smaller nested rectangles inside representing the budget categories within each department.

Configuration

To view the configuration options for a treemap chart, open the Chart options panel in a workbook.

Orientation

The Orientation setting controls the layout direction for rectangles within each level:
  • Horizontal - Rectangles arranged left to right
  • Vertical - Rectangles arranged top to bottom

Color

Treemap charts support multiple coloring modes:
  • Discrete - Assigns a distinct color from the palette to each top-level category
  • Gradient - Applies a continuous color scale based on rectangle size, where larger values receive more saturated colors
Treemap charts inherit modeled colors when defined. You can also apply color overrides to individual categories.

Labels

Toggle data labels to display category names and values on rectangles. Label options include:
  • Font size - Adjust the label text size
  • Styling - Bold and italic options
Labels automatically hide for rectangles that are too small to display text clearly.

Tooltips

Tooltips appear when hovering over rectangles to display detailed information about that segment of the hierarchy.

Default tooltip content

Tooltips display the category name, full hierarchy path, and the measure value for the selected rectangle. Use the tooltip configuration to add additional fields to tooltips.

Generating treemaps with AI

You can prompt the Omni Agent to generate a treemap chart directly from your query results. The Omni Agent can configure:
  • Grouping - The dimension fields that define the nested hierarchy, in the order you want them nested
  • Value - The measure field that determines the size of each rectangle
  • Color - An optional field that colors rectangles independently of grouping. A numeric field creates a gradient; a categorical field uses discrete colors
  • Hierarchy levels - How many nested levels display at once. By default only the top level displays, and you click a rectangle to drill into deeper levels
The Omni Agent does not configure the minimum rectangle size shown before a rectangle is hidden - this always uses the same default as the Chart options panel.

Troubleshooting

The treemap chart type requires a dimension and a measure. If you don’t see the treemap option in the Chart selector, add the required fields to your query.
When your data has many categories or deep hierarchies, some rectangles may become too small to be useful. Consider:
  • Filtering your data to focus on specific branches of the hierarchy
  • Limiting the depth of hierarchy levels included in your query
  • Using a different visualization type for data with a very large number of small categories