Power BI Report Page Tooltips - Adding Context Without Cluttering Your Dashboard

There's a constant tension in dashboard design between showing enough information and showing too much. Stakeholders want the big picture at a glance, but they also want to drill into specifics without leaving the page. Cram everything onto one screen and you end up with a wall of tiny charts that nobody reads. Strip it back too far and you get constant requests for "can you also show the breakdown by region?"

Report page tooltips in Power BI hit a sweet spot that I think is underused. They let you attach rich, formatted detail to any visual on your report - detail that only appears when a user hovers over a data point. The dashboard stays clean, but the depth is there when someone wants it.

We've been building Power BI solutions for Australian organisations at Team 400 for years, and tooltips are one of those features that consistently impress stakeholders during demos. Here's how to use them well.

What report page tooltips actually are

A report page tooltip is a separate report page - small in size, usually 320x240 pixels - that appears as a popup when a user hovers over a visual. Unlike the default tooltips (which just show the value), page tooltips can contain any combination of visuals, text, shapes, and images.

You design them like any other report page. Add charts, KPIs, formatted text, whatever tells the story. Then you associate the tooltip page with specific visuals on your main report. When someone hovers over a data point in the main visual, Power BI passes the filter context (the specific product, region, time period, or whatever the user hovered over) into the tooltip page, and the tooltip visuals filter accordingly.

It's a simple concept, but the execution details matter.

Three patterns that work well

1. Show a different time perspective

This is my favourite use of page tooltips, and it's the one that gets the best reaction from business users.

Say you have a bar chart showing monthly revenue by product. A user hovers over the October bar for Product A. The default tooltip shows "$1.2M." That's fine, but it tells you nothing about the trend.

With a page tooltip, you can show a line chart of the last 12 months for that product, right in the hover popup. The user sees the October value in context - is $1.2M a spike? A dip? Part of a steady climb? They get the answer without clicking anything or navigating to another page.

The trick here is that the tooltip page applies a different time filter than the source visual. The source visual shows one month. The tooltip shows the full year. You set this up by configuring the tooltip page filters to show a rolling 12-month window while the source visual's filter context identifies which product to highlight.

2. Add supporting detail

This is the most straightforward pattern. You have a summary visual - say average violation scores by postcode - and the tooltip shows the specific attributes and statistics for whichever postcode the user hovers over.

Think of it as a details pane that appears on demand. Instead of building a separate detail page and requiring the user to click through to it, the information appears instantly on hover. For operational dashboards where managers are scanning through dozens of items, this saves a lot of time.

A practical example from a project we did for an Australian logistics company: the main map showed delivery performance by depot. Hovering over a depot showed the tooltip with that depot's top 5 delayed routes, current vehicle utilisation, and the name of the depot manager. The operations director could scan the map and immediately see which depots needed attention without drilling through to separate pages.

3. Embedded help text

This one's less obvious but genuinely useful. You can configure visual headers to display a tooltip when users hover over the header icon. Use this to explain what a metric means, how it's calculated, or what action to take based on the values.

For complex dashboards where not every user understands every metric, this is better than a separate "definitions" page that nobody reads. The help appears right where the user needs it, right when they need it.

I've seen this work particularly well in finance dashboards. Acronyms and calculated metrics like "EBITDA margin adjusted for one-offs" mean different things in different organisations. A tooltip on the visual header that explains the specific calculation for your organisation removes ambiguity without cluttering the dashboard.

Design recommendations

Having built quite a few tooltip-enhanced reports, here are the things that make the difference between tooltips that feel polished and ones that feel janky.

Keep them small. The built-in Tooltip page size is 320x240 pixels. You can go larger, but resist the urge. An oversized tooltip obscures the visuals underneath it, which defeats the purpose. If you need that much space, you probably want a drillthrough page instead of a tooltip.

Design at actual size. Switch the page view to Actual Size when designing tooltip pages. The default Fit to Page view makes your tiny tooltip page fill the entire screen, which gives you a false sense of how much space you have. Design at actual size and you'll make better choices about what to include.

Match the report's visual style. Tooltips that use a completely different colour scheme or font from the main report feel disconnected. Use the same theme. If you want the tooltip to be visually distinct, a subtle background colour change is enough.

Remove design-time filters before publishing. When you're building a tooltip page, you'll probably add filters so you can preview it with realistic data (e.g., filter to a specific product so you can see how the tooltip looks). Remove those filters before you publish, or your tooltips will always show data for that one product regardless of what the user hovers over. I've seen this mistake in production reports more than once.

Hide your tooltip pages. Users shouldn't be able to navigate directly to a tooltip page using the page tabs. Right-click the page tab and select Hide Page. The tooltips still work when hidden - they just don't appear in the page navigation.

When to use tooltips vs drillthrough

This question comes up in every Power BI project, so here's how I think about it.

Tooltips are for quick, passive exploration. The user doesn't have to decide to investigate - they just notice extra detail while scanning. Tooltips should take less than two seconds to read and understand. No interaction is supported within a tooltip, so if you need the user to click, filter, or explore further, a tooltip is the wrong choice.

Drillthrough pages are for deliberate investigation. The user right-clicks a data point and chooses to navigate to a detail page. The detail page can be full-sized, interactive, and as complex as needed. Use drillthrough when the investigation requires more than a glance.

In practice, the best reports use both. Tooltips provide the quick "is this interesting?" signal. If the answer is yes, drillthrough lets the user go deeper. Think of tooltips as a preview of what the drillthrough page shows in full.

Common mistakes

Too much in the tooltip. If your tooltip has five visuals, three KPIs, and a text box, it's too much. Pick the one or two things that add the most context and leave everything else for a drillthrough page.

Incompatible filter contexts. A tooltip page only works when its filters are compatible with the source visual. If your source visual groups by product but your tooltip page filters by customer, the tooltip won't appear. Power BI just silently skips it. This is confusing to debug if you're not aware of it, because there's no error message - the tooltip simply doesn't show up.

Forgetting to test across data points. A tooltip that looks great for one product might overflow or display weirdly for another product with a longer name or more data points. Test your tooltips across a range of representative data.

Getting started

If you haven't used page tooltips before, Microsoft's documentation on report page tooltips walks through the setup process in detail.

For organisations that want help designing Power BI reports that balance simplicity with depth - including tooltip strategies, drillthrough patterns, and overall dashboard architecture - our consulting team works with Australian businesses across a range of industries. We've learned what works through building hundreds of reports, and we're happy to share those patterns with your team.

If you're looking at broader data strategy beyond just reporting, our business intelligence practice covers the full spectrum from data modelling through to self-service analytics.