Related terms

Data visualization is not decoration. Edward Tufte's data-ink ratio principle^[1] argues that every pixel should encode information — gradients, 3D effects, and decorative icons are chart junk that competes with the signal your media buyer needs in a five-second scan.

William Cleveland and Robert McGill's landmark perception study ranked how accurately humans decode visual encodings^[2]. Position along a common scale (bar length, aligned points on a line) ranks highest. Angle (pie slices) and area (bubble size) rank far lower. That hierarchy maps directly to marketing dashboards:

The Chart Selection Matrix

Before opening Looker, Triple Whale, or Northbeam, name the analytics question — not the metric name. "I need a ROAS chart" is the wrong starting point. "I need to see whether efficiency trended over the last twelve weeks" is the right one.

Use the tabs above to see how each question type maps to a chart family with live examples. The poster below is the same framework at a glance — print it, pin it in Slack, or keep it next to your BI tool. It covers five common chart decisions; the interactive explorer adds cohort heatmaps as the sixth dashboard pattern.

Quick-reference matrix

Time Series: The Monday Standup Chart

Line charts are the default for weekly business reviews — when done correctly. Plot MER (blended), platform-reported ROAS, and total spend on one chart with event annotations. For encoding rules, see the line chart glossary entry.

Rules that survive executive scrutiny:

• Start Y-axis at zero for absolute metrics (spend, revenue). Truncated axes exaggerate small swings and trigger false alarms.
• For ratio metrics (ROAS, CTR) where the floor is not zero, a truncated axis is acceptable if labeled clearly.
• Annotate events: creative refresh dates, budget reallocation, platform outages, promotional periods.
• Limit to 3–4 lines per chart. More lines create spaghetti nobody reads.

Common mistake: Plotting platform-reported ROAS and MER on the same chart without noting that MER includes organic revenue. The divergence is expected, not a bug. Our MER vs ROAS vs nMER article explains when each metric belongs on a dashboard.

Visualizing Creative Performance

Video ads generate second-by-second retention data that no summary stat can replace. A 32% thumbstop rate tells you the hook worked; it does not tell you viewers cliffed at second 14.

Retention curve diagnosis patterns

Retention curves compress thousands of impressions into a single diagnostic read. The shape matters more than any single summary stat — a high thumbstop with a cliff at 14s is a pacing problem, not a hook problem.

Compare against our hook rate benchmark and ThruPlay rate benchmark when diagnosing hook vs hold issues.

Overlay multiple variants on one chart when comparing creative tests — but cap at three curves. More than three and the chart becomes unreadable in a standup. Use direct labels at the 3s, 15s, and end markers rather than a legend alone; legends force eye travel that five-second scans cannot afford.

Use our Video Drop-off Calculator to generate retention data from your own exports.

Creative variant comparison

Grouped bar charts with confidence intervals are the right readout for A/B tests. Rules:

• One cluster per variant; bars for primary KPI (CPA, thumbstop, ThruPlay).
• Sort by primary KPI, not test order.
• Include sample size in labels — 45% thumbstop on 800 impressions is not comparable to 32% on 80,000.
• Do not declare winners with overlapping error bars.

For multivariate creative tests, a feature × metric heatmap supports the creative feature model approach — but keep the primary stakeholder read simple.

Funnels and Cohort Charts

Funnel charts answer: where do users drop between sequential stages? Impressions → clicks → landing views → add-to-cart → purchase. Label absolute counts at each stage, not just conversion rates.

A stage showing 2.1% click-to-purchase CVR without click volume is a classic trap: if top-of-funnel clicks fell 40% week-over-week, the rate can look stable while the business is shrinking. Always pair rates with the numerator:

Cohort charts answer a different question: how do groups acquired in different periods behave over time? A heatmap (rows = acquisition month, columns = months since acquisition, color = repeat rate) reveals retention quality shifts that blended metrics mask. If January cohorts repeat at 38% in month 3 but June cohorts repeat at 24%, your blended repeat rate can look flat while acquisition quality is deteriorating.

How to read a cohort heatmap in a weekly review:

• Rows = when customers were acquired (January 2026 cohort, February 2026 cohort, …)
• Columns = periods since acquisition (month 0, month 1, month 2, …)
• Color = the metric you care about (repeat purchase rate, LTV contribution, subscription renewal)
• Cell labels = the actual percentage — do not rely on color alone; color scales are hard to decode precisely and fail accessibility checks without text

Watch for diagonal patterns: a column that is uniformly darker across all rows signals a calendar effect (promotion, platform outage, seasonality), not a cohort-quality shift. A row that fades left-to-right while other rows stay bright signals deteriorating acquisition quality for that vintage.

Dual Y-Axes and Small Multiples

Dual Y-axes are tempting when you want spend and MER on one slide. The problem is scale manipulation: readers infer correlation from line crossings that may be meaningless. Stephen Few's guidance is blunt — dual scales make it easy to tell any story you want^[3].

Use dual Y-axes only when:

• Both metrics share the same time axis
• The relationship between the two lines is the explicit point of the chart
• Both scales are labeled clearly and cannot be merged onto one axis

Prefer small multiples when metrics are related but not directly comparable — three aligned line charts (MER, spend, CVR) with shared X-axis but independent Y-scales communicate more honestly than one overlay. The extra vertical space is cheaper than a misallocated budget decision.

Weighted vs Unweighted Rate Averages

Averaging CTR across campaigns is one of the most common silent errors in marketing dashboards. Campaign A: 5.0% CTR on 2,000 impressions. Campaign B: 2.0% CTR on 80,000 impressions. The unweighted average is 3.5%. The impression-weighted average is 2.07% — barely above Campaign B alone.

Always show volume next to rate in chart labels, tooltips, and tables. If you cannot weight the aggregate, show the distribution (histogram or box plot) instead of a single summary bar.

Where this shows up in real dashboards:

• Blended CTR across campaigns with 100× impression variance
• Average CPA across ad sets with different conversion volumes
• Thumbstop rate averaged across variants without impression weighting
• Platform-reported ROAS rolled up without spend weighting

The fix is not always a weighted formula in the BI tool — sometimes the honest read is a distribution chart that shows whether your "average" hides a bimodal split (two clusters of high and low performers).

Part-to-Whole: Why Pie Charts Fail Marketing Dashboards

Pie charts are seductive because they look like "share." Research consistently shows humans compare angles poorly but compare bar lengths accurately^[4].

When pie charts are acceptable: 2–4 slices summing to 100%, and precise comparison is not required — e.g., "paid vs organic revenue share this month." For channel mix, budget allocation, or attribution splits with 5+ categories, use a sorted horizontal bar chart.

Seven Dashboard Mistakes That Hide Signal

Truncated axes are especially dangerous on CPA and efficiency metrics where a $3 swing can look like a 40% crisis when the Y-axis starts at $44 instead of zero.

Stephen Few's dashboard design principles reinforce Tufte: reduce non-data ink, use consistent color semantics, and design for the decision the viewer must make — not for the data you have^[5].

Chart Polish Standards for Marketing Teams

Treat chart styling as analysis quality, not decoration. A correct chart that is hard to read will still produce bad decisions in a weekly growth meeting.

• One semantic legend entry per measure. If a filled area and a line encode the same metric, label the line and keep the fill out of the legend. Duplicate legend entries make teams hunt for a difference that does not exist.
• Prefer horizontal bars for long campaign or creative names. Rotated labels are a last resort; they waste vertical space and make screenshots harder to scan in Slack.
• Put benchmark labels where they do not fight the axes. Reference lines should be annotated outside dense tick bands on desktop and simplified on mobile.
• Do not let decorative shapes cross the data labels. Funnel and waterfall visuals should keep labels on stable cards or rows, with proportional encoding as a separate layer.
• Mobile charts need a separate design pass. Hiding cramped labels is acceptable when the exact values are available in a tooltip, table, or adjacent text; clipped labels are not.

These standards are deliberately conservative: the point is to make the trade-off obvious before anyone asks a data scientist to explain the screenshot.

Building Dashboards That Ship Decisions

Dashboards exist to change behavior — reallocate budget, pause a creative, escalate an incrementality test. If the chart type does not match the decision, the dashboard becomes wallpaper.

Tooling to prototype before you wire live data

Explore per-chart definitions in our Charts Glossary — each entry covers when to use the type and common marketing use cases.

Key Takeaways

Further reading

• Marketing Data Visualization Guide — quick-reference condensed version (start here)
• Data Visualization topic hub — chart glossary, tools, and related articles
• Data Storytelling: Transform Metrics into Creative Insights
• Statistical Noise in Marketing

A 45% thumbstop on 800 impressions is not comparable to 32% on 80,000 — label sample sizes directly on the chart.