The analytics events worth tracking for a service business

Most service businesses need about six events, not sixty: a qualified lead, a quote request, a call click, a booking, a form start, and a short list of key content views. Those six tell you whether marketing is producing work you can invoice, and everything past them is usually noise you pay for in maintenance. This article covers how to define that set, name it, push it into your CRM, and review it on a cadence a small team can actually keep.

Start at the sale and work backwards

The usual mistake is to open the analytics tool and start ticking boxes: scroll depth, video plays, outbound clicks, time on page. That gives you a dashboard full of numbers nobody can act on. Start instead with the last honest step of your sales process, the one where money changes hands, and walk backwards through the moments that reliably precede it.

For a service business that sequence is short. Someone finds you, reads enough to trust you, and then either phones, books a time, or fills in a form. Each of those three is a real commitment of the visitor's attention, and each maps cleanly to a row in your CRM. The reading step matters too, but only for the two or three pages that genuinely move people, not for every article on the site.

Write the list on paper first. If you cannot say in one sentence what you would do differently when an event's number goes up or down, it does not belong in the set. That single test removes most of what people track.

The short list of events worth tracking

Here is the set we start from for a service business, with the trigger and the decision each one supports. Adapt the names to your business, but keep the count near this size.

Two notes on that table. The qualified lead is the only event that needs a human or a rule to confirm it, which is exactly why it is the most valuable one you have. And booking_confirmed fires on confirmation because a click that opens a calendar tells you nothing about whether anyone chose a time.

Name events so they still make sense next year

Naming is the cheapest quality control in analytics and the most commonly skipped. Pick one pattern and apply it without exception:

• Lower case, words separated by underscores. No spaces, no capitals, no punctuation.
• Object first, then action in the past tense: quote_requested, not RequestQuote or Quote Form Success.
• One event name per meaning, with detail carried in parameters rather than in new names. Use form_started with a form_id parameter instead of contact_form_started, quote_form_started and careers_form_started.
• Never encode a page, a campaign or a date in the name. Those change; the meaning should not.
• Keep a one-line written definition for each event and each parameter, including the exact trigger. Store it where the marketing team and the developers both look.

That last point does the heavy lifting. When a number moves six months from now, the first question is always whether the business changed or the tracking changed, and only a written definition with a change log answers it.

An event you cannot define in one sentence is an event you will misread in six months.

Retire the vanity metrics

Vanity metrics are not wrong, they are simply not decisions. Sessions, page views, bounce rate, average time on page, follower counts and impressions all describe activity. None of them tells you whether to change the offer, the page or the budget. Keep them as context in a single traffic line if you like, but take them off the report you make decisions from.

Watch for two subtler versions. The first is the aggregated conversion count that mixes a newsletter signup, a careers application and a quote request into one number called "conversions"; it always looks healthy and it means nothing. The second is any event that fires on a button click rather than on the outcome, which quietly counts intent as success. Both flatter the report and misdirect the budget.

Trim by asking the same question of every metric on your dashboard: what would we do differently at a higher number, and what at a lower one? Anything with no answer gets deleted, not demoted.

Wire events into the CRM, in this order

An event living only in an analytics tool cannot be checked against reality. The point of wiring events into the CRM is that a lead's marketing source travels with it all the way to won or lost, so the report and the sales team describe the same world. Work through it in order:

1. Add hidden fields to every enquiry form for source, medium, campaign, landing page and referrer, populated from the first and last touch you can capture.
2. Pass those fields through the form handler into the CRM record so they are stored on the contact and the deal, not just in a notification email.
3. Generate a unique lead ID at submission, and send it as a parameter on the analytics event as well. That ID is the join between the two systems.
4. Define the qualifying rule in the CRM: which stage, owner action or set of field values means the lead counts as qualified. Fire qualified_lead from that change, not from the form.
5. Handle phone calls with tracking numbers or a logged intake question, so calls land in the CRM with a source like every other lead.
6. Test the whole chain with a real submission each time the site, the form or the CRM changes, and record the test in the change log.

If you only do one of these, do the third. A shared identifier turns two disagreeing reports into one auditable pipeline. Our analytics and CRO work normally starts here, because there is little point tuning campaigns against numbers the sales team does not recognise.

A reporting cadence a small team can keep

Reports fail from frequency more often than from content. Three rhythms are enough:

1. Weekly, ten minutes. Volume only: qualified leads, quote requests, call clicks, bookings, by source. You are looking for a break in tracking or an obvious swing, nothing more.
2. Monthly, an hour. Quality and progression: qualified rate, close rate by source, and the form start to submission ratio for each form. This is where you decide budget and page changes.
3. Quarterly, half a day. The definitions themselves. Has the service mix changed, is the qualifying rule still right, did any event stop firing, and is anything on the dashboard no longer earning its place?

Consent adds one standing item. Consent rules in the EU and, in Canada, Quebec's Law 25 mean a share of your traffic is never measured at all, so treat your event counts as directional and your CRM record as the count of record. Keep the two labelled clearly so no one compares them as if they should match.

How OlDevs helps

OlDevs has been building and measuring sites for service businesses from Vancouver since 2014. We define the event set with you, write the definitions down, implement the tracking and CRM plumbing alongside the site work our web development team already handles, and set up reporting your team can read without a specialist in the room. One accountable team, a working demo every week, and you own all the code, designs, accounts and IP at the end of it.

If your dashboard is full of numbers nobody acts on, a first call is usually enough to name the handful of events that would replace them. Request a quote and we will reply within one business day.