Connect campaign labels, recognised enquiries and agreed qualification rules before judging which marketing channel deserves more budget.
One campaign brings many form submissions. Another brings fewer enquiries but more conversations about projects your business can actually deliver. If the report only counts submissions, you may reward the wrong activity.
For a Nepal service business, useful channel measurement connects marketing activity with a recognised enquiry and a consistent qualification decision. It does not require pretending that every sale has one perfectly knowable source.
The examples below are hypothetical. They illustrate a reporting method, not advertising results or a recommendation to buy a particular channel.
Agree what qualified means before comparing channels
A Bharatpur equipment-installation business might call an enquiry qualified when the requirement fits its service, the location is within actual coverage, the customer has a meaningful project timeframe and staff have enough information to take the next step. These are proposed business criteria, not a universal definition.
Apply the same criteria to every channel. Do not mark social-media enquiries qualified after a short message while requiring search enquiries to complete a detailed consultation. Keep the reason for the decision and the date of review.
Qualification is also different from a quotation, an accepted order or a payment. A person can have a relevant requirement without being ready to purchase. Keep those later outcomes in their own stages.
Hypothetical campaign review: enquiries need a shared qualification definition.
Keep source, campaign and enquiry identity separate
Google Analytics documents UTM parameters for identifying campaigns that refer website traffic. A consistent naming convention helps avoid splitting one campaign across several labels. Those labels describe acquisition information; they do not automatically establish that an enquiry became a good business opportunity.
Retain a recognised enquiry reference in the CRM or enquiry register. Record the available source evidence, programme or service interest, assigned staff member and current qualification outcome. If the person contacts the business again about the same requirement, review whether it is the same opportunity rather than counting a new lead automatically.
For telephone calls, referrals and walk-ins, use an agreed source question when appropriate. Record “unknown” where the answer is unavailable. An honest unknown category is more useful than a staff member guessing that every enquiry came from a recent advertisement.
Suggested qualification process; unanswered and unsuitable are different outcomes.
Conceptual artwork: more messages and better-fit enquiries are different measures.
Use a comparison with a clear denominator
Consider two hypothetical paid campaigns reviewed over the same period. Campaign A costs NPR 12,000 and produces forty recognised enquiries, twelve of which meet the agreed qualification criteria. Campaign B costs NPR 9,000 and produces twenty enquiries, ten qualified.
| Hypothetical metric |
Campaign A |
Campaign B |
| Included campaign spend |
NPR 12,000 |
NPR 9,000 |
| Recognised enquiries |
40 |
20 |
| Qualified enquiries |
12 |
10 |
| Spend per recognised enquiry |
NPR 300 |
NPR 450 |
| Spend per qualified enquiry |
NPR 1,000 |
NPR 900 |
Campaign A costs NPR 300 per recognised enquiry and NPR 1,000 per qualified enquiry. Campaign B costs NPR 450 and NPR 900 respectively. These figures use the stated campaign spend only; they exclude staff costs and other marketing overhead.
Hypothetical CRM dashboard compares recognised and qualified enquiries using the article’s original campaign-spend example. It is not a live WorkSphere dashboard or evidence of marketing results.
A is cheaper for initial enquiry volume, while B is cheaper for qualified enquiries in this example. Neither calculation proves that B is more profitable. You still need later outcomes, comparable selling effort, adequate observation time and a clear definition of what the spend includes.
Hypothetical campaign-spend measure, not profit or full customer-acquisition cost.
Allow time for the business decision
A new campaign may appear weak if its enquiries have not had time to receive a response. Record the reporting cut-off, whether staff contacted each enquiry and whether a qualification decision remains pending. Do not quietly classify unanswered enquiries as poor-quality leads.
Compare cohorts with similar time to develop. If an installation project typically requires discussion and site information, a same-day report should not be interpreted as a final sales result. The review period should fit the real process rather than a convenient spreadsheet date.
Avoid turning source labels into certainty
A customer might first see a social post, later search for your name and finally call after a referral. A last-touch record is one useful observation, not the full story. Explain which attribution method the report uses and keep self-reported source separate from observed website evidence where both exist.
Do not put names, phone numbers or other personal information into public campaign URL parameters. Collect only the information needed for the process, restrict access and define retention with the actual business policies and applicable requirements.
When sharing a report, include unknown sources and pending qualification. A tidy percentage that excludes every difficult record can create a misleading impression of precision.
Unknown and pending records remain visible instead of being silently discarded.
Hypothetical follow-up scene: record what is known before classifying an enquiry.
Connect the report to an action
Review the search query or message that attracted unsuitable enquiries, the page explaining the service and how quickly the business responded. Low quality can reflect targeting, unclear copy or inconsistent follow-up; the channel name alone does not explain the cause.
A planned connection between CRM and marketing reports could retain recognised opportunities, while Tasks could assign unanswered enquiries and Project Management could hold accepted work. Each integration needs agreed definitions. Do not assume that a dashboard automatically reconciles those records.