Blog · Board and management reporting
Marketing operations KPIs show whether campaign records are complete and sales handoffs happen on time. Work through campaign-level completeness, response delays, acceptance, and opportunity conversion with reconciled CRM counts.
Marketing operations KPIs measure whether campaign records are usable and qualified demand reaches sales under agreed rules. Start with record completeness, timely handoffs, pending work, acceptance, and opportunity conversion by campaign. These measures explain whether the process supports the funnel, alongside the commercial outcomes marketing already reports.
A handoff needs an eligible record, a start timestamp, a receiving owner, and a recorded action that stops the clock. Assignment and acknowledgment are different events. Choose the one your service policy actually promises, then use that event consistently.
For this article, the clock starts when a qualified lead becomes eligible for sales. It stops when the assigned salesperson acknowledges the lead. The policy allows 24 elapsed hours, including weekends; a company using business hours would need the appropriate working calendar instead.
Acceptance is a separate decision about readiness. HubSpot's lifecycle-stage documentation distinguishes marketing qualification from sales qualification. An acknowledgment can be timely even when sales later rejects the lead, so do not let the acceptance date silently replace the response timestamp. Covirage is not affiliated with HubSpot.
Document what constitutes an opportunity too. For broader stage terminology, see the sales terms comparison pages; for outcome selection, see B2B marketing KPIs.
| KPI | Definition | Accountable owner |
|---|---|---|
| Required-field completeness | Records with every applicable required field valid / Entering records | Marketing operations |
| On-time acknowledgment rate | Eligible leads acknowledged within the policy window / Eligible leads with the full window elapsed | Sales operations |
| Overdue pending rate | Unacknowledged eligible leads past the deadline / Eligible leads with the full window elapsed | Receiving sales manager |
| Mean acknowledgment delay | Total elapsed hours for acknowledged leads / Acknowledged leads | Sales operations |
| Sales acceptance rate | Accepted leads / Eligible leads in the observation cohort | Marketing and sales |
| Accepted-to-opportunity conversion | Accepted leads reaching an opportunity / Accepted leads | Sales operations |
State that acceptance uses all eligible leads here. Another report may use acknowledged leads as its denominator; that is a different rate and should have a different label. Completeness is also record-based, so one record missing several fields still counts as one incomplete record.
The Census Bureau's editing standard identifies checks for missing data, duplicate records, and outliers as part of detecting errors. That standard governs Census work, not a company's CRM. The practical lesson for this scorecard is to check the input records before interpreting the percentages, and retain the reason each record failed.
Bring one row per lead-cohort ID with campaign ID, entry date, qualification date, eligibility timestamp, assigned owner, acknowledgment timestamp, acceptance outcome, and opportunity ID. Include the fields your organization requires for routing, such as account, contact method, and territory.
Keep eligibility independent from completeness. A record can meet the routing rule while lacking a reporting field, or contain every required field while not qualifying for sales. Do not remove incomplete records from the completeness denominator simply because they are inconvenient.
Use a single reporting cutoff and time zone for elapsed-hour calculations. Freeze the cohort definition and observe acceptance and opportunity creation through the same follow-up window after eligibility. A current-stage export alone may lose historical transitions, so request the dated fields needed to reconstruct the handoff.
A fictional US business compares two completed campaign cohorts. Every eligible lead below has had the full acknowledgment window and the common downstream follow-up window. The total hours include acknowledged leads only; pending leads remain separately visible.
| Input from export | Webinar campaign | Guide campaign | Total |
|---|---|---|---|
| Entering lead records | 200 | 100 | 300 |
| Complete entering records | 190 | 80 | 270 |
| Eligible sales handoffs | 180 | 90 | 270 |
| Acknowledged on time | 153 | 54 | 207 |
| Acknowledged late | 18 | 18 | 36 |
| Still pending and overdue | 9 | 18 | 27 |
| All acknowledged handoffs | 171 | 72 | 243 |
| Total hours to acknowledgment | 1,026 | 864 | 1,890 |
| Accepted leads | 126 | 45 | 171 |
| Accepted leads reaching an opportunity | 42 | 9 | 51 |
The input counts are distinct leads. Where several accepted leads are associated with one opportunity, this scorecard counts each qualifying lead once, not the number or value of opportunities. A deal-level measure needs a separate distinct-opportunity denominator.
Percentages and hours below are rounded to one decimal place, using unrounded calculations.
| KPI | Webinar campaign | Guide campaign | Combined cohort |
|---|---|---|---|
| Required-field completeness | 95.0% | 80.0% | 90.0% |
| On-time acknowledgment rate | 85.0% | 60.0% | 76.7% |
| Overdue pending rate | 5.0% | 20.0% | 10.0% |
| Mean acknowledgment delay, completed only | 6.0 hours | 12.0 hours | 7.8 hours |
| Sales acceptance rate | 70.0% | 50.0% | 63.3% |
| Accepted-to-opportunity conversion | 33.3% | 20.0% | 29.8% |
Webinar completeness is 190 / 200 = 95.0%. Its on-time rate is 153 / 180 = 85.0%, and its completed-only delay is 1,026 / 171 = 6.0 hours. The guide campaign's delay is 864 / 72 = 12.0 hours; its overdue pending rate is 18 / 90 = 20.0%.
The combined delay is 1,890 / 243 = 7.8 hours. Do not average the campaign means because their completed populations differ. Also do not read that mean as the waiting time of every eligible lead: the overdue pending population is excluded from the completed-time calculation.
The handoff identity is on time plus late plus pending equals eligible. Across both campaigns, 207 + 36 + 27 = 270. Acknowledged handoffs are 207 + 36 = 243, the denominator used for the mean delay.
Completeness has its own check: 270 complete records + 30 incomplete records = 300 entering records. The equal totals for complete records and eligible handoffs are coincidental; they do not establish that these are the same leads. Match every subtotal back to its filtered record list.
The guide campaign needs two investigations: missing required fields and overdue acknowledgments. Marketing operations should inspect the field failures; the receiving manager should inspect assignment, coverage, and pending ownership. Lower acceptance and opportunity conversion warrant a qualification review, but the table does not prove delayed responses caused those outcomes.
Use marketing automation KPIs for message delivery and campaign conversion. The separate marketing operations analytics page covers the broader analysis of process issues.
Bring campaign and CRM exports with the required-field rules, timestamps, and observation cutoff documented. Covirage maps the columns; its tools compute and check completeness, handoff, and conversion figures, and the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data; account creation takes about a minute.
See Covirage for metrics governance for the supporting business use case.
Marketing outcome measures describe demand, customers, and commercial returns. Marketing operations measures examine whether the supporting records, definitions, and handoffs are reliable. A campaign can create strong demand while incomplete records or delayed assignment prevent sales from handling that demand consistently.
Use the service target agreed by marketing and sales for the lead type and working schedule. State when the clock begins and what action stops it. Compare performance against that policy and your history rather than treating an unexplained industry average as a universal target.
Define the fields required for each eligible record and count records meeting all applicable requirements. Divide by the full eligible population. Keep invalid values and missing fields visible as exceptions, and distinguish a record-completeness rate from the percentage of individual field cells populated.
Keep them in the service-level denominator once they have had the full allowed response window. An average response time calculated only from acknowledged records can still be useful, but label that population and show the overdue pending count beside it so unfinished work does not disappear.