Skip to main content
Meytal Dahan
Back to insights

Designing a MarTech Dashboard: How Do You Present Real-Time Analytics That Marketers Can Actually Act On?

Product managers working on MarTech systems face a unique dilemma: their users — marketing managers, data analysts, and campaign managers — need an enormous amount of information, but they also need the ability to make decisions fast. A dashboard that shows everything at once overwhelms the user; a dashboard that hides important information forces them to go hunting for it. Striking the balance between these two extremes is critical. In the campaign management system project, the product breakthrough was built on the principle of "Insights Before Numbers." Instead of presenting the user with rows of numbers and expecting them to draw their own conclusions, the system surfaces analyzed insights front and center on the dashboard. "Your Facebook campaign dropped 15% this week," "Your Google Ads budget is approaching its limit," "The new audience you added on Monday is performing 2.3x better than the previous one." The numbers are still available — but they support the insight rather than replace it. On top of that, the system was designed with Action Buttons attached to every insight. Saw that campaign performance dropped? One button to dig deeper. Another button to raise the budget for a high-performing audience. This guidance turns the dashboard from a "source of information" into an "action system." For product managers in MarTech, AdTech, or any analytics-driven system, the insight is this: marketers don't want more data — they want more insights. Design your dashboard so it shows "what to do now" before "what happened." That's the difference between a tool people use once a month and a tool they use every day.

Get in touch

Have a project in mind?

Drop a line. Meytalyav@gmail.com

Related articles

Marketing & Campaign Analytics
Product ManagersUser Research

Researching the Marketer, Not Just the Metric

In analytics products, users don't want data. They want to know if it's working and what to do next. Every time I run discovery for a marketing dashboard, the same thing surfaces: people get raw numbers before meaning, so they burn energy interpreting instead of acting. That single insight reframes the roadmap, from "more charts" to "faster decisions." Research isn't a quote deck. It's the thing that tells your PM what NOT to build.

Read
Marketing & Campaign Analytics
Engineering Leaders

Data Visualization in MarTech: How Do You Design Charts That Don't Collapse Under Massive Data?

Engineering leaders on MarTech systems: dashboards with real-time visualizations are a performance nightmare. In our campaign management system project we built "Skeleton Loading" — every chart loads separately, a fast experience even under load. Every visualization passed through a "Performance Impact" filter. Design + performance = a system that works in production.

Read
Marketing & Campaign Analytics
Project ManagersDelivery & Handoff to Development

A Handoff the Team Can Actually Build From

A handoff isn't the moment you share a file. It's a quality gate. If I only hand over the happy path, the team builds the happy path, and every loading, empty, and error state becomes a clarification ticket mid-sprint. So I spec the states, the interactions, the shared-vs-specific components, all on existing Design System tokens. A good handoff makes delivery assembly, not archaeology.

Read
Meytal Dahan

About

Making complicated into easy for users.

Senior product designer with a decade of work across complex systems - financial risk platforms, legal operations, healthcare apps, manufacturing tooling and insurance portals. The common thread is depth: products where the data is rich, the users are expert, and the interface has to disappear into the work.