Tableau Actions: Filter, URL, and Highlight Actions Explained

Tableau actions are the mechanism for making dashboards interactive — allowing users to drive the analytical experience rather than passively receiving a static view. Well-designed actions turn a presentation into an analytical tool. Poorly designed actions create confusion about what is filtered, what is selected, and why numbers change unexpectedly. This guide covers every action type, the most effective design patterns, and the common mistakes that make actions frustrating.

The Four Action Types

### Filter Actions

Filter actions use the selection in one sheet as a filter condition for one or more target sheets. When a user clicks a region in a map, the time-series chart below shows only data for that region.

Configuration choices:

**Run on:** Determines when the action fires — Select (click), Hover (mouse over), or Menu (right-click context menu).

- Select is the default and most intuitive for filter actions

- Hover is useful for tooltips and preview contexts where you do not want to commit to a selection

- Menu is less discoverable but useful when you want the action to be explicit rather than automatic

**Clearing the selection:** What happens when the user clicks on an empty area to deselect? Options: Leave the filter (keeps the last selection), Remove all values (returns to unfiltered state), or Show all values (all values, which may differ from the unfiltered state for some calculation types). Leave the filter is useful for drill-down workflows; Show all values is better when users should be able to return to the full dataset with a single click.

**Source and target:** Actions can filter within a sheet, across sheets on a dashboard, or across sheets in separate worksheets. Using a "source" sheet (the control) to filter a "target" sheet (the result) is the most common pattern.

**Multi-sheet filtering:** A single filter action can target multiple sheets simultaneously. All sheets that should update when a region is selected should be listed as targets.

### URL Actions

URL actions open a URL when a mark is selected — navigating to an external website, opening a support ticket, launching another internal tool, or opening a deeper detail view.

The URL can include field values from the selected mark using angle-bracket syntax: opening https://salesforce.com/opportunity/[Opportunity ID] navigates to the specific Salesforce record for the selected opportunity.

Design pattern: Navigation to external context

URL actions bridge Tableau to external systems. A sales pipeline dashboard where clicking an opportunity name opens that opportunity in Salesforce; a customer health dashboard where clicking a customer opens their Zendesk tickets; a campaign performance view where clicking a campaign opens the Google Ads campaign editor.

**URL action in a new tab vs same tab:** URL actions default to opening in the current browser tab, replacing the Tableau view. Configure to open in a new tab to preserve the Tableau context.

### Navigate Actions

Navigate actions navigate to a different dashboard or sheet within the same Tableau workbook. They enable multi-level drill-down experiences where the top-level dashboard provides summary context and clicking navigates to a detail view.

Design pattern: Summary to detail

Dashboard 1: Sales overview by region and product category

Navigate action on region → Dashboard 2: Detailed view of the selected region, with rep-level performance and deal pipeline

Navigate action on a deal → Dashboard 3: Individual deal details and activity history

Navigate actions preserve the filter context from the source — the detail dashboard loads pre-filtered to the selected item.

### Highlight Actions

Highlight actions change the opacity of non-selected marks, visually emphasising the selected marks while keeping the non-selected marks visible (greyed out). Unlike filter actions, highlight actions do not remove data — they preserve context while drawing attention to the selection.

**When to use highlight vs filter:** Filter actions are appropriate when the user wants to focus exclusively on the selected segment. Highlight actions are appropriate when the comparison between the selected segment and the full dataset is analytically meaningful — the user wants to see how the selection relates to everything else.

Designing Dashboard Interactions

### The Drill-Down Pattern

The most common effective action design: a summary view with broad aggregation, where clicking drills into a more specific view.

1. Top-level: KPI tiles + regional bar chart + trend line

2. Click a region → filter action → Regional detail: rep-level performance, pipeline by stage, recent deals

The user experience is: the summary answers "where is performance good or bad?" and the drill-down answers "what specifically is happening in that area?"

The mistake: making the drill-down the first view. Users need the summary context before the drill-down means anything.

### The Cross-Filter Pattern

Multiple charts on the same dashboard that all filter each other. Clicking a segment in one chart immediately updates all other charts to show only that segment.

**Implementation:** Create one filter action per source sheet, each targeting all other sheets on the dashboard. When a user clicks any element, all other charts filter to match.

**The caveat:** Cross-filtering with LOD expressions can produce surprising results. FIXED LODs ignore filter context unless promoted to context filters — a cross-filter action may not affect FIXED LODs as expected. Test cross-filter behaviour carefully with any LOD calculations on the dashboard.

### The Master-Detail Pattern

A list or table on the left, a detail view on the right. Clicking a row in the table populates the detail view with that record's information.

Implementation: a text table as the source sheet (run on Select, with clicking a row as the trigger), a collection of detail sheets as the target.

For this pattern to feel intuitive, the default state (nothing selected) should show something meaningful in the detail view — not an empty chart. Use a parameter with a default value to display a "select an item to see details" message or to show the overall summary when nothing is selected.

Common Action Mistakes

**Multiple overlapping actions with conflicting targets:** If a dashboard has filter action A targeting sheets 1, 2, and 3, and filter action B targeting sheets 2 and 3 but not 1, clicking in a way that triggers both actions produces confusing results — sheet 1 is partially filtered. Audit all actions on a dashboard to ensure the filter logic is consistent.

**Using hover actions for interactive filtering:** Hover actions fire as the mouse moves across marks, causing the filter to change continuously as the user moves. This is rarely the intended behaviour for filter actions; use Select instead.

**Not configuring "clear selection" behaviour:** Without careful thought about clearing, users encounter unexpected states — selecting a region, then clicking on an empty area of the map, and not being sure whether the charts are now filtered to the region or unfiltered. Be explicit about what clicking empty space should do.

**Actions that do not work on mobile:** Some action patterns (hover actions, right-click menu) do not translate to touch interfaces. If the dashboard will be used on Tableau Mobile or a tablet, test the interaction model on touch before deploying.

**Circular filter actions:** Actions where Sheet A filters Sheet B and Sheet B filters Sheet A create infinite loops. Test all cross-filter configurations for circular dependencies.

Our Tableau consulting practice engineers interactive dashboard experiences — contact us to discuss dashboard design for your analytical use cases.

A former Microsoft data architect audits your data foundation, identifies your top priorities, and sends you a written plan. Free. No pitch.