HubSpot Admin · Module 11 · Curriculum Capstone

Reports &
Dashboards

The measurement layer of your CRM — where every object, property, workflow, and pipeline you've built becomes visible, actionable, and improvable. Reports are the feedback loop that makes a CRM self-improving.

4 report types 8 essential reports Dashboard design Attribution models 3 case studies Curriculum capstone
Naveed Abbas profile photo
Naveed Abbas
CRM Administrator
Foundation · 01
What Is Reporting?

The measurement layer — turning CRM data into decisions. Everything you've configured generates data; reports reveal whether it's working.

Core definition

HubSpot Reporting is the system that converts your CRM activity data into answers to business questions. A Report is a saved query that answers one specific question. A Dashboard is a curated collection of reports for a specific audience. Together they are the feedback mechanism that tells you whether your CRM system is generating the right outcomes — and where to improve it.

Questions reports answer

Business questionReport that answers itUsed by
How many MQLs did marketing generate?Contacts by Lifecycle Stage over timeCMO, marketing team
What's our MQL → Customer conversion rate?Lifecycle stage funnel with conversion %CMO, RevOps
Which deals are at risk of slipping?Open deals by stage + last activity dateVP Sales
What's our weighted pipeline forecast?Deal forecast: Amount × ProbabilityCEO, CFO, VP Sales
Why are we losing deals?Closed Lost Reason breakdownVP Sales, RevOps
Which lead source generates the most revenue?Revenue by Original SourceCMO, RevOps
How fast do reps respond to inbound leads?First response time by repSales manager
Which customers are at risk of churning?Ticket volume + CSAT by customerCS manager
The capstone insight

Reporting is why everything else in this curriculum matters. The lifecycle stages, workflows, pipeline required fields, lead status reasons — all of it was building the data infrastructure that reporting depends on. Reports don't create insight from nothing. They surface what's already in your data. The quality of your reports is exactly proportional to the quality of your CRM configuration upstream.

Foundation · 02
Reporting Architecture

Three layers from raw data to executive insight — understanding the stack makes you a better admin.

LayerWhat it isWho configures itWhat it produces
Layer 1: CRM DataContact properties, deal properties, lifecycle stages, logged activities, form submissions, email eventsGenerated automatically by CRM activity + admin configurationsRaw data — the fuel for all reporting
Layer 2: ReportsSaved queries that pull, filter, group, and visualise CRM data to answer one specific questionAdmin + RevOps practitionersSingle visualisations answering individual business questions
Layer 3: DashboardsCurated collections of reports for a specific audience — showing multiple answers on one screenAdmin + RevOps practitionersOperational views tailored to specific decision-makers
Foundation · 03
The Four Report Types
Single-object report
Reports on one object type
Count of Contacts by Lifecycle Stage · Sum of Deal Amount by Owner · Tickets by Category this month. The most common report type — fast to build, highly readable.
Cross-object (multi-object) report
Joins two or more objects
"Contacts who became Customers this quarter with their associated Deal Amount, broken down by Original Source." Requires Marketing Hub Pro+ or Sales Hub Pro+.
Funnel report
Tracks stage-by-stage progression
Lifecycle stage conversion rates · Deal stage velocity · Support ticket resolution stages. Shows count at each stage and the % conversion between adjacent stages.
Attribution report
Traces which interactions drove conversions
Which pages, forms, campaigns, and emails contributed to contacts becoming Customers. Three models: First touch, Last touch, Linear. Marketing Hub Pro+ required.
Which to start with

For most HubSpot setups: build Single-object reports first (they're fastest and most reliable). Add Cross-object reports when you need to connect Marketing activity to Sales outcomes. Add Funnel reports for conversion analysis. Add Attribution reports last — they require the most data maturity to be accurate and meaningful.

Foundation · 04
Report Builder Anatomy

Every report in HubSpot is configured through five panels. Understanding each determines whether your report answers the right question.

Panel 1
Data source
Which object(s) to pull from. Contacts, Deals, Companies, Tickets, or a combination for multi-object.
ex: Contacts
Panel 2
Filters
Which records to include. Same AND/OR logic as lists. Date ranges, property values, status conditions.
ex: Close Date = this quarter AND Stage ≠ Closed Lost
Panel 3
Measures
What to count, sum, or average. Count of records, sum of a number property, average of a duration.
ex: Count of Contacts · Sum of Deal Amount
Panel 4
Dimensions
How to group or break down the results. By property value, by time period, by owner, by stage.
ex: By Lifecycle Stage · By Month · By Deal Owner
Panel 5
Visualisation
How to display the result. Table, bar, line, funnel, pie, donut. Choose based on the data structure.
ex: Bar chart comparing owners · Funnel for stages

Visualisation selection guide

VisualisationBest forAvoid when
TableDetailed data with multiple dimensions, when exact numbers matterAudience needs a quick visual — tables require reading
Bar chartComparing groups or categories (reps, stages, sources)More than 12 bars — becomes unreadable
Line chartTracking change over time — MQL count by month, revenue trendsFewer than 3 data points in time — not enough to show trend
Funnel chartStage-by-stage progression with visible drop-offNon-sequential data — a funnel implies progression
Pie chartProportional breakdown with 2–4 categoriesMore than 4 categories — slices become unreadable
Donut chartSame as pie, but better for centering a total countMore than 5 categories
Essential Reports · 05–12
The 8 Essential Reports

Every HubSpot portal needs these 8 reports before any other custom reporting work. Together they cover the full revenue operation across Marketing, Sales, and Customer Success.

📊
Report 01 — Lifecycle stage funnel
The foundational revenue pipeline health report
RevOpsFunnel reportContacts
Config
How to read it
SettingValue
Report typeFunnel (Contact funnel)
Data sourceContacts
Funnel stagesSubscriber → Lead → MQL → SQL → Opportunity → Customer
Date filterContact Create Date: Rolling last 90 days OR This quarter
VisualisationFunnel chart (shows count per stage + conversion % between stages)
Admin note

This report only works accurately if lifecycle stages are being set consistently by workflows — not manually or randomly. If you see 90% of contacts stuck at "Lead" with only a handful at MQL, it likely means your MQL promotion workflow is either broken or your MQL criteria are too strict. Investigate the data first.

Read this report as a health check on your entire funnel. A healthy funnel shows consistent conversion rates at each stage. A sudden drop between MQL and SQL (e.g. 80% MQL acceptance one quarter, 40% the next) signals a qualification friction point — could be wrong MQL criteria, SDR capacity issue, or a change in lead quality. This single report should open every marketing-sales alignment meeting.

📈
Report 02 — MQL-to-customer conversion rate
The primary marketing effectiveness metric
MarketingMulti-objectContacts + Deals
Config
How to read it
SettingValue
Report typeSingle-object or funnel (Contacts)
MeasureCount of contacts — filter to each stage separately, or use funnel
DimensionBy month or quarter
Date filterMQL Date: this year (requires MQL Date custom property)
VisualisationLine chart (showing trend over time) or Funnel (showing current conversion)
Requires

MQL Date, SQL Date, and Customer Date custom properties must be created and stamped by workflows. Without these date-stamp properties, you can only see current state — not historical trends.

This report connects marketing output (MQL count) to business outcome (Customer count). A high MQL count with a low Customer conversion rate means either marketing is generating the wrong leads or sales is failing to convert them. This data makes the Marketing-Sales alignment conversation productive because it's based on facts, not opinions.

💰
Report 03 — Weighted pipeline forecast
The number the CEO asks about every week
SalesSingle-objectDeals
Config
How to read it
SettingValue
Data sourceDeals
FiltersDeal Stage: not Closed Won, not Closed Lost · Close Date: this quarter
MeasuresSum of Amount (raw pipeline) · Sum of Weighted Amount (Amount × Probability)
DimensionBy Deal Stage OR by Deal Owner (run both versions)
VisualisationBar chart (by stage) or Table (by owner with both values shown)
Accuracy depends on

Probability percentages must be calibrated from historical close rates (not HubSpot defaults) and Deal Amounts must be required at the Qualified stage. If either condition is unmet, this report produces a meaningless number.

Raw pipeline (total amount) overstates expected revenue. Weighted pipeline (amount × stage probability) is the accurate forecast. Always build the report to show both — the gap between them reveals how much speculative pipeline exists. By owner view shows who is pulling their weight and who has under-sized or low-quality pipeline.

⏱️
Report 04 — Deal velocity (time in stage)
Where in the sales process are deals stalling?
SalesSingle-objectDeals
SettingValue
Data sourceDeals (Closed Won deals from last 12 months)
MeasuresAverage days in each stage using hs_date_entered_[stage] properties
DimensionBy Deal Stage (sequenced in pipeline order)
VisualisationBar chart (horizontal) — stages with longest average time stand out immediately
The bottleneck finder

The stage with the longest average time is your pipeline bottleneck. That's where coaching, enablement, or process improvement will have the highest impact. HubSpot auto-creates hs_date_entered_[stage] properties for every deal stage — no custom setup required to use these.

Report 05 — Closed lost reason breakdown
Why deals are being lost — the most actionable data in the CRM
SalesSingle-objectDeals
SettingValue
Data sourceDeals
FiltersDeal Stage = Closed Lost · Close Date: last 90 days
MeasureCount of Deals
DimensionBy Closed Lost Reason (required dropdown)
VisualisationBar chart sorted by count (most common reason at top)
What this report drives upstream

Price dominates → pricing strategy conversation. Competitor wins → competitive battle card. Wrong fit → ICP refinement. Timing → build the Bad Timing re-engagement workflow. No budget → add budget qualification earlier in discovery. One chart drives changes across Marketing, Sales, and Product.

🎯
Report 06 — Lead source revenue attribution
Which marketing channels generate the most customers and revenue
MarketingMulti-objectContacts + Deals
SettingValue
Data sourceDeals (with associated Contact data)
FiltersDeal Stage = Closed Won · Close Date: this year
MeasuresCount of Deals (customers) · Sum of Deal Amount (revenue)
DimensionBy Contact Original Source (or First touch source)
VisualisationBar chart sorted by revenue (not by count)
Sort by revenue, not count

A source that generates 100 leads but $10k revenue is less valuable than one generating 10 leads and $200k revenue. Sorting by revenue (not by lead count) reveals true ROI. This is how marketing justifies budget allocation.

👤
Report 07 — Rep activity dashboard
What each sales rep is actually doing — calls, emails, meetings, tasks
SalesSingle-objectActivities
SettingValue
Data sourceActivities (separate reports for Calls, Emails, Meetings)
FiltersActivity date: this week · Owner: all reps
MeasureCount of each activity type
DimensionBy Activity Owner (rep name)
VisualisationGrouped bar chart (one bar per rep, grouped by activity type)
The coaching separator

This report separates activity from outcome. A rep with low pipeline but high activity has a quality or process problem — coach on targeting and messaging. A rep with low activity has an effort problem — different management conversation entirely. Never have a pipeline review without this report on the table.

🎫
Report 08 — Customer success metrics
Ticket volume, resolution time, and customer health indicators
CSSingle-objectTickets
SettingValue
Data sourceTickets
FiltersTicket Create Date: this month · Associated Contact Lifecycle = Customer
MeasuresCount of tickets by status · Average hs_time_to_first_reply_ms · Average resolution time
DimensionBy Ticket Category OR by CS Owner
VisualisationTable + metric cards (total open, avg response time, avg resolution)
Revenue connection

Rising ticket volume from a specific category = product or process issue that drives churn. High tickets per customer per month = leading indicator of churn risk before the customer churns. These metrics connect directly to retention revenue — the CS dashboard should be on every revenue review.

Admin Setup · 13
Step-by-Step Setup

Building Report 01 — the Lifecycle Stage Funnel — step by step.

Path in HubSpot

Reports → Reports → Create report → Funnel reports → Contact funnel

  1. Choose report type — Select "Funnel" from the report type picker. Then "Contact funnel" for lifecycle stage analysis.
  2. Add funnel stages — HubSpot populates with lifecycle stage options. Select: Subscriber, Lead, MQL, SQL, Opportunity, Customer. Arrange in funnel order.
  3. Set date filter — Click "Add filter" → Contact Create Date → "is in the rolling 90 days." This keeps the report automatically current.
  4. Optional: segment filter — Add "Original Source = Organic Search" to see the funnel specifically for organic contacts. Or leave unfiltered for the full picture.
  5. Choose visualisation — Select "Funnel chart." The funnel view shows both count at each stage and conversion percentage between adjacent stages.
  6. Preview the report — Click "Apply" to see a live preview with your real data. Check: do the numbers make sense? Is MQL count significantly lower than Lead count (expected)? If MQL count is 0, your MQL promotion workflow may not be running.
  7. Name and save — "Lifecycle Stage Funnel — All Contacts — Rolling 90 Days." Click "Save" and add to your RevOps Operations dashboard.
  8. Repeat the pattern — Every other essential report follows the same five-panel structure: source → filters → measure → dimension → visualisation. Once you've built one, the rest follow naturally.
Admin Setup · 14
Dashboard Design

A dashboard is not a collection of reports — it's a curated decision-making tool for a specific audience.

Executive dashboard
Weekly

CEO · CFO · Board

  • Revenue vs target (closed won YTD)
  • Weighted pipeline forecast (this quarter)
  • MQL → Customer funnel conversion
  • NPS / CSAT score
  • Churn rate (if tracked)
Marketing dashboard
Daily

CMO · Marketing team

  • MQL count this month (vs last month)
  • Lead source breakdown by MQL count
  • Form conversion rates by form
  • Email campaign performance
  • Lifecycle stage funnel
Sales dashboard
Daily

VP Sales · Sales managers

  • Open pipeline by rep (weighted)
  • Deals closing this week
  • Stale deals (no activity 14+ days)
  • Rep activity this week (calls/emails)
  • Closed lost reasons last 90 days
RevOps dashboard
Daily

RevOps practitioner

  • Full funnel conversion rates
  • Pipeline velocity (time in stage)
  • Closed lost reason breakdown
  • Data quality monitors (blank stages, owners)
  • Forecast accuracy (predicted vs actual)

Dashboard design principles

  • 👥
    One audience per dashboard. The Marketing dashboard should not include rep activity metrics. The Sales dashboard should not include email campaign click rates. Design for the person reading it every morning.
  • 📊
    8–12 reports maximum. A 25-chart dashboard nobody reads is worse than a 6-chart dashboard everyone uses. Edit ruthlessly.
  • 📅
    Consistent time periods across all reports. If reports on the same dashboard use different time periods, the numbers won't be comparable. Pick one default per dashboard (this quarter, rolling 90 days) and stick to it.
  • 👑
    Lead with the headline number. The most important metric for that audience goes top-left. For Sales: weighted pipeline. For Marketing: MQL count. For CEO: revenue vs target.
  • 🔄
    Use rolling date ranges, not fixed. "Last 30 days" stays current automatically. A fixed date range requires manual updating and goes stale.
Admin Setup · 15
Data Quality Dependency

Reports are only as accurate as the data that feeds them. Every report traces back to a configuration decision earlier in this curriculum.

The most important concept in this module

A report that shows wrong numbers is almost never a report configuration problem. It's a data capture problem upstream. Before trusting any report, trace backward: what property does this report depend on? Is that property being set consistently? By a workflow? By a required field? Or by manual rep entry (unreliable)?

If this isn't configured This report breaks Risk level
MQL promotion workflow not built
Lifecycle funnel shows 0 MQLs forever
Critical
Amount not required at Qualified stage
Pipeline forecast includes $0 deals — overstates volume, understates value
Critical
Closed Lost Reason not required
Lost deal analysis has no data — most valuable diagnostic is blank
Critical
Date-stamp properties (MQL Date, Customer Date) not built
Can't show trends over time — only current state visible
High
Contact owner not assigned consistently
Rep-level reports are inaccurate or show "no owner" for large segments
High
Deal auto-set to Customer never enabled
Lifecycle → Customer data is stale — customers still show as SQL or Opportunity
High
Form fields mapped to wrong property types
Lead Source attribution is wrong — "unknown" inflated, paid channels understated
Medium
Lifecycle stages manually updated (no workflows)
Funnel data is inconsistent — reflects which reps remember to update, not reality
Medium
Admin Setup · 16
Attribution Models

How HubSpot credits marketing interactions for driving a conversion — three models, each telling a different story.

First touch
100% of credit goes to the very first marketing interaction the contact had with your company.
100%
Use for: Understanding what brings people in the door — top-of-funnel channel performance. Best for: awareness campaign measurement.
Last touch
100% of credit goes to the final marketing interaction before the contact converted (became a Customer).
100%
Use for: Understanding what closes the deal — bottom-of-funnel conversion drivers. Best for: identifying what content or campaigns directly precede purchase decisions.
Linear
Credit distributed equally across all marketing interactions — every touchpoint gets a proportional share.
25%
25%
25%
25%
Use for: Understanding the full buyer journey — which channels support conversion throughout the funnel, not just at entry or exit. Best for: long sales cycles with multiple touchpoints.
Admin truth about attribution

No attribution model is "correct" — they each answer a different question about the marketing funnel. Most mature RevOps teams look at all three and understand what each tells them. Start with Last touch attribution (it's the most intuitively understood by leadership) and add First touch when the CMO starts asking "but how do they find us in the first place?"

Applied Learning · 17
Real-World Example
The situation

A 25-person B2B SaaS company has been using HubSpot for 9 months. The CEO asks for a quarterly business review presentation and wants answers to: how many leads did we generate, what's our pipeline for next quarter, why are we losing deals, and what is our average sales cycle? The admin has 5 days to build the reporting system from scratch. Most of the data is there — but nobody has built any reports yet.

Day-by-day build plan

  • Day 1
    Data quality audit. Pulled every essential property and checked coverage: 94% of contacts have Lifecycle Stage set (good), 61% of deals have Amount populated (not good), 0% of Closed Lost deals have a Closed Lost Reason (nothing). Fixed: enabled Amount required at Qualified stage, enabled Closed Lost Reason required at Closed Lost. Can't retroactively fix old data, but future data will be clean.
  • Day 2
    Built date-stamp properties — MQL Date, SQL Date, Customer Date. Retroactively stamped Customer Date from deal close dates via import (had 2 years of deal history). This unlocked trend reporting.
  • Day 3
    Built the 8 essential reports. Lifecycle funnel, pipeline forecast (discovered 43% of deals had $0 amount — found and fixed), closed lost reason (blank — noted for future quarters), lead source breakdown, rep activity, deal velocity.
  • Day 4
    Built 3 dashboards — Executive (for QBR), Sales (for VP of Sales review), Marketing (for CMO). Each with 8 reports, rolling time periods, consistent formatting.
  • Day 5
    Prepared QBR narrative. Lead source data showed 68% of customers came from Organic Search — the company had been investing heavily in paid social with near-zero revenue attribution. This single data point redirected $15k/month in ad spend before the QBR presentation even ended.
RevOps outcome

The QBR was the first time the company had a data-backed conversation about its revenue operations. Three strategic decisions came directly from the dashboards: redirect paid social budget to organic content, require Closed Lost Reason to diagnose why they were losing deals (they assumed wrong fit — the data later showed it was mostly price), and hire a second SDR because the MQL → SQL conversion was healthy but volume was the constraint. All three decisions were data-driven and tied to specific reports. The admin's 5 days of work changed the direction of marketing budget allocation and headcount planning.

Applied Learning · 18
Three Case Studies
📊
Case 1 — The inflated pipeline problem
When reports reveal that pipeline volume is misleading
Pipeline reportingB2B SaaS
Discovery
Fix
Outcome
What the admin found

A VP of Sales was reporting $3.2M in "pipeline" to the board. The admin built the weighted pipeline forecast report for the first time and the number was $680k. The gap: 52% of open deals had no amount populated, so they contributed $0 to the weighted forecast. A further 30% were in Prospecting stage (5% probability). The actual weighted forecast of deals with real amounts was $680k — 79% less than the number being quoted to the board.

  • 1.
    Required Amount and Close Date at the Qualified stage. Going forward, no deal can progress to Qualified without both fields.
  • 2.
    Bulk-updated Amount on existing open deals via a rep-by-rep review session with the sales manager. Took 2 hours. Many "deals" turned out to be nothing — 18 were closed as Lost.
  • 3.
    Rebuilt the pipeline dashboard to show BOTH raw pipeline and weighted pipeline side by side. The gap between them is now a visual reminder that raw pipeline overstates expected revenue.
RevOps outcome

The board got an accurate picture for the first time. The quarter's actual closed revenue ($410k) was close to the weighted forecast ($680k at the start of quarter, accounting for deals that progressed and regressed). The VP of Sales initially objected to the lower number — "it makes us look worse." The admin's response: "It makes us look accurate, which lets us make better decisions about hiring, runway, and target-setting." The CEO agreed.

🔍
Case 2 — Lead source attribution changes marketing spend
When reporting reveals the wrong channels are getting the budget
AttributionB2B Tech
Discovery
Decision
Outcome
What the admin found

A B2B tech company was spending $45k/month on marketing. Budget breakdown: $20k Google Ads, $15k LinkedIn Ads, $8k content production, $2k tools. The marketing team reported monthly on lead volume — Google Ads generated 150 leads/month, LinkedIn 80 leads/month, organic 40 leads/month. The CMO was considering doubling LinkedIn spend. The admin built the lead source revenue attribution report for the first time — tracking Original Source to Closed Won revenue.

  • 1.
    Revenue attribution report revealed: Organic Search generated $380k in closed won revenue (40 leads × high conversion). Google Ads: $185k. LinkedIn Ads: $42k (80 leads, very low conversion rate — most were wrong industry).
  • 2.
    The CMO's plan to double LinkedIn spend was immediately reversed. LinkedIn was generating volume but almost no revenue.
  • 3.
    $10k/month was shifted from LinkedIn to content production (which fed organic search). Google Ads spend remained but with tighter targeting criteria.
RevOps outcome

Within 2 quarters: organic search leads grew from 40 to 85/month. Revenue from organic grew from $380k/quarter to $620k/quarter. The $10k/month shift in budget generated approximately $240k in additional quarterly revenue — a 2.4× return. The admin's single report changed how $120k/year of marketing budget was allocated. This is why revenue attribution reporting exists.

📈
Case 3 — Rep performance reporting reveals the real problem
When activity data separates effort from outcome
Sales reportingAgency
Discovery
Analysis
Outcome
What the admin found

A 6-rep sales team was missing quota by 23%. The VP of Sales assumed the MQL quality was poor — blaming Marketing for sending bad leads. The admin built the rep activity dashboard alongside the pipeline report for the first time. The activity data told a different story.

  • 1.
    Activity report showed: 4 of 6 reps were averaging 18–24 calls/week. Two reps (James and Sarah) were averaging 6 and 4 calls/week respectively. All 6 reps received the same volume of MQLs.
  • 2.
    Pipeline report showed: James and Sarah had 65% of the stale deals (no activity in 14+ days). The other 4 reps had healthy pipeline velocity.
  • 3.
    The MQL quality was not the problem. The team had 2 underperforming reps dragging the collective quota attainment number down. The other 4 were hitting or exceeding individual quota.
RevOps outcome

Marketing budget was not cut. MQL criteria were not changed. Instead, the VP of Sales had targeted performance conversations with James and Sarah based on activity data. James improved to 16 calls/week within 30 days; Sarah left the company within 60 days and was replaced. Team quota attainment went from 77% to 102% within 2 quarters. The admin's reports redirected a misdiagnosed Marketing problem to the correct Sales performance problem — saving a marketing channel restructuring that would have caused significant revenue damage.

Applied Learning · 19
Common Admin Mistakes
  • 01 — Building reports before fixing data quality
    A lifecycle funnel report that shows 94% of contacts at Lead with 3 at MQL is not a broken report — it's a broken workflow. Fix the MQL promotion workflow first. Then the report becomes accurate. Never spend time formatting a report built on bad data.
  • 02 — Reporting on current state instead of over time
    "How many MQLs do we have right now?" tells you nothing useful. "How many MQLs did we generate each month for the last 12 months?" reveals trends, seasonality, and growth trajectory. Always add a time dimension to operational metrics.
  • 03 — Using fixed date ranges instead of rolling dates
    A report with a fixed date range (Jan 1 – Dec 31 2024) becomes stale the moment the period ends. Use rolling dates (Last 30 days, This quarter, Rolling 90 days) — they stay current automatically and never require updating.
  • 04 — Too many reports on one dashboard
    A 25-chart dashboard that nobody reads is worse than a 6-chart dashboard everyone opens every morning. Limit dashboards to 8–12 reports. Every report on a dashboard must answer a question someone is genuinely asking.
  • 05 — Pie charts for data with more than 4 categories
    A pie chart with 10 slices representing 10 Closed Lost Reasons is unreadable. Use a bar chart. Pie charts are appropriate for 2–4 proportional categories with meaningful size differences. Nothing else.
  • 06 — Dashboards without named owners
    If nobody is responsible for a dashboard, nobody reads it. Every dashboard should have a named owner who reviews it on a defined cadence and is accountable for the business outcome it represents. Without ownership, dashboards become digital wallpaper.
Applied Learning · 20
Admin Best Practices
  • Start with the question, not the report. Never open the report builder without knowing the exact business question. "I want a report on contacts" is not a question. "Which lead source generates the most revenue per customer?" is a question. Every configuration decision flows from the question.
  • 🏷️
    Name reports like newspaper headlines. "Closed Lost Reason — Last 90 Days — By Rep" is better than "Deal Report 3." The name should tell you what question it answers, what time period it covers, and what breakdown it shows.
  • 🔍
    Always audit the upstream data before trusting a report. Trace backward from the report to the properties it depends on. Verify each property is being set consistently — by a workflow, by a required field, or by a reliable process. A wrong number in a report is almost never a report problem.
  • 👥
    Design dashboards for the reader, not for yourself. The best dashboard is the one the VP of Sales opens every morning without anyone explaining it to them. Test it: show it to them and see if they understand it in 30 seconds without narration.
  • 📋
    Document every dashboard. Maintain a simple record: Dashboard name · Primary audience · Review cadence · Owner · Key questions it answers. This prevents dashboard sprawl and keeps the system purposeful over time.
  • 🔄
    Build reporting into your workflow configurations. Every time you build a workflow that sets a property, ask: "Do I need to report on this later?" If yes, make sure the property it sets is the exact property the report will filter on. Plan reporting requirements before building automations.
Applied Learning · 21
Practice Exercise

Do this in your free HubSpot sandbox — approximately 60 minutes. This exercise builds the full reporting layer on top of everything you've configured in previous modules.

Part A — Build 3 essential reports (40 min)

  1. Lifecycle Stage Funnel — Reports → Create report → Funnel → Contact funnel. Stages: Lead → MQL → SQL → Opportunity → Customer. Date filter: Create Date, rolling last 90 days. Save as "Lifecycle Stage Funnel — Rolling 90 Days."
  2. Pipeline Forecast — Create report → Single object → Deals. Filters: Stage not Closed Won or Lost · Close Date this quarter. Measure: Sum of Amount. Breakdown: by Deal Stage. Visualisation: bar chart. Save as "Pipeline Forecast — This Quarter — By Stage."
  3. Rep Activity — Create report → Single object → Calls. Filters: Call Date this week. Measure: Count of calls. Breakdown: by Activity Owner. Visualisation: bar chart. Save as "Call Activity — This Week — By Owner." Repeat for Emails and Meetings.

Part B — Build a Sales Dashboard (20 min)

  1. Go to Reports → Dashboards → Create dashboard. Name it: "Sales Team Dashboard."
  2. Add your 3 reports from Part A. Arrange: Pipeline Forecast top-left (most important for sales), Lifecycle Funnel top-right, Rep Activity bottom.
  3. Set the dashboard to be shared with: "Anyone in my HubSpot account." This makes it visible to all users.
  4. Pin it to your HubSpot home (click the pin icon in the dashboard header). Now it appears on your HubSpot home page every time you log in.
  5. Look at the pipeline forecast report. Is the data what you expected? If Amount is showing as $0 for most deals — that's a data quality issue, not a report issue. Make a note: "Require Amount at Qualified stage."
Applied Learning · 22
Interview Questions
"How do you ensure reporting data is accurate in HubSpot?"
Reporting accuracy is entirely dependent on data quality upstream. Before building any report, I audit the data that feeds into it. For a lifecycle funnel report: are lifecycle stages being set consistently by workflows or manually? For a pipeline forecast: is Amount required at the right stage so it's never blank? For lost deal analysis: is Closed Lost Reason required? For any report I build, I trace backward to identify every property it depends on and verify that property is being set correctly — either by a workflow, a required field, or a reliable manual process. A report showing wrong numbers is almost never a report configuration problem. It's a data capture problem that needs to be fixed upstream.
"A VP of Sales asks you to build a pipeline health dashboard. What do you include and why?"
I'd start by asking what decisions they're making from this dashboard — that determines the reports. Typically a pipeline health view needs: a weighted pipeline forecast grouped by owner and by stage (this is the number leadership trusts for planning, not raw pipeline total), deals closing in the next 30 days sorted by amount (the immediate-action list), an open pipeline view sorted by last activity date ascending (stale deals surface at the top — the weekly review tool), a closed lost reason breakdown for the last 90 days (the diagnostic tool), and rep activity metrics for the week (calls, emails, meetings by rep — separates effort from outcome for coaching). I'd put the weighted forecast prominently at the top since that's the most time-sensitive. All reports would use rolling time periods so the dashboard stays current automatically. I'd also verify before building that Amount and Close Date are required fields on the pipeline — if they're not, the forecast report will produce meaningless numbers regardless of how well it's built.
"What's the difference between a single-object, cross-object, and attribution report, and when would you use each?"
Single-object reports pull from one type of record — Contacts, Deals, Tickets — and answer questions within that domain: "How many deals closed this quarter by stage?" or "How many contacts have lifecycle stage MQL?" They're fast to build and highly reliable. Cross-object reports join two or more object types — for example, Contacts plus their associated Deals — letting you answer questions that span the Marketing-to-Sales journey: "Which lead sources generate the highest average deal value?" That requires connecting Contact source data with Deal revenue data. Attribution reports are specifically for tracing which marketing interactions contributed to a conversion, using models like first touch (who brought them in), last touch (what closed them), or linear (distributing credit across all touchpoints). I'd use single-object for operational reporting within a team, cross-object when I need to connect Marketing outcomes to Sales revenue, and attribution when the CMO needs to justify budget allocation by channel.
Applied Learning · 23
Summary Cheatsheet
ConceptKey point
What is a reportA saved query against CRM data answering one specific business question
What is a dashboardA curated collection of reports designed for one specific audience
4 report typesSingle-object · Cross-object (multi-object) · Funnel · Attribution
5 report builder panelsData source → Filters → Measures → Dimensions (breakdown) → Visualisation
Most important principleReports are only as accurate as the upstream data that feeds them
Report 01: Lifecycle funnelContact funnel → all stages → rolling 90 days. Reveals funnel health and conversion rates.
Report 02: MQL→CustomerRequires date-stamp properties. Shows marketing effectiveness over time.
Report 03: Pipeline forecastDeals: Sum of Amount × Probability. Requires calibrated probabilities and required Amount field.
Report 04: Deal velocityAverage days in each stage (hs_date_entered_[stage]). Reveals pipeline bottlenecks.
Report 05: Closed lost reasonsMost actionable diagnostic report. Requires Closed Lost Reason as required field.
Report 06: Lead source revenueOriginal Source → Closed Won Amount. Sort by revenue, not lead count.
Report 07: Rep activityCalls/emails/meetings by rep this week. Separates effort from outcome for coaching.
Report 08: CS metricsTicket volume, first response time, resolution time. Connects to retention revenue.
Dashboard limit8–12 reports max per dashboard. One audience per dashboard.
Date rangesAlways use rolling dates (Last 30 days, This quarter). Fixed dates go stale.
Attribution modelsFirst touch (awareness) · Last touch (conversion drivers) · Linear (full journey)
Naming convention"Metric — Time Period — Breakdown" e.g. "Closed Lost Reasons — 90 Days — By Rep"
The feedback loopData → Report → Insight → Decision → Changed CRM behaviour → Better data → Better reports
RevOps insightReports don't create insight from nothing — they surface what's already in your data. Data quality is everything.
Admin interview gold"Before trusting any report, I trace backward to every property it depends on and verify each is being set consistently."
RevOps mindset on reporting — the curriculum capstone

This is the module where everything you've learned connects. The objects and properties you configured in Layer 1 generate raw data. The lifecycle stages, workflows, required fields, and pipeline configurations you built in Layers 2–4 ensure that data is clean, consistent, and meaningful. The reports and dashboards you build in this final layer are the feedback mechanism that reveals whether all of it is working — and what to improve next. A CRM with good reporting is a self-improving system: reports reveal problems, problems drive process changes, process changes improve data, better data produces more accurate reports. That loop — maintained by a skilled admin who understands both the technical configuration and the business questions — is what transforms a CRM from a digital contact book into a genuine revenue intelligence platform. That is the work of a HubSpot admin. That is the work of a RevOps practitioner. That is where you are now.

Curriculum complete.

11 modules · Objects · Properties · Lists · Lifecycle Stages · Lead Status · Forms & Imports · Conversations · Workflows · Sequences · Pipelines · Reports. You have the full stack.