How to build a marketing dashboard: connecting GA4, ad platforms, and CRM data
Max Musing
Max MusingFounder and CEO of Basedash
· June 26, 2026

Max Musing
Max MusingFounder and CEO of Basedash
· June 26, 2026

A marketing dashboard is only as good as the data behind it, and marketing data is the hardest kind to assemble. Ad spend lives in Google Ads and Meta, traffic and conversions live in GA4, leads and pipeline live in your CRM, and revenue lives in your billing system. Each platform reports only its own slice, and most of them quietly over-claim credit for the same conversions. The real work of a marketing dashboard is not picking charts. It is unifying these sources and agreeing on a single set of numbers.
This guide is for marketing ops, growth, and analytics leads who want one dashboard that answers how much was spent, what it produced, and whether the spend is paying back. It covers the data sources you have to connect, how to wire them together, the attribution and identity problems that make the numbers disagree, the metrics worth defining, and the tools that fit different stages.
A sales dashboard pulls mostly from one system (the CRM). A SaaS revenue dashboard joins two or three. A marketing dashboard routinely spans five or more, and the platforms actively disagree:
The practical consequence: you cannot build a trustworthy marketing dashboard by pasting each platform’s native numbers side by side. You have to bring the data into one place and define the metrics yourself.
Before building anything, map the sources and what each one is the authority for. A clean map prevents the most common failure, which is pulling the same metric from two systems and getting two answers.
| Source | What it is the authority for | Typical connection method |
|---|---|---|
| Google Ads, Meta Ads, LinkedIn Ads | Spend, impressions, clicks, campaign and ad metadata | Platform API or managed connector |
| GA4 | Sessions, traffic source, on-site conversions, engagement | BigQuery export or GA4 Data API |
| CRM (HubSpot, Salesforce) | Leads, MQLs, opportunities, pipeline, closed revenue | Managed connector to a warehouse |
| Billing (Stripe, Chargebee) | Actual paid revenue, subscriptions, refunds | Managed connector to a warehouse |
| Product analytics or app database | Signups, activation, trial-to-paid | Direct connection or warehouse sync |
The dividing line that keeps a dashboard honest: ad platforms own spend, your CRM and billing system own outcome, and GA4 owns on-site behavior between the two. When a metric needs both spend and outcome, like cost per customer, it has to be computed across sources rather than read from one.
There are three ways to bring this data together, and the right one depends on how many sources you have and whether you already run a warehouse. These map directly to the patterns covered in how BI tools combine data from multiple sources.
A BI tool connects to each platform’s API and queries it live. This is the fastest way to start and fine for a small number of sources and modest volumes. It breaks down when you need to join across platforms, because most ad and CRM APIs are not built for arbitrary joins, and live API calls hit rate limits and latency on every dashboard load.
Use direct connections when you have one or two sources, low volume, and no need to join spend against revenue yet.
The durable pattern is to sync every source into a warehouse (BigQuery, Snowflake, Postgres, or similar) on a schedule, model the raw tables into clean facts, and point the dashboard at the modeled tables. Managed connectors like Fivetran, Airbyte, or Stitch handle the extraction. GA4 has a native BigQuery export that lands event-level data, which is the cleanest way to get GA4 into a warehouse.
This is the right pattern once you need to join spend to revenue, want consistent definitions across teams, or have more than two or three sources. If you are not sure whether you have outgrown direct connections, the signals that you need a warehouse apply here too.
Some BI tools can blend results from multiple connected sources without a warehouse, joining them at query time on a shared key like date or campaign ID. This avoids standing up a warehouse but is fragile for marketing data, where the join keys (campaign names, UTM values) are messy and inconsistent across platforms. Treat blending as a stopgap, not the foundation.
This is the part that makes marketing data different from every other dashboard, and the part most guides skip. Two technical problems sit underneath every efficiency metric.
A person clicks a Meta ad, lands on the site (GA4 records a session), fills out a form (CRM creates a lead), and pays three weeks later (billing records revenue). To attribute that revenue back to the Meta campaign, you need to connect four records that live in four systems and share no common ID by default.
The connective tissue is UTM parameters and click IDs. Tag every campaign URL with consistent utm_source, utm_medium, and utm_campaign values, and capture the platform click IDs (gclid for Google, fbclid for Meta) on the landing page. Store those values on the lead record in the CRM so the campaign that produced a lead travels with it all the way to closed revenue. Without this, spend and revenue can never be joined and your dashboard can only ever show platform-reported numbers.
Once identity is stitched, you still have to decide how credit is assigned when a customer touches several channels. The common models:
For most teams, pick last-touch or first-touch as the dashboard default, label it clearly, and treat multi-touch attribution as a separate analysis rather than the headline number. The worst outcome is a dashboard where nobody knows which model produced the numbers.
Decide for every metric whether it comes from a platform’s own reporting or from your unified data, and never mix the two on the same chart.
A marketing dashboard should lead with measured metrics for anything that drives budget decisions, and clearly tag any platform-reported figures as “as reported by [platform].” Blended metrics, which divide total spend by total measured outcomes, sidestep the attribution argument entirely and are the most defensible numbers on the page.
Keep the headline set small and define each one in one place. The table below shows the metrics that earn space on most marketing dashboards and where each comes from.
| Metric | Definition | Sources required |
|---|---|---|
| Total spend | Sum of spend across all paid channels | Ad platforms |
| Blended CAC | Total spend / new customers acquired in the period | Ad platforms + billing |
| Channel CAC | Channel spend / customers attributed to that channel | Ad platforms + CRM/billing + attribution |
| ROAS | Revenue attributed to spend / spend | Ad platforms + billing + attribution |
| CAC payback | Blended CAC / monthly gross margin per customer | Billing + finance |
| Lead-to-customer rate | Customers / leads in a cohort | CRM + billing |
| Cost per lead (CPL) | Spend / leads | Ad platforms + CRM |
| Pipeline contribution | Pipeline value sourced by marketing | CRM |
Two definitions deserve special care. Blended CAC divides all acquisition spend by all new customers, with no attribution required, which makes it the most trustworthy efficiency number and a good top-of-dashboard KPI. CAC payback tells you how many months of margin it takes to recover acquisition cost, and it requires margin data from finance, so confirm the margin assumption with whoever owns the model before publishing it.
Marketing data has a quirk that trips up dashboards built like operational dashboards: it is not final when it first arrives.
Real-time refresh is rarely worth the cost for a marketing dashboard, because the underlying attribution is not real-time anyway. A scheduled daily or hourly sync is almost always the right tradeoff.
The right tool depends on whether you have a warehouse, who consumes the dashboard, and how much you want to centralize definitions. The patterns below are the ones marketing teams choose most often.
| Tool | Best for | Marketing data fit | Notes |
|---|---|---|---|
| Looker Studio | Small teams reporting straight from GA4 and Google Ads | Strong inside the Google stack, weaker across non-Google sources | Free, native Google connectors, joins across sources are limited |
| Power BI | Microsoft-stack teams with a warehouse | Strong once data is in a warehouse | Many connectors, heavier authoring model |
| Tableau | Enterprise teams with dedicated BI staff | Strong on visualization, needs modeled data | Best-in-class charts, heavyweight to maintain |
| A dedicated marketing platform (for example a reporting tool that ingests ad and CRM data) | Teams that want pre-built ad connectors and templates | Purpose-built for channel reporting | Fast for channel views, less flexible for custom revenue joins |
| Basedash | Startup and lean marketing teams that want fast, AI-assisted dashboards | Works on a warehouse or direct via 750+ connectors | Natural-language queries, governed metric definitions, no separate BI stack required |
For a full evaluation by tool, see our comparison of marketing analytics tools. If your marketing dashboard needs to sit next to a sales view, the HubSpot analytics dashboard guide covers the CRM side in detail.
For most growth teams, a single screen organized top-down works well:
Resist adding more. The fastest way to lose trust in a marketing dashboard is to fill it with platform-reported vanity metrics that contradict the measured numbers above them.
Use this before you ship:
What is the difference between a marketing dashboard and a sales dashboard?
A marketing dashboard tracks spend efficiency and top-of-funnel performance: spend, CAC, ROAS, lead volume, and channel mix. A sales dashboard tracks pipeline and deal execution: open pipeline, stage conversion, win rate, and rep performance. They share a few numbers (leads, MQLs) but answer different questions, so most teams build them separately and align on a common header.
Why don’t the numbers in my ad platforms match GA4?
Because each platform uses a different attribution model and window. Ad platforms count conversions they influenced within their own lookback period, GA4 deduplicates across channels with its own model, and none of them see your final billed revenue. The fix is to bring the data into one place and define the metrics yourself rather than trusting any single platform’s view.
Do I need a data warehouse to build a marketing dashboard?
Not to start. One or two sources at low volume can run on direct connections. You need a warehouse once you want to join spend to revenue across platforms, keep consistent definitions across teams, or handle more than two or three sources. A managed connector plus a warehouse is the durable pattern most teams settle on.
What is blended CAC and why is it more trustworthy?
Blended CAC is total acquisition spend divided by total new customers in a period, with no attribution required. Because it does not depend on assigning credit to specific channels, it sidesteps the attribution disagreements that make channel-level CAC contentious. It is the most defensible efficiency number and a good top-of-dashboard KPI, even though it cannot tell you which channel to scale.
How fresh does marketing data need to be?
Daily is enough for most marketing decisions. Attribution backfills for days after spend happens, so real-time refresh rarely changes a decision and adds cost and complexity. Set a scheduled refresh, show a “data through” timestamp, and mark recent periods as provisional.
A marketing dashboard does not need to be elaborate. It needs the sources mapped correctly, identity stitched across the funnel, one attribution model chosen and labeled, and a small set of measured metrics that the marketing and finance teams both agree on. Get that foundation right and the charts on top almost build themselves.
Written by

Founder and CEO of Basedash
Max Musing is the founder and CEO of Basedash, an AI-native business intelligence platform designed to help teams explore analytics and build dashboards without writing SQL. His work focuses on applying large language models to structured data systems, improving query reliability, and building governed analytics workflows for production environments.
Basedash lets you build charts, dashboards, and reports in seconds using all your data.