Start with three shared definitions: a genuine enquiry, a qualified lead and booked work. Record a source and an owner, test each handoff, and review outcomes alongside advertising costs. Add advanced tracking only after the basic records are dependable.

Why enquiries alone can hide the real result

A form submission is a useful starting signal, but it may come from a supplier, a job applicant, a duplicate request or someone outside your service area. If every submission counts equally, a campaign can look busy while your team struggles to find suitable work.

For an Edmonton contractor, a suitable lead might require the right project, location and timing. A Sherwood Park consultant may care about the decision-maker and scope. Define those checks with the person who answers the phone. Choose rules your team can apply consistently, rather than making a score that nobody maintains.

Agree on the stages before connecting tools

Use a short list of stages that matches how your business works. A new enquiry becomes qualified after someone checks fit. It becomes booked work when the customer reaches a clearly defined commitment, such as accepting an estimate. Keep a separate reason for enquiries that do not progress.

Google Analytics provides recommended lead-generation events, including generate_lead, qualify_lead and close_convert_lead. These are measurement labels, not a replacement for your own operating definitions. Google's recommended events reference explains their intended use.

A practical lead tracking mapAn operating template to adapt to your business; priority refers to setup order.
StageRecord or triggerOwnerPriority
Genuine enquirySuccessful accepted request; unique record IDWebsite and front deskEssential
Qualified leadService, location and timing checkedSales or estimatorEssential
Booked workAccepted quote or agreed bookingSales or operationsHigh
Closed without bookingReason recorded without deleting historyLead ownerHigh

Capture a useful source without making the form longer

Keep your website development focused on a reliable request flow: clear success and failure states, accessible fields and an acknowledgement that tells customers what happens next. Trigger an enquiry event after the server accepts the request. A click on Submit can happen even when validation fails.

Use consistent campaign tags for links you control, such as paid social or email campaigns. Keep source, campaign and landing-page fields with the lead where your integrations and permissions support them. A phone-link click shows intent to call; it does not prove a conversation happened. Record the actual call outcome separately.

Ask 'How did you hear about us?' when it helps, while allowing 'not sure'. A customer may see a social post, search your name later and call from another device. Report what your tracking can establish and retain uncertainty instead of assigning every booking to a confident-looking source.

Make your service area part of qualification

An enquiry from St. Albert may be ideal for one Edmonton company and impractical for another. Write down the communities you genuinely serve, travel limits and exceptions. Spruce Grove, Beaumont, Leduc, Fort Saskatchewan and Nisku can require different scheduling and dispatch decisions.

For example, a service firm could mark a Nisku industrial request as qualified after checking the equipment involved and its team's availability. A residential request outside its operating area could close with an out-of-area reason. These are illustrative workflow choices, not claims about local demand.

Compare outcomes by service and community only when you have enough records to make the comparison useful. A single large booking can distort a small sample. Avoid creating location pages or ad promises for areas your team cannot reliably serve.

Connect Google Ads to meaningful business outcomes

If you use Google Ads, review the conversion actions before increasing spend. Google supports qualified and converted lead goals for outcomes that happen after the initial online enquiry. Enhanced conversions for leads can improve matching by using hashed first-party customer data with supported imports. Implementation needs appropriate data collection, consent and platform configuration.

Decide which outcome should guide bidding and which events should remain diagnostic. Counting the same enquiry through several primary conversion actions can make results harder to interpret. Validate new imports and check duplicate handling, timestamps and import errors before relying on the data.

Google's current implementation guidance points advertisers toward Data Manager for enhanced conversions for leads. Ask whoever maintains your integration to verify its supported upload route against the current documentation. A functioning form tag does not establish that later CRM outcomes are reaching the advertising account.

Read the funnel before changing your budget

Review the same reporting period across your advertising platform and lead records. Account for delayed bookings: a lead received this week may become work next month. Compare lead cohorts when possible, and keep platform attribution separate from your financial records.

The example below uses invented figures to explain the calculation. With $1,200 in spend, 20 qualified leads and five booked jobs, cost per qualified lead is $60 and cost per booked job is $240. Those figures do not establish profit; include job margin, service costs, capacity and repeat business in your decision.

Example: enquiries to booked jobsIllustrative monthly cohort only. These are not NMR results, local benchmarks or promised outcomes.
  1. 40Genuine enquiries
  2. 20Qualified leads
  3. 5Booked jobs

40 enquiries → 20 qualified leads = 50% qualification. 20 qualified leads → 5 booked jobs = 25% booking. Example spend: $1,200; cost per booked job: $240.

Test the handoffs with real business scenarios

Run a controlled test enquiry through each important route before trusting a dashboard. Label test records and keep them out of performance reports. Verify the accepted request, confirmation, assigned owner, source and eventual status. Check a failed form, a duplicate submission, a phone enquiry and an out-of-area request too.

Keep names, email addresses, phone numbers and free-text enquiry contents out of GA4 event parameters and page URLs. Store customer details in the system designed to manage them, with access limited to the people who need them. Hashing data for a supported advertising feature does not make every use of customer data appropriate.

A short verification checklist

  • The event fires after a successful accepted enquiry, once per intended action.
  • The lead record has an owner and a clear next action.
  • Qualified and booked statuses have agreed meanings.
  • Import failures are visible to someone responsible for fixing them.
  • Test, duplicate and spam records can be excluded consistently.

Start with one dependable weekly review

Bring your lead records and campaign costs together in a short weekly review. Identify missing owners, stalled follow-ups and unclear sources before changing the budget. CRM development can help connect the records when spreadsheets no longer support the handoffs. Our AI automation guide explains how to start with a contained process and a human review point.

Choose one improvement for the next review: repair a broken success event, agree on qualification rules or record a reason for lost work. A useful tracking system should help the team decide what to do, not simply add more charts.

Want to see where your enquiries become booked work? Contact New Marketing Revolution for a review of your website enquiry flow, campaign measurement and CRM handoffs. Bring one real customer journey and the tools your Edmonton-area team already uses.

Common questions

What is the difference between a lead and a qualified lead?

A lead is an enquiry. A qualified lead meets your agreed checks, such as service fit, operating area and timing. Your team should document those checks so reports mean the same thing to everyone.

Can GA4 tell us exactly which marketing produced every sale?

No. Consent choices, device changes, offline conversations and attribution rules can leave gaps. Use analytics alongside CRM outcomes and financial records, and keep unknown sources visible.

Do we need a CRM to start tracking leads?

No. A carefully maintained shared record can support a small team. A CRM becomes useful when ownership, reminders, permissions or integrations become difficult to maintain.

Should a phone-link click count as booked work?

No. It records an attempt to call. Record the conversation and booking outcome separately, and keep the labels clear in your reports.

Further reading