Campaign-to-revenue
measurement worksheet.
The ad platform reports a conversion. Sales can’t find the campaign on the opportunity. Use this worksheet to agree what gets captured, who qualifies the response, and how won business appears in the report.
For B2B marketing, sales, and RevOps teams. No email required.
Leave with a plan
your team can use.
Fill in the Measurement plan with sales and your CRM owner. Use Campaign report for one campaign and acquisition cohort, then duplicate that tab for the next report. Check the separate Illustrative example when you need a starting point.
The workbook includes editable definitions and owners, a reporting form, and formulas for cost per qualified lead and the media-only bookings multiple. Missing inputs stay blank; a zero denominator shows n.a.
Download the template
Download Excel worksheet (.xlsx)Download text worksheet (.md)Open the workbook in Excel or import it into Google Sheets. The text version has the same planning prompts and a report form.
All examples are illustrative planning choices or fictional numbers. They are not client results, benchmarks, recommended platform defaults, or performance forecasts.
Choose channels and accounts
Start with the audience and the offer. ABM is an account strategy that can span several channels; record the account list and buying roles separately from the advertising platform.
Channel and role
Name each platform, its job, offer, landing page, budget owner, and spend source. Confirm account and market availability before including a channel.
Illustrative example or site convention
LinkedIn Ads; invite operations leaders to a CRM measurement workshop.
Source and medium
Agree a controlled vocabulary. Separate paid campaigns from organic social and AI referrals. Document any custom channel grouping.
Illustrative example or site convention
linkedin / paid_social; facebook / paid_social; instagram / paid_social; openai / paid (custom grouping to verify).
Target accounts
Define ICP, account list version, tier, buying roles, account ID, and exclusions. Decide how subsidiaries and existing customers are handled.
Illustrative example or site convention
Tier 1: named consulting firms; exclude customers and active opportunities from acquisition reporting.
Sales handoff
Name the receiving owner, follow-up deadline, fallback queue, and what happens when an account is already owned.
Illustrative example or site convention
Account owner reviews the inquiry by the next business day; unowned accounts enter the RevOps queue.
Give every campaign a stable ID
A campaign name can change. Its ID should survive the rename. Keep a registry that connects your internal ID to platform IDs, CRM campaigns, and cost exports.
Campaign registry
Record internal campaign ID, name, platform account ID, platform campaign ID, CRM campaign ID, owner, start/end dates, and status. Store identifiers as text.
Illustrative example or site convention
Internal ID: pm_2026_09_001; display name: consulting_measurement_workshop.
URL parameters
Define utm_id, utm_source, utm_medium, utm_campaign, utm_source_platform, and utm_content. Reserve utm_term for an agreed keyword or targeting code. Use lowercase tokens without personal data.
Illustrative example or site convention
utm_id=pm_2026_09_001; utm_source=linkedin; utm_medium=paid_social; utm_campaign=consulting_measurement_workshop; utm_source_platform=linkedin; utm_content=ops_leader_v1.
Destination QA
Test the final URL through redirects and form submission. Confirm campaign IDs reach the lead record. Do not add UTMs to internal links.
Illustrative example or site convention
Ad URL to landing page to contact request retains pm_2026_09_001.
Native lead forms
Map platform lead ID and campaign ID through the integration when there is no website visit. Document unavailable browser attribution.
Illustrative example or site convention
Native form maps to the same CRM campaign registry using the platform campaign ID.
Define what counts as a conversion
A downloaded worksheet is engagement. A received inquiry still needs qualification. Write the exact trigger and counting rule before choosing which events inform campaign optimization.
Engagement event
Record the event name, trigger, permitted parameters, and purpose. Keep resource use separate from leads.
Illustrative example or site convention
On this site: content_engaged with content_type=resource_download on a download-link click. It does not prove the file was opened.
Inquiry event
Count only accepted submissions with a durable delivery receipt. Record form ID, stable receipt/event ID, timestamp, and destination.
Illustrative example or site convention
On this site: generate_lead after a valid lead_id receipt. book_call_clicked measures a contact-link click, not a booking.
Lifecycle events
Define qualified lead, sales acceptance, meeting held, opportunity created, and closed won as distinct CRM transitions with timestamps and owners.
Illustrative example or site convention
Set qualified_at after fit and intent review; a booked meeting alone does not qualify an opportunity.
Deduplication
Choose an event ID, retry policy, and counting unit. Browser/server copies of one event share an ID where the destination supports deduplication.
Illustrative example or site convention
One submission ID per accepted inquiry; one opportunity ID per deal; retries do not create new conversions.
Consent and QA
Document consent requirements, destination allowlists, test exclusions, and failed-delivery behavior. Keep personal data and raw click IDs out of general analytics events.
Illustrative example or site convention
Test denied consent, accepted and failed deliveries, and repeated receipts. CRM lifecycle feedback needs its own integration.
Map the CRM fields and joins
Record your actual CRM field names, types, write rules, and owners. These names describe a proposed contract; they are not fields this download installs.
First and latest source
Map source, medium, campaign, campaign_id, content, source_platform, landing_path, and captured_at for first and last non-direct touch. Preserve the first touch.
Illustrative example or site convention
On this site: attribution.first_touch.campaign_id and attribution.last_touch.campaign_id come from utm_id; direct returns retain the last non-direct touch.
Lead and contact keys
Map submission ID, platform lead ID if available, lead/contact ID, created_at, and deduplication key. Define lead-to-contact merge behavior.
Illustrative example or site convention
Keep campaign memberships and timestamps when a lead becomes a contact. Do not join by company name alone.
Account and membership
Map account ID, ABM tier/list version, buying role, CRM campaign ID, member status, and membership timestamp. Define contact-to-account resolution.
Illustrative example or site convention
Resolve approved company domains to account IDs; queue ambiguous matches for review.
Qualification and owner
Map lifecycle stage, qualified_at, accepted_at, qualification/rejection reasons, assigned owner, and next action due_at.
Illustrative example or site convention
qualification_reason=fit_and_active_project; rejection_reason=outside_icp.
Opportunity and revenue
Map opportunity ID, account ID, contact roles, primary sourced campaign ID, created_at, stage, closed_at, amount, currency, and revenue type.
Illustrative example or site convention
One primary sourced campaign per opportunity; store influenced campaign memberships separately.
Reconciliation keys
Specify campaign/platform ID joins for spend and opportunity/invoice IDs for finance. Retain source extracts, extracted_at, and unmapped records.
Illustrative example or site convention
Aggregate spend and opportunity facts separately. Joining daily spend to every contact row would multiply the cost.
Agree qualification with sales
A form fill is evidence of a response, not a sales stage. Sales and marketing need a rule they can apply to the same record and get the same answer.
Qualified lead rule
Specify required fit AND intent evidence, acceptable values, missing-data handling, and the person who approves the transition.
Illustrative example or site convention
Target account and relevant buying role AND a request about an active project. Missing fit data goes to review.
Account qualification
Define how contact activity rolls up to an account. Decide whether one contact is enough and what evidence sales must accept.
Illustrative example or site convention
An engaged target account qualifies when sales confirms a relevant project and next step.
Opportunity entry
Define required problem, buyer/contact role, next step, owner, and amount policy. Keep meeting booked, held, and opportunity created separate.
Illustrative example or site convention
Sales accepts a discovery outcome and records an agreed next step before creating an opportunity.
Rejection and recycling
List spam, tests, duplicates, vendors, candidates, outside-ICP records, existing deals, and timing issues. Define reason codes and re-entry rules.
Illustrative example or site convention
No active project: recycle with a review date. Duplicate: merge and retain source history.
Feedback cadence
Agree who reviews quality and when rules change. Version the rule and preserve the version used for prior reports.
Illustrative example or site convention
Sales and marketing review rejections weekly; RevOps records approved changes and effective dates.
Write down the attribution windows
Record each platform's actual settings and your CRM reporting rule. A browser retention period, an ad-platform conversion window, and a sales-cycle cohort are different decisions.
Platform windows
For each platform and event, record click/view windows, model, conversion date basis, timezone, and settings review date. Use n.a. where unavailable.
Illustrative example or site convention
Illustrative choice only: 30-day click and 1-day view. Confirm support and actual settings; this is not a platform default.
CRM sourced rule
Choose the eligible touch, lookback length, anchor event, boundary inclusivity, tie-break rule, and handling of existing opportunities.
Illustrative example or site convention
Earliest known eligible campaign within 90 elapsed days before opportunity creation, inclusive; break ties by stable touch ID.
Influenced rule
Define eligible engagement and its window separately. Multiple campaigns may influence one opportunity, so influenced totals are not additive.
Illustrative example or site convention
Known response between opportunity creation and close is influence only; it does not replace the sourced campaign.
Storage and missing signals
Define browser retention separately from CRM history. Retain unknown sources, consent gaps, offline activity, and cross-device limitations.
Illustrative example or site convention
This site's attribution storage expires after 90 days with analytics consent. That does not set a client's sales-cycle reporting window.
Model changes
Record rule version, effective date, restatement policy, data lag, and report owner. Explain platform/CRM differences.
Illustrative example or site convention
Show platform credit beside CRM outcomes. Attribution assigns credit; it does not establish incremental revenue.
Specify the revenue report
Choose the revenue definition before comparing channels. A signed contract, an invoice, cash received, and recognized revenue can have different dates and amounts.
Report scope
Record owner, cadence, period start/end, timezone, as-of date, extract timestamps, currency, FX policy, and rule version.
Illustrative example or site convention
Monthly review, UTC boundaries, USD, campaign cohort through an explicit as-of date; save extract timestamps.
Cohort and grain
Choose a cohort and counting unit for each measure. Document date filters. Separate current-period activity from outcomes of earlier acquisition cohorts.
Illustrative example or site convention
One campaign and acquisition cohort per report tab. Count later outcomes of that cohort through the as-of date.
Spend and funnel
Record media spend separately from fees, software, and creative. Count distinct inquiries, qualified contacts, qualified accounts, and sourced opportunities.
Illustrative example or site convention
Cost per qualified lead = cohort media spend / distinct qualified contacts. A contact count is not an account count.
Pipeline and won value
Sum sourced opportunity amounts once per opportunity under the chosen rule. Separate open pipeline from closed-won contract bookings.
Illustrative example or site convention
Bookings / media spend is a media-only bookings multiple, not profit, ROI, cash collected, or incremental lift.
Revenue adjustments
Define recurring contracts, renewals, cancellations, credits, refunds, taxes, and FX. Reconcile booked value to the agreed CRM or finance source.
Illustrative example or site convention
Use signed net contract value; show recognized revenue and cash collected in separate finance reports.
Reconciliation and action
Check duplicate opportunity IDs, unmapped campaigns, unknown sources, currency, missing inputs, and lag. Record discrepancy, action, owner, and next review.
Illustrative example or site convention
Reconcile sourced plus other/unknown totals to the eligible CRM cohort. Never add platform credit or influenced totals to sourced revenue.
Trace one record all the way through.
Choose a test inquiry and follow its campaign ID into the CRM account and opportunity. Retry the delivery. Check a rejected lead and an unknown source too.
Before launch, each decision needs a definition, an owner, and evidence that the mapping works. Leave unresolved decisions open and assign the next action. If your CRM can already produce the agreed report, you may only need field cleanup and a reporting routine.
This is a planning template. It doesn’t connect ad accounts or install CRM fields, offline conversions, pixels, or server integrations. Those changes need to be implemented and tested in your systems.
Reference documentation
UTM parameters identify campaign traffic; a lookback window determines which earlier touches are eligible for credit. Confirm the settings in each account before launch.
Worksheet updated September 12, 2026.
Bring the fields you can’t reconcile.
We can scope campaign setup, CRM handoffs, qualification feedback, and reporting around the gaps you identify in the worksheet.