Short answer: A marketing dashboard for leads, pipeline and revenue follows one group of leads from ad spend to valid enquiries, qualified leads, opportunities and won revenue, by channel and campaign. It needs about 15 written KPI definitions, one join key (date plus normalised source, medium and campaign) shared by your ad platforms and CRM, a cohort view so spend is compared with the revenue it produced, and a data-quality panel. In Data Studio (Google's new name for Looker Studio) that usually means GA4 and Google Ads connectors, plus a CRM export through Google Sheets or BigQuery.
Need this done for you? GrowthSparx offers a fixed-scope lead tracking and attribution setup: GA4, Google Ads, Meta, WhatsApp, calls and CRM wired into one dashboard, usually live in 2–3 weeks.
What should a marketing dashboard for leads, pipeline and revenue show?
It should answer one question for each budget line: for every ₹1 spent, how much qualified pipeline and won revenue came back, and how fast? Platform dashboards stop at the lead. Google Ads reports conversions, Meta reports form fills, GA4 reports key events. None of them knows that 40% of last month's Meta leads gave wrong numbers or that one Google campaign produced most of the closed deals. That knowledge sits in your CRM, so the dashboard's job is to put spend and CRM outcomes on the same row.
We organise every leads dashboard into five layers, read left to right:
| Layer | Question it answers | Core measures | Main source |
|---|---|---|---|
| Acquisition | What did we buy? | Spend, impressions, clicks, CPC | Google Ads, Meta, LinkedIn |
| Capture | How many real people enquired? | Raw leads, valid leads, duplicate rate, CPL | GA4 + CRM |
| Quality | Were they the right people? | Qualified leads, cost per qualified lead, rejection reasons | CRM |
| Velocity | Did sales act on them? | Speed to first contact, contact rate, days in stage | CRM activity log |
| Value | What came back? | Pipeline value, wins, revenue, cost per win, return on spend | CRM / billing |
If you can only build one layer this month, build Quality. Cost per qualified lead changes budget decisions far more often than CPL does.
Which KPIs belong on the dashboard, and how are they defined?
Write these definitions down before anyone opens a dashboard tool. Most dashboard arguments are really definition arguments: sales counts a lead once per person, marketing counts once per form fill, and both numbers are "right".
| KPI | Formula | Source of truth | Watch for |
|---|---|---|---|
| Spend | Media cost, excluding GST and agency fee (show fee separately) | Ad platforms | Mixing GST-inclusive invoices with platform cost |
| Raw leads | Form submits, instant-form leads, connected calls and WhatsApp chats, one per person per 30 days | CRM | Counting thank-you page reloads |
| Valid lead rate | Leads with a reachable, genuine contact ÷ raw leads | CRM disposition | "Not yet called" counted as invalid |
| CPL | Spend ÷ raw leads | Calculated | Optimising this alone |
| Qualified leads (MQL/SQL) | Leads meeting your written criteria (budget, need, location, timeline) | CRM stage | Criteria changing mid-quarter |
| Cost per qualified lead | Spend ÷ qualified leads | Calculated | Small numbers; read monthly, not daily |
| Speed to first contact | Median minutes from lead created to first call or message | CRM activity log | Averages hiding a few 3-day gaps; use median and 90th percentile |
| Contact rate | Leads reached within 48 hours ÷ valid leads | CRM | Different rules across sales reps |
| Lead-to-opportunity rate | Opportunities ÷ qualified leads | CRM | Opportunities created without a source |
| Pipeline value | Sum of open opportunity value, unweighted and stage-weighted | CRM | Stale deals never closed out |
| Win rate | Won ÷ (won + lost) opportunities in the cohort | CRM | Including deals still open |
| Revenue | Invoiced or collected value of won deals | Billing / finance | Booking value vs collected value |
| Cost per win (CAC) | Spend (+ fees, if you choose) ÷ won customers | Calculated | Stating which costs are included |
| Return on ad spend | Revenue ÷ spend | Calculated | Use gross margin for a true break-even view |
| Sales cycle | Median days from lead created to won | CRM | Judging new campaigns before one cycle has passed |
For the stage definitions themselves, use the framework in our lead qualification guide; for the GA4 side of lead counting, see GA4 lead generation tracking. Note that GA4 now calls conversions key events: label dashboard fields so nobody confuses a GA4 key event with a CRM-qualified lead.
What does a sample leads-to-revenue metric table look like?
Worked example (illustrative numbers, not client data): a Noida B2B services firm, leads created in July, outcomes read in October so most deals have had time to close.
| Channel | Spend | Raw leads | Valid | Qualified | Opps | Won | Revenue |
|---|---|---|---|---|---|---|---|
| Google Search | ₹3,00,000 | 400 | 340 | 120 | 40 | 10 | ₹25,00,000 |
| Meta lead forms | ₹2,00,000 | 800 | 560 | 90 | 22 | 4 | ₹9,00,000 |
| Organic search | – | 150 | 135 | 60 | 20 | 6 | ₹15,00,000 |
| Referral | – | 40 | 40 | 25 | 12 | 5 | ₹14,00,000 |
The derived row is where decisions come from:
| Channel | CPL | Valid rate | Cost per qualified lead | Cost per win | Revenue ÷ spend |
|---|---|---|---|---|---|
| Google Search | ₹750 | 85% | ₹2,500 | ₹30,000 | 8.3x |
| Meta lead forms | ₹250 | 70% | ₹2,222 | ₹50,000 | 4.5x |
Read it the way a CFO would. On CPL, Meta looks three times cheaper. On cost per qualified lead the two are close. On cost per win, Google is 40% cheaper, because its qualified leads became opportunities more often (33% against 24%). A dashboard that stops at CPL would move budget the wrong way. Our lead funnel calculator does the same arithmetic for your own stage rates.
How should the dashboard pages be laid out?
Five pages cover most businesses. Keep each one answerable in under a minute.
- Executive summary. Six scorecards with the previous period for comparison: spend, qualified leads, cost per qualified lead, pipeline created, revenue won, cost per win. One line chart of qualified leads by week. No tables.
- Channel and campaign table. The two tables above, with filters for date cohort, channel, campaign and city. Sort by cost per qualified lead, not by spend.
- Funnel by cohort. Leads created per month as rows, and how many reached each stage as columns. This is the page that shows whether last quarter's leads are still converting.
- Sales velocity. Median speed to first contact by rep and by hour of day, contact rate, and leads with no activity after 24 hours. Most "bad lead" complaints are settled here.
- Data quality. The checks in the panel section below. Put it on every review agenda.
Segment by landing page, device and city only when each segment has enough leads to read. A campaign with 6 qualified leads cannot support a five-way breakdown.
Which data sources do you connect in Data Studio (Looker Studio)?
Google renamed Looker Studio to Data Studio on 16 April 2026; the product and connectors are the same. A typical lead-generation build uses four sources:
| Source | Connector | Default refresh | Notes |
|---|---|---|---|
| GA4 | Google Analytics (native) | Every 12 hours (1 or 4 hours selectable) | Needs at least Read & Analyze access; GA4 segments and comparisons are not available through the connector |
| Google Ads | Google Ads (native) | Every 12 hours, fixed | Pulls cost, clicks and conversions by campaign |
| Meta, LinkedIn | No native Google connector; use a partner connector or a scheduled export to Sheets | Depends on method | Keep the same campaign naming as your UTMs |
| CRM | Google Sheets export, or BigQuery for larger volumes | Sheets every 15 minutes; BigQuery every 1 to 12 hours (down to 1 minute selectable) | One row per lead with source fields and stage dates |
Refresh rates are from Google's data freshness documentation, and connector rules from the Google Analytics connector page. Two practical limits matter:
- GA4 quotas. GA4-backed reports draw on Data API quotas: 200,000 core tokens per property per day, 40,000 per hour, and 14,000 per project per property per hour on a standard property. A dashboard with 30 GA4 charts opened by a whole sales team on Monday morning can hit them. Fewer GA4 charts, extracted data or a BigQuery export avoid the errors.
- GA4 latency. Google says daily GA4 data typically takes about 12 hours to process on standard properties, and some data can arrive up to 7 days late. Do not judge yesterday from GA4 at 10 a.m.
The CRM export is the source that matters most. It should hold, for every lead: lead ID, created date, first-source fields (UTM source, medium, campaign, click ID), current stage, the date each stage was reached, rejection reason, owner, first-contact timestamp, deal value and won date. Our CRM revenue attribution guide covers how to capture and freeze those source fields.
How do you join ad spend to CRM outcomes?
Spend lives in ad platforms by campaign and day. Outcomes live in the CRM by lead. To put them on one row you need a shared key, and the only practical one is date (or month) + campaign name, with source and medium where campaign names repeat.
- Enforce one naming convention. The campaign name in Google Ads must equal the
utm_campaigncaptured in the CRM, in lowercase, with no spaces. Our UTM parameters guide has a naming pattern you can copy. - Aggregate the CRM first. Group CRM rows to month × campaign before joining, so spend is not duplicated across every lead row.
- Blend. Data Studio blends allow up to five tables and support only equality join conditions, so the key must match exactly. Use a left outer join from spend to CRM, so campaigns with spend but zero leads stay visible.
- Above a few thousand leads a month, move the join to BigQuery or Sheets and point the dashboard at the finished table. Blends with many calculated fields become slow and hard to audit.
Should the dashboard use cohort dates or calendar dates?
Use both, labelled clearly. A calendar view counts everything that happened in October: October spend, October leads, October wins. But October's wins mostly came from August and September leads, so "October revenue ÷ October spend" mixes unrelated periods and swings wildly when you change budgets.
A cohort view groups by the lead's created month: July's spend, July's leads, and whatever those July leads have produced so far. It is the honest view for investment decisions, with one condition: a cohort is immature until a full sales cycle has passed. Show the median sales cycle next to each cohort and grey out cohorts younger than it. For a real estate developer with a 60–90 day cycle, the latest two months are always immature. For an ecommerce brand the cohort closes in days.
What goes in the data-quality panel?
A dashboard without quality signals invites false confidence. Show these six checks with a red/amber/green rule you agree internally (the thresholds below are our working defaults, not an industry standard):
| Check | Green | Red |
|---|---|---|
| Leads with no source captured | Under 5% | Over 15% |
| Leads with no owner after 1 hour | 0 | Any |
| Duplicate rate (same phone within 30 days) | Under 10% | Over 25% |
| Open leads with no activity for 7 days | Under 10% | Over 30% |
| Ad-platform leads vs CRM leads, same week | Within 10% | Gap over 25% |
| CRM won revenue vs finance invoices, last month | Reconciled | Not reconciled |
When a check goes red, run the matching section of our lead tracking audit checklist before changing any budget.
How often should you review it?
- Weekly (30 minutes, marketing + sales head): velocity page, valid-lead rate, rejection reasons, data-quality panel. Decide fixes to follow-up and targeting.
- Monthly (60 minutes, add the founder or finance): cost per qualified lead and cost per win by channel for mature cohorts. Decide budget moves.
- Quarterly: win rate, sales cycle and revenue by first source. Decide channel mix and whether definitions need updating.
Daily viewing is fine for spend pacing, but daily budget decisions on qualified-lead data mostly react to noise.
What are the most common dashboard mistakes?
- Platform conversions treated as leads. Google Ads and Meta both claim some of the same people. Count leads from the CRM, and show platform-reported conversions only as a diagnostic. Why the totals differ is covered in our attribution guide.
- Spend without fees and GST. Decide whether cost per win includes agency fees and taxes, write it on the page, and never change it silently.
- Last-touch only. Show first source and latest source side by side. Organic and referral leads often start a journey that a branded Google search finishes.
- No owner. Every metric needs a named person who explains movement. Without one, the dashboard becomes wallpaper.
- Too many charts. If a chart has not changed a decision in a quarter, remove it.
If you want this built on your own CRM and ad accounts, our performance marketing team sets up the tracking and dashboard before scaling spend.
Sources
- Data Studio release notes: Looker Studio rebranded as Data Studio, 16 April 2026.
- Data Studio: Manage data freshness: default refresh rates for Google Analytics, Google Ads, Sheets and BigQuery.
- Data Studio: Connect to Google Analytics: access requirement, quota errors, segments not supported.
- Data Studio: How blends work: up to five tables, join types, equality-only joins.
- Google Analytics Data API quotas: core token limits per property.
- GA4 Help: Data freshness: typical processing times and late-arriving data.
- GA4 Help: About key events: key event definition.