A useful monthly marketing KPI dashboard does more than display traffic numbers. It connects campaign activity to engagement, leads, conversions, and revenue using consistent definitions and time windows. This reusable marketing KPI dashboard template shows which metrics to include, how to calculate the most useful rates, and how to turn unusual movements into decisions you can revisit each reporting cycle.
Overview
The best dashboard is not the one with the most charts. It is the one that helps you answer a small set of recurring questions:
- Are the right people reaching the website?
- Are visitors engaging with important pages and calls to action?
- Are those visits becoming leads, sign-ups, or purchases?
- What did marketing contribute to revenue during the selected period?
- What should change next month?
Organize the dashboard by funnel stage rather than by platform. A channel-by-channel report can show what happened in search, email, social, and paid campaigns, but a funnel view makes it easier to compare activity with business outcomes.
Use the following five dashboard groups:
- Reach and acquisition: users, sessions, visits from key channels, impressions, and campaign clicks.
- Engagement: engaged sessions, landing-page views, scroll or interaction events, and calls-to-action clicked.
- Lead generation: form submissions, demo requests, newsletter sign-ups, or another defined lead event.
- Conversion: purchases, qualified leads, trials, bookings, or the primary outcome for the business.
- Revenue and efficiency: attributed revenue, conversion rate, cost per lead, cost per acquisition, and return measures where cost data is reliable.
Keep a short executive summary above these groups. It should contain the reporting period, three to five headline KPIs, notable changes, and an explanation of the most important movement. The detailed tables can follow below.
How to estimate
Start with a simple funnel model. Each stage should use a defined numerator, denominator, and reporting window.
| Funnel stage | Recommended metric | Basic calculation |
|---|---|---|
| Acquisition | Channel share | Channel sessions ÷ total sessions × 100 |
| Engagement | Click-through or interaction rate | Tracked interactions ÷ relevant views or visits × 100 |
| Lead generation | Lead conversion rate | Leads ÷ eligible sessions or landing-page visits × 100 |
| Sales | Conversion rate | Conversions ÷ eligible sessions or users × 100 |
| Efficiency | Cost per lead | Marketing cost ÷ leads |
| Revenue | Revenue per conversion | Attributed revenue ÷ conversions |
“Eligible” is important. A purchase conversion rate may use sessions, users, or checkout starters as its denominator. Those choices produce different results, so record the definition beside the metric instead of assuming the label explains it.
For planning, you can estimate downstream outcomes from upstream activity:
Expected conversions = eligible visits × lead or purchase conversion rate
For example, if a landing page receives 2,000 eligible visits and the working conversion-rate assumption is 2%, the estimate is 40 conversions. This is a planning calculation, not a promise. Replace the assumption with observed data as soon as the campaign has enough comparable activity.
For revenue planning, use:
Expected revenue = expected conversions × average order value
For a lead-based business, use qualified leads and an observed close rate instead of treating every form submission as revenue. If 100 qualified leads produce a 15% close rate and the average closed deal is 1,000 units of your chosen currency, the model estimates 15 deals and 15,000 in revenue. Label whether this is booked, recognized, or pipeline revenue; those are not interchangeable.
When campaign data looks inconsistent, review the UTM naming convention and campaign audit workflow. Consistent source, medium, campaign, and content values make channel comparisons more useful.
Inputs and assumptions
Before building charts, create a metric dictionary. This prevents a monthly dashboard from quietly changing meaning over time.
Required inputs
- Reporting dates: the exact start and end dates, including the time zone used by the reporting system.
- Traffic inputs: users, sessions, landing-page visits, and channel or campaign dimensions.
- Interaction inputs: defined click, download, video, form-start, or other events.
- Lead inputs: the event that counts as a lead and, if available, its qualification status.
- Conversion inputs: completed purchases, booked calls, subscriptions, or another primary outcome.
- Cost inputs: spend, media cost, or other included marketing costs, with a clear inclusion rule.
- Revenue inputs: the revenue field and attribution method used in the report.
Assumptions to document
Write down whether the dashboard counts users or sessions, how internal traffic is handled, which events are marked as conversions, and whether totals are platform-reported or imported from another system. Privacy-conscious measurement may limit user-level detail, so a dashboard can still be useful when it focuses on aggregated trends and clearly defined events.
Do not mix incompatible windows. Monthly traffic from April should not be compared with conversions recorded under a different attribution window without noting the difference. A lead generated late in the month may become a sale later, while platform dashboards may assign that sale back to an earlier interaction. Keep “activity generated this month,” “conversions recorded this month,” and “revenue attributed this month” as separate concepts when necessary.
For reliable event definitions, use a documented event plan such as the GA4 event tracking plan template. For button clicks, outbound links, and downloads, compare the dashboard with a click tracking setup guide so important actions are not inferred from pageviews alone.
Worked examples
Example 1: Landing-page performance
A campaign sends 1,500 sessions to a landing page. The page records 45 completed forms and 9 qualified leads.
- Form conversion rate: 45 ÷ 1,500 × 100 = 3%
- Qualification rate: 9 ÷ 45 × 100 = 20%
- Qualified-lead rate from sessions: 9 ÷ 1,500 × 100 = 0.6%
The first rate describes the page’s ability to generate forms. The second reveals what happened after submission. Reporting both prevents a high form count from hiding weak lead quality.
Example 2: Monthly revenue view
Suppose a website records 80 purchases during the reporting period, with 12,000 eligible sessions and 24,000 in attributed revenue.
- Purchase conversion rate: 80 ÷ 12,000 × 100 = 0.67%, rounded
- Average revenue per purchase: 24,000 ÷ 80 = 300
- Revenue per eligible session: 24,000 ÷ 12,000 = 2
These figures become more useful when compared with a prior period using the same definitions. If revenue rises while purchases remain flat, investigate order value, product mix, refunds, and attribution settings before concluding that conversion performance improved.
Example 3: Finding the bottleneck
A report shows that traffic increased by 25%, but leads stayed unchanged. Check the funnel in order: channel mix, landing-page engagement, form starts, form completions, and qualification rate. More traffic from a lower-intent source may explain the result. Alternatively, a broken event, slower page, unclear CTA, or form change may have reduced conversion. A conversion funnel analysis can help isolate the stage that changed.
When to recalculate
Recalculate the dashboard every reporting cycle, but do not treat every fluctuation as a trend. Use a repeatable review process:
- Duplicate the previous report or preserve a dated snapshot.
- Set the new reporting window and confirm the time zone.
- Check tracking health before interpreting results: missing UTMs, duplicate events, sudden referral changes, or unrecorded conversions can distort the view.
- Replace the input values and recalculate rates from the raw counts.
- Compare with the previous period and a relevant prior period, such as the same season or campaign phase, when available.
- Record an explanation for each material movement and assign a next action.
Update the metric dictionary whenever a platform changes a metric name, attribution setting, event definition, or reporting interface. Revisit cost and revenue assumptions when budgets, pricing, product mix, sales-cycle timing, or refund behavior changes. Review the dashboard structure at least quarterly: remove metrics that no longer guide a decision, add missing business outcomes, and keep diagnostic metrics below the core KPI summary.
Finally, separate measurement from experimentation. If a landing-page change is being tested, use an appropriate experiment plan rather than declaring a winner from a single monthly comparison. The A/B test duration and sample size guide can help you assess whether a test has enough evidence. A dashboard should show what changed; a disciplined analysis should explain whether the change is likely to persist.
Use this template as a living worksheet: define the metric, enter the raw inputs, calculate the rate, note the attribution caveat, and attach one decision to the result. That keeps monthly marketing reporting focused on learning and action rather than collecting numbers for their own sake.