Tableau Blending vs Joining: Why Your Metrics Look Wrong and How to Fix It

You publish a dashboard, the numbers look reasonable, and then a stakeholder points out that the revenue total doesn't match the finance report. You dig in and everything seems correct. The culprit is often hiding in plain sight: Tableau silently chose a data blend where you expected a join, or vice versa, and the aggregation math quietly broke your metrics.

Understanding when Tableau blends data versus joins it — and what each method does to your row counts and aggregations — is one of the most practical skills you can develop as a Tableau user.

What You'll Learn

• The mechanical difference between a join and a blend in Tableau
• Why blends produce aggregated results that can inflate or suppress your metrics
• How to spot which relationship type is active in your workbook
• When to use each approach deliberately
• Concrete steps to fix a dashboard that's showing the wrong numbers

Prerequisites

This article assumes you're comfortable building basic Tableau views and connecting to at least one data source. You don't need to be a SQL expert, but knowing what a SQL JOIN does at a conceptual level will help the analogies land.

How Joining Works in Tableau

A join in Tableau works the same way a SQL join does: Tableau combines rows from two tables before the data reaches your view. The result is a single, flat table where every row reflects matched records from both sides.

When you open a data source and drag a second table onto the canvas in the data source editor, Tableau creates a join. By default it suggests an inner join, but you can switch to left, right, or full outer depending on what you need.

-- What Tableau is doing behind the scenes for a left join
SELECT
  orders.order_id,
  orders.revenue,
  customers.region
FROM orders
LEFT JOIN customers
  ON orders.customer_id = customers.customer_id

The critical point: the join happens at the row level, before any aggregation. If a single order matches three customer records (a data quality issue, but it happens), you'll get three rows for that order — and your SUM(Revenue) will count that order three times.

How Blending Works in Tableau

Blending is a completely different mechanism. Instead of merging tables before aggregation, Tableau queries each data source independently and then combines the aggregated results in the view.

The primary data source returns its aggregated values first. Then Tableau runs a separate query against the secondary source and joins the aggregated results on the linking field. Think of it as a left join of summary tables, not raw rows.

Blending activates automatically when you place fields from two different data sources in the same view. The chain icon next to the linking field in the secondary source tells you blending is in effect.

A blend is always a left join of aggregated data. There is no option for an inner, right, or full outer blend. If a value exists in the secondary source but not the primary, it will never appear.

Why This Causes Metric Errors

The difference in aggregation timing is where things go wrong. Here are the two most common failure patterns.

Inflated metrics from a join

Imagine you have an orders table and a promotions table. One order can be associated with multiple promotions. When you join them, each promotion generates an extra row for the same order.

If you then do SUM(Revenue), Tableau adds up every row — including duplicates. Your revenue figure looks healthy. It's actually counting the same sale multiple times. This is called a fan-out and it's one of the most dangerous silent errors in analytics.

Suppressed metrics from a blend

Now flip it. You blend sales (primary) with targets (secondary) on Region. If your secondary source has a target for