Skip to content

What we build

Explore Vendrato

For enterprise teams

Book a free call

Based in the Philippines. Working worldwide.

All insights

What Should an Australian Service Business Track on Its Website?

Build a practical measurement plan that separates contact clicks, saved enquiries, booked calls and qualified opportunities without inventing conversions.

Track the steps that connect a website visit to useful business work: contact intent, a successfully saved enquiry, a confirmed appointment and the later outcome recorded by your team. Keep those stages separate. A telephone-link click does not prove a call connected, and a booking-page view does not prove an appointment exists.

Start with a short measurement plan before adding more dashboard charts. The plan should say what triggers each event, how to test it and who checks the result.

Choose the business question first

An illustrative Perth electrical service wants to know whether its website produces suitable enquiries within its actual service area. Total visits cannot answer that. The team needs website activity alongside records showing the requested work, location and next action.

The CRM can hold the customer details needed to qualify a request. The analytics report should describe the interaction without carrying those personal details. Google’s PII guidance prohibits sending information Google could use or recognise as personally identifiable information to Analytics.

Do not put email addresses, phone numbers or free-text enquiries into event labels, page URLs or custom dimensions. Review confirmation-page query strings as well as the fields you intentionally send.

Use a small event map

Interaction Meaning and test
Contact intent A visitor clicked email, phone or the booking link; verify the chosen method
Saved enquiry The receiving system confirmed a new request; verify the corresponding record
Appointment booked The booking provider confirmed an appointment; compare the calendar record
Qualified opportunity Staff confirmed the request fits the business; record this in the CRM
Won work The business accepted the job under its normal process; reconcile separately

Google documents recommended and custom events, and provides Realtime and DebugView for checking events. A developer should select the appropriate event names and parameters, rather than generating a different name for every campaign or customer.

For a saved enquiry, generate_lead is a useful recommended event to discuss with your implementer. Do not assign an invented dollar value just to make the report look complete. A real valuation model needs documented business assumptions.

Keep attempts out of the completion count

Ask what happens if the visitor double-clicks, the network times out or the calendar sends the same completion message twice. The implementation should follow a documented duplicate policy and distinguish an attempted action from a confirmed result.

An embedded calendar may live on another domain. Clicking its container or opening the booking page is not a reliable completion signal. Use the provider’s supported confirmation mechanism and test the actual appointment record. If that mechanism changes, the reporting must be checked again.

In the Perth example, a test with analytics consent granted and blockers disabled should create one test record and one completion event, not three conversions from opening, starting and submitting the form. Also test with analytics disabled: the enquiry should still reach the team even when no analytics event is received. Keep diagnostic events labelled and separate from genuine leads.

Read acquisition reports with their limits

Search Console clicks and Analytics sessions measure different things. Google explains the differences between Search Console and Analytics data, including consent choices, tracking blockers and time zones. Repeat visits can also affect what you see. Do not force the totals to match by changing event definitions.

Separate the main business website from demos, unrelated products and staff testing. For a business serving Australia remotely, inspect relevant landing pages and country data together. A large number of impressions for unrelated names is not evidence of demand for the service.

Use a consistent period, then record the filter and date range with the result. Small samples can swing sharply; avoid presenting a handful of visits as a dependable conversion benchmark.

Reconcile with the team’s weekly review

Choose a modest set of numbers: relevant visits, saved enquiries, qualified opportunities, held appointments and won work. Add the source of each number and note gaps. Analytics can describe online interactions; the team must still decide whether an enquiry was suitable and whether work was won.

Our CRM setup checklist helps define those operational fields. The tradie website guide connects measurement to the information buyers need before enquiring.

If you want help connecting website behaviour to real enquiries, explore Vendrato websites or book a project call. Bring one current report and one example of a completed enquiry so the measurement plan starts with evidence.

Your next chapter

Planning a digital project?

Show us your current website or workflow. We will discuss where to focus and what a project could involve.

Let’s talk about ithello@vendrato.com