Marketing operations analytics: throughput and handoff delays

Marketing operations analytics measures how long campaigns take to launch and how long assigned leads wait for sales acceptance. Start with dated work records, calculate elapsed time, and report the unfinished queue alongside completed throughput.

These measures answer an execution question: where is work waiting, and who can move it? Campaign response and revenue answer different questions. Use marketing ROI versus ROAS when the decision concerns campaign return rather than process delay.

Define the events before measuring speed

A launch clock needs a start that people recognize. A request submitted without approved copy is different from a campaign ready for production. Choose one start event, retain the original date, and document any separate paused-time measure. Otherwise teams can improve reported speed simply by moving the start later.

For this example, launch time runs from an approved, complete brief to the first actual launch. Handoff time runs from assignment to explicit sales acceptance. Assignment alone does not establish that someone reviewed the lead.

Use one row per campaign in the launch file and one row per assignment episode in the handoff file. Keep campaign ID, lead ID, assignee, event dates, and current state. Reassignment should create a traceable new episode rather than overwrite the first waiting period. The distinction between operational and sales events also matters in sales terminology comparisons.

Calculate campaign launch time from the export

A fictional US industrial supplier reviews its September work as of September 30, 2026. These are date-only records using calendar days. The same-day difference is zero; weekends remain in the elapsed period.

On a tab named Campaigns, put the reporting date in K1 with =DATE(2026,9,30). Columns A through E hold the following rows; a dash represents an empty cell, not a typed dash.

Use these Google Sheets formulas in D2 and E2, then fill down through row 7:

=IF(C2="","",C2-B2)
=IF(C2="",$K$1-B2,"")

Keep dates as actual spreadsheet dates. Reject a launch before its ready date and any event after the cutoff. Do not replace a missing launch with the cutoff inside the completed-time column; that would label unfinished work as completed.

The completed durations total 7 + 9 + 10 + 14 = 40 days across four launches. Their mean is 40 / 4 = 10 days. The median is (9 + 10) / 2 = 9.5 days:

=MEDIAN(D2:D7)

Google Sheets documents MEDIAN as the center of the numeric values, interpolating between the middle pair for an even count and ignoring text. Keep the two open campaigns in the backlog report: their current ages are eight and five days. A completed-time summary alone cannot describe their eventual launch duration.

Measure the lead handoff separately

The same supplier reviews this small assignment cohort at the same cutoff. Put September 30, 2026, in K1 on a separate Handoffs tab. Columns A through E again hold identifiers, the start event, the completion event, completed days, and open age.

Reuse the row formulas above, filling through row 6. The median accepted time is three days: the middle of 1, 3, and 4. Acceptance to date is 3 / 5 = 60%, while two assignments remain open. This is a cohort snapshot, not a forecast of eventual acceptance.

Count open assignments and those older than an internally agreed two-calendar-day target:

=COUNTIFS(B2:B6,"<>",C2:C6,"")
=COUNTIFS(B2:B6,"<>",C2:C6,"",E2:E6,">2")

The results are two open and one over target: L204. L205 is exactly two days old and does not meet the >2 test. Google's COUNTIFS documentation explains the multiple-criteria count and requires matching range dimensions.

This handoff view stops at acceptance. Follow later opportunity and won outcomes with CRM marketing analytics; do not rename acceptance as conversion to revenue.

Prove that work has not disappeared

Reconcile both queues to their source IDs. The campaign file has six records: four launched plus two open. The handoff file has five: three accepted plus two open. No row is counted in both completion and backlog.

For the illustrated handoff cohort, opening backlog is zero, five assignments enter, three are accepted, and none are returned or canceled. Closing backlog is therefore 0 + 5 - 3 - 0 = 2. A full monthly queue uses the same bridge but includes opening items from earlier months.

Marketing operations should bring the oldest unresolved IDs to the review. The assignee confirms the blocker and next action; sales operations confirms whether acceptance was recorded correctly. Use B2B marketing analytics for broader commercial comparisons once the operational records reconcile.

Where it goes wrong

• Changing the clock. Starting one campaign at request and another at approved brief creates a difference in definitions rather than speed.
• Hiding open work. A short median among completed items can coexist with a growing, aging backlog. Publish both populations.
• Overwriting assignment history. Reassignment can erase the longest delay. Retain each episode and distinguish episode time from total lead waiting time.
• Mixing timestamps and dates. Time zones, partial days, and weekend rules alter the clock. Normalize the source before applying a calendar-day target.
• Dropping returned leads. Returns and cancellations need explicit dispositions in the backlog bridge, with responsibility for any further action.

Covirage is not affiliated with Google.

Check your operational exports in Covirage

Bring your campaign register and lead-handoff export with agreed start events and a reporting cutoff. Covirage maps the columns, and its tools compute and check the timing and backlog figures; the external AI model explains the result with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data.

See Covirage for sales insights for the supporting business context.