HubSpot Reporting cheat sheet

HubSpot CRM objects include contacts, companies, deals, tickets, products, and line items; each record has a unique object ID used in report joins.

Properties are fields on an object; each has an internal name, field type, and group, and reports reference the internal name rather than the display label.

Associations connect records across objects, such as contact-to-company or deal-to-line-item; association labels can be used as report filters.

Lifecycle stage is a property that tracks a contact's or company's journey phase; standard values include subscriber, lead, MQL, SQL, opportunity, and customer.

Deal stages belong to pipelines; stage probability and deal amount feed weighted pipeline and forecast calculations.

Reports can use CRM objects plus HubSpot event data such as sessions, page views, form submissions, and marketing events when tracking is enabled.

Property history is not automatically reportable for every property; historical snapshots require property history settings or external storage.

Data source availability in reports depends on subscription tier, connected integrations, and user permissions.

A HubSpot dashboard is a collection of report cards; access can be set to private, specific users and teams, or everyone in the account.

Dashboard date-range filters apply only to cards that support the same date property; cards with incompatible date fields ignore the filter.

Visualization decision rule: use line for time trend, bar for category comparison, pie or donut for part-to-whole with few slices, table for record detail, and KPI for one value.

Report cards pull live from saved reports; editing a report changes every dashboard card that uses it.

A dashboard filter does not grant data permissions; viewers only see records their HubSpot permissions allow.

Compare equal-length periods, such as 28 days versus the prior 28 days, to avoid partial-month or partial-week bias.

Order cards from headline KPI to diagnostic breakdown so the dashboard answers one audience's primary question.

HubSpot dashboards can be exported or shared as a link; scheduled email delivery is configured on the report or dashboard where available.

A session begins with a first page view and ends after 30 minutes of inactivity or at midnight in the account time zone.

Page views count each page load; one session can contain multiple page views across pages.

Bounce rate equals single-page sessions divided by total sessions, expressed as a percentage.

Traffic source categories include direct, organic search, paid search, referral, social, email, and other campaigns.

UTM parameters populate campaign source, medium, name, term, and content; inconsistent capitalization creates separate source rows.

Session-to-contact conversion rate equals new contacts divided by sessions for the same date range.

HubSpot analytics requires the tracking code on pages; internal IP addresses can be excluded from traffic reports.

Contact original source records the first known source; latest source records the most recent source, so the two reports can differ.

The flywheel replaces the linear funnel with three stages-attract, engage, delight-and adds friction and leverage as forces.

Sales velocity formula: (number of open opportunities × average deal value × win rate) ÷ sales cycle length.

Stage conversion rate equals records reaching the next stage divided by records that entered the prior stage.

Deal velocity can be measured as average days from deal creation to close, segmented by pipeline and source.

Friction indicators include rising ticket volume, long stage dwell time, and falling lifecycle-stage conversion.

Leverage indicators include high-converting content, strong referral rates, and repeatable sales sequences.

Cross-object reports join marketing contacts, sales deals, and service tickets to reveal handoff gaps.

Retention reporting uses subscription status, repeat deal counts, or churn rate; churn rate = lost customers ÷ starting customers.

ROI = (revenue − cost) ÷ cost × 100%; ROAS = revenue ÷ ad spend.

CAC = total sales and marketing cost ÷ number of new customers acquired in the period.

Revenue in HubSpot ROI reports normally uses closed-won deal amount and close date, not deal create date.

Campaign ROI compares closed-won revenue attributed to the campaign with campaign cost or budget.

First-touch attribution credits the first interaction; last-touch credits the last; linear spreads credit evenly across touchpoints.

Connected ads accounts supply spend, clicks, impressions, and contact conversions; missing spend data produces incomplete ROI.

LTV:CAC ratio compares customer lifetime value with acquisition cost; payback period = CAC ÷ monthly gross margin per customer.

Exclude internal users, test deals, and duplicate records before calculating ROI to avoid distorted revenue totals.

Customer Journey Analytics is a Marketing Hub Enterprise reporting area with funnel, journey, and attribution report types.

A funnel report defines ordered stages using lifecycle stages, deal stages, or custom events and shows conversion between stages.

Funnel stage conversion rate = contacts reaching stage N ÷ contacts entering stage 1 × 100%.

Journey reports visualize paths across channels and interactions; incomplete tracking appears as unknown or unassigned paths.

Attribution reports assign credit for contacts or deals to marketing assets and interactions using a selected model.

Segment journey reports by contact property, campaign, or cohort to compare behavior between groups.

Time-to-convert metrics require reliable event timestamps; missing timestamps weaken stage duration analysis.

Journey data depends on lifecycle stage hygiene; skipped or manually overwritten stages distort funnel conversion.

The custom report builder combines a primary data source with associated objects, producing cross-object reports.

Data sources must be connected by HubSpot associations; the join path determines which records appear in the output.

Metrics include count, sum, average, minimum, and maximum; sum and average require numeric properties.

Filters combine AND/OR groups; filtering on an associated object can change the report grain and duplicate primary records.

Visualization options include table, bar, column, line, area, pie, donut, and KPI; table is required for row-level detail.

Saved custom reports can be added to dashboards and shared; access still follows object and report permissions.

Use a single-object report when the question needs one record type; use cross-object when the question needs a relationship.

Report performance and row limits depend on data volume; aggregated reports are lighter than record-level tables.

Reporting cadence rule: daily for operational alerts, weekly for pipeline, monthly for ROI and channel performance, quarterly for strategy.

Every KPI needs an owner, formula, data source, target, and review date before it enters an executive dashboard.

Standardize UTM naming, lifecycle stages, deal stages, and required properties to keep reports comparable across periods.

Build separate dashboards for executives, marketing, sales, and service so each audience sees relevant metrics and permissions.

Audit dashboards quarterly for unused cards, duplicate properties, broken filters, and reports with no decision owner.

Connect ads, analytics, CRM, and external warehouse data to close the loop from campaign spend to closed-won revenue.

Use closed-loop reporting: campaign → contact → deal → revenue; report both sourced and influenced revenue where available.

Before scaling a report, validate totals against a source-of-truth report such as deals closed-won or sessions.