You get more useful phone calls by putting a working number where the decision happens. Make the tap keep its promise on a real phone, match the prompt to the page, and answer.
Whether calling should lead depends on the visitor's task, accessibility needs and whether your team can pick up.
The aim is relevant, answered enquiries, not a bigger number in a click report.
Should your website prioritise calls, forms or bookings?
Lead with the route that completes the customer's task. But keep another route open for people who cannot or will not use it. Calls are not inherently higher intent, more valuable or more likely to book than a form.
A call is faster for the business when someone is there to answer and dispatch. A form is better when a useful answer needs a photo, a document or a scope first. Where customers do both, the site needs both. So the real question is which one leads on which page.
Situation | Useful primary route | Keep an alternative |
|---|---|---|
Urgent trade work | Calling, when staff can answer and dispatch | Real hours and coverage, with a route for when nobody is available |
Appointments | Whatever answers the task, such as checking availability or booking online | Phone and an accessible written contact. Not every clinic enquiry is urgent |
Detailed quotes | A short form that gathers scope, photos or documents first | A call for suitability questions, without a long form as the toll |
Professional services and B2B | A consultation booking or a project enquiry | Who the caller reaches and what the first conversation covers |
Ecommerce | Buying online | Phone support for complex purchases, reported separately from existing customer support |
Treat those rows as starting points rather than measured conversion rates. Urgent commercial services are not public emergency services and should not borrow their urgency.
The mistake to avoid is forcing one route on everyone. An urgent caller shouldn't be pushed into a form. A detailed enquiry shouldn't be pushed into a phone call that can't carry the information.
People who cannot hear well, cannot speak privately or simply prefer writing need a usable non voice route. A well built one is its own discipline. Our guide to website enquiry form design covers it.
A person's preferred or accessible channel can differ from the business's usual route. So the tree decides what leads, not what exists. An urgent trade that answers its phone lands on yes and yes. Our guide to web design for tradies sets out the site built around that answer.
Where should you place the number and call prompts?
Put the number where it helps the decision, not everywhere. A number after every paragraph reads as nagging. One that only lives in the footer is the opposite fault.
Our website audits show how often the number misses the first screen. Our audit sample is 100 website audits from May 2023 to September 2026. Of those, about 2 in 3 sites had no tap to call link in the first mobile screen. The number was missing, sat only in the menu or footer, or was plain text or an image.
SourceElev8d website audit sample, 2023 to 2026
That first fix costs almost nothing. It's a labelled call link in the first screen of every page where calling matters. Where the rest goes depends on the page.
Page or location | What to include |
|---|---|
Header and hero | A visible number or a labelled call link when calling matters, after the offer and real coverage are stated |
Service page | One service specific prompt beside the scope, suitability, proof or a resolved objection |
Campaign landing page | The ad's promise, the destination number and the availability, with one clear primary action |
Contact page and footer | A readable number, hours and time zone where relevant, branch or service routing and a written alternative |
Article page | A relevant service link or call prompt only where the reader has a practical need |
Sticky mobile bar | Consider it for an evidenced call led journey, clear of forms, keyboard focus, chat and cookie controls |
Match the wording to the conversation the page sets up. "Call about blocked drains", "Ask about availability", "Book by phone" and "Discuss your project" each tell the visitor what the call is for. "Contact us" is not wrong when it accurately leads to a choice of channels.
It is wrong as the only prompt on a page that exists to produce one kind of call.
Give people a reason to call before you ask them to. Proof is genuine reviews, relevant credentials, actual coverage, work examples and useful price factors. Use "Free quote", "same day", a review rating or a response promise only when it's true and qualified.
A promise beside the number is advertising like any other. ACCC guidance on false or misleading claims says information must be accurate, truthful and based on reasonable grounds. That holds whether or not you meant to mislead. The small print can't contradict the overall message either. So a "no call out fee" headline can't sit above a call out fee in the fine print.
Our guide to service page structure and copy shows how the prompt, proof and service decision sit together. For a campaign page where the call is the goal, read building a landing page that converts. It covers message match and the single action.
That is an example wireframe, not a screenshot. Replace every bracket with an accurate business fact. Give the real form clear labels and a way to reply.
How do you make calling easy on mobile and desktop?
A tel: link asks the device, or the application it has configured, to handle a telephone number. On a phone that usually means the dialler opens or a confirmation step appears. The link does not confirm that a call was placed, connected or answered.
On a desktop, the behaviour depends on whatever calling application is installed, if any. So the visible number has to stay readable and copyable.
The format comes from the tel URI standard. The standard treats a number starting with a plus sign and the country code as global. That global form is the safe destination for an Australian geographic number.
Use a real anchor link, never an icon only JavaScript control. Keep the number in the link text so screen readers and copy and paste both work.
<a href="tel:+6139000XXXX">Call the team on 03 9000 XXXX</a>
Because the X characters are placeholders, not digits, the example can't be dialled. Before implementation, replace the whole number with the verified business number. Change it in both the destination and the visible text. In international form, a geographic number drops the leading 0 after +61, as the example shows.
Don't assume every 13, 1300 or 1800 number converts or dials the same way from overseas. Dialling them can differ between mobile plans too. These numbers have no area code and no leading 0 to drop. So confirm the actual number and its routing with the provider, not whoever built the last website.
A written alternative can be as light as an sms: link to a mobile the business actually reads. The same caveat applies: desktop handling varies.
The sticky mobile call bar is conditional, not standard. Use a persistent call action where it serves the customer's task and the business can respond. Outside staffed hours it should change to the real option: leave a message, request a callback, book online.
Build it to the accessibility floor, then go past it. WCAG 2.2 sets an AA minimum target size of 24 by 24 CSS pixels, with exceptions. A main call button has every reason to be bigger. Our guide to website accessibility basics for Australian businesses covers target sizes and the criteria around them.
The bar also has to stay off whatever has keyboard focus. WCAG 2.2's focus not obscured criterion, also level AA, sets the minimum. When a keyboard user tabs to a link or field, the site's own content can't entirely hide it. A sticky bar that completely covers a focused form field fails the criterion.
Meeting either criterion does not make the page accessible. It makes it less broken.
Test it the way a visitor meets it:
cookie controls open
chat widget open
the on screen keyboard up
text zoomed
the page scrolled to its final action
A one thumb test helps too: hold the phone in one hand. Then see whether you can find and tap the number without shuffling your grip. Treat the one thumb test as a usability prompt, not a conversion benchmark.
If the content and the call route arrive slowly on a phone, that's a real problem. Our guide to why your website is slow covers the fixes. But no speed score guarantees a call.
How do you track calls and the pages behind them?
Start with what each method can show. One report line labelled "calls" can mean taps, attempts or answered conversations. Those are three different numbers.
Method | What it can show | What it does not prove |
|---|---|---|
GA4 phone_click event | Activations of a configured tel: link, with the page, device and other website dimensions | A placed or answered call, qualified intent or booked work |
Call tracking platform | Recorded attempts, routing and whatever source or session association the setup supports | Page or keyword attribution for every call, or a human conversation because a call is labelled connected |
Google Ads call tracking | Calls after ad interactions through forwarding numbers, taps on a mobile number, and imported call outcomes | Calls from other channels. A duration threshold is a conversion rule, not qualification |
CRM or a disciplined call log | Reason for calling, new enquiry or support, qualification, follow up and later outcome | Marketing attribution for calls whose source was never recorded |
One more source sits outside the website entirely. The call button on your Business Profile is counted in the profile's own performance report. The report shows clicks on the call button, with organic results and Google Ads combined. Keep those calls apart from website calls in the monthly numbers, because they never touch your pages. Our Google Business Profile guide covers how to read that report.
The website tap is the one you can measure yourself. Here's how we set it up: a Tag Manager click trigger catches the tap. A GA4 event tag then sends it as a custom GA4 event.
Use real links and the Click URL variable
Make every phone number a real anchor whose destination begins with tel:. Then enable the Click URL built in variable in Tag Manager so the trigger can read it.
Create a Just Links trigger
Choose the Just Links click trigger and set it to fire on some link clicks. Add the condition Click URL starts with tel:. Just Links tracks only HTML links. That's one more reason the number has to be a real anchor.
Send one GA4 event
Create a GA4 event tag on the existing Google tag, named phone_click. That's an example custom event name, not an automatic phone call report. If it should count as a key event, you mark it as one yourself.
Add safe context
Where it helps, pass a stable location parameter such as header, service body or sticky bar. Record the page as well. Register a custom dimension if the parameter needs to appear in reports.
Test every placement
Use Tag Manager preview and GA4's DebugView on each placement. Include dynamically replaced numbers and each consent state you support. Confirm one event per activation and remove any plugin or tag sending a duplicate.
Trigger type: Just Links
This trigger fires on: Some Link Clicks
Condition: Click URL starts with tel:
Never send any of these to GA4:
caller numbers
names
emails
recordings
transcripts
personal query strings
A missing event under a deliberate privacy or consent restriction is not a broken setup. The fix is never to bypass the restriction. Our guide to GA4 for small business covers the wider event plan and key events. It also covers the reports that read them.
If call outcomes also go into Google Ads, agree which single action represents the business goal. Google's page on primary and secondary conversion actions says primary actions drive bidding and the Conversions column. Secondary actions are for observation only, unless a custom goal includes them. Counting the same enquiry as a tap, a connected call and an imported outcome triples it.
Every phone button tap is reported as a new lead.
Phone taps show website intent. Call records show attempts and routing. Staff or CRM outcomes identify qualified enquiries and booked work.
Each layer answers a different question. So each gets its own line in the monthly report. That holds even where the records cannot be matched one to one.
How do tracking numbers fit with a stable business number?
Dynamic number insertion, or DNI, replaces designated phone displays on the site with tracking numbers. Each number is tied to a source or a visitor session. The calls route to the business and can be joined to whatever visit evidence the platform holds.
What DNI can attribute depends on the provider, the number pool, the integration, privacy settings and visitor behaviour. So nobody should promise you the exact source or organic keyword behind every call.
SourceElev8d explanatory model, October 2026
Ask any provider whether its script serves the same page to visitors and to bots. Google's spam policies define cloaking as showing users and search engines different content to manipulate rankings.
Some setups offer a main line only option instead. That trades attribution detail for simplicity. Either way, treat a vendor's documentation as its own claims. It isn't proof that a provider gives complete attribution or keeps your listings consistent. Whichever provider you use, the setup has to meet these requirements.
Requirement | What to do |
|---|---|
Permanent business number | Keep a business controlled main number in the business record that works when tracking does not run |
Designated replacements | Update the displayed number and the matching tel: destination together, in headers, body and sticky bars |
No crawler only trick | Never serve one number to crawlers and another to people. Check the rendered page, not the vendor's assurance |
Static contact details | Keep session pool numbers out of directories and schema, and label any static office number shown beside them |
Number and route control | Confirm the numbers reach the right branch, stay under business control and have a plan for a provider change |
Concurrent tracking | If Google Ads forwarding and a DNI script target the same number, agree ownership and test for conflicts |
Google's Business Profile guidelines require a number that connects to the location, under the business's direct control. Where possible, it should be local rather than a central call centre. It also shouldn't redirect callers elsewhere. So website DNI never rewrites the profile or the directories. They keep the stable number.
Our guides to local citations and directories and schema markup for small businesses cover where it must agree.
Separate website context from proven attribution
Report the page on which a phone link was activated as the click page. The visitor's landing page is a different field.
A platform may associate a later call with a session, source, landing page or last observed page. That depends on how it was built. So label the field you actually have. Don't claim a landing page report proves where someone saw or copied the number.
People dial manually from another device, come back later, use a saved number or decline tracking. Keep an unattributed category. Ask callers a simple source question where it is natural. Never divide all recorded calls by website phone clicks as if they were one matched funnel.
When the calls come from ads
In Elev8d's service accounts, calls are commonly 30% to 50% of leads, more for emergency trades. That's our observation, not a market statistic. It covers the 45 service accounts we managed from May 2024 to September 2026, all with call tracking.
Our guide to Google Ads call tracking covers the call types Google counts. It also explains the call length that makes a call a conversion. And it shows the number format Google's website call tag expects.
One Google Ads rule protects your stable number. Google forwarding numbers are the property of Google and can change or be reassigned at any time. So they never go into a listing, your schema or a letterhead.
What happens when someone calls, or you miss the call?
More calls are useful only when the business can handle them. So ask the operational questions before you add a single prompt:
who answers each branch or service line
what happens when the line is busy
where the missed call alert goes
who owns the callback
Check staffed hours, public holidays, time zones, overflow and the after hours route. Test the actual destination, not whether the dialler opens.
Distinguish a network connection, an IVR or a voicemail pickup from a conversation with the team. An IVR is the recorded "press 1 for sales" menu. Confirm the platform's status definition before you call anything an answered call rate.
A voicemail can still become a valid enquiry. A missed call is not automatically a lost sale. The "every missed call costs you $X" sum some vendors run assumes every caller would have booked.
For callbacks, record an owner, a realistic response window and whether it was completed. Do not promise "within the hour", "24/7" or same day availability unless operations can deliver it. Keep a written or booking route beside the phone.
Internal call reference: [reference, not public caller details]
Received time and relevant time zone: [time]
Destination and availability: [team, hours or overflow]
Assigned owner: [person]
Promised response window, if any: [verified expectation]
Callback attempted and completed: [times and status]
Outcome and next action: [qualified enquiry, support, other or unassessed]
Keep completed logs private. A returned call can be worth as much as an answered one. The Google Ads call tracking guide linked above covers automated missed call text back.
Recording is optional. Do not treat recording or AI transcription as necessary to count calls or judge outcomes. Get advice on the actual collection, consent, disclosure, access and retention arrangements if you use either. The same goes for the recording rules that apply where you operate.
The OAIC's guidance on consent to the handling of personal information covers consent in general. It doesn't deal with call recording. Most small businesses sit outside the Privacy Act. But some are covered whatever their turnover, as the OAIC's small business page sets out.
A disclosure message at the start of a call is not a universal permission formula. Our guide to privacy policy and terms for your website covers the site's data handling. That's context, not clearance to record anyone.
Use one set of definitions for the monthly review and keep them written down.
Measure | Definition |
|---|---|
Page phone action rate | Sessions with at least one phone_click on a page divided by sessions that viewed it |
Human answer rate | Attempts answered by staff divided by eligible attempts in the period |
Qualified enquiries | Unique enquiries meeting the stated service, location and suitability rules |
Booked work and value | Qualified enquiries matched to confirmed bookings or sales |
Each one carries conditions. The action rate counts sessions, not repeated clicks, with the same device, period and filters on both sides. The answer rate needs:
the hours defined
test and spam calls excluded the same way every month
unclassified missed calls kept in the denominator
voicemail reported separately
Qualified enquiries separate sales from support, wrong numbers and repeats. They also show unassessed outcomes rather than counting them as qualified. Booked work allows for delay and for the same person enquiring by form and by phone.
What should you test and improve first?
Baseline first, then fix anything broken, then test one thing. A dead tel: link is a fault, not an experiment. So is a wrong destination after number replacement. So is a missed call alert going to a departed staff member. They get fixed today.
After that, test one evidenced change: a placement, a label or a response process. Compare like periods and note campaign, staffing and seasonal changes.
At low volume, extend the observation and use direct task tests with real people. Don't declare a winner from a dozen calls. An increase in taps alone is not proof of more business. That's the whole point of the measures above.
SourceElev8d suggested improvement loop, October 2026
What should you check before you rely on the phone path?
Run these before a campaign, after a number change and after any plugin update. Three rows stop the campaign on their own if they fail, whatever the rest says. Those rows are display and destination, alternative route, and hours and routing.
Display and destination
The visible number and the tel: destination reach the intended branch, including after dynamic replacement
Real device activation
The label, link and dialler behaviour work on representative phones and on the supported desktop path
Keyboard access
The call link is reachable, visibly focused and never trapped or covered
Overlays and safe areas
Sticky bars, consent controls, chat, forms and the on screen keyboard remain usable together
Alternative route
A working form, booking or other written option remains available
Hours and routing
Normal hours, public holidays, time zone and the after hours destination are correct
Performance
The content and the call route appear promptly, with any real delay investigated
Failure state
The permanent business number stays usable if tracking scripts fail or never run
A site rebuild or a move to a new platform can break every row at once. So run the full launch list as well.
What we recommend at Elev8d
Fix the path before you pay for more traffic. Getting more calls to a line nobody answers is the most expensive improvement a website can make.
We'd work in this order:
Make every number a real tel: link that rings a person, on every page where calling matters. Fix any wrong destination the same day.
Settle who answers each line, the hours you can actually keep and who owns each missed call.
Count taps and qualified enquiries separately from the first week. That way, every later change is judged on enquiries rather than taps.
Only then move the number, rewrite the label or add a sticky bar, one change at a time.
If a quote needs photos or a scope first, we'd lead with a form or online booking instead. We'd do the same when nobody can answer in the hours you advertise. Keep the number visible either way, with honest hours beside it.
If the phone path passes every check and the right calls still don't come, stop tuning the phone. Find out why your website is not converting. Run our DIY website audit checklist across the rest of the journey in about 30 minutes.
When the evidence points beyond the phone path, it's time for conversion rate testing. Investigate what visitors actually do, then test changes properly.
We'll check your main pages on a phone and tap the number. We'll follow the call to whoever answers it. Then we'll tell you what we'd fix first.
FAQ
Can desktop visitors use a click to call link?
Sometimes. It depends on the calling app the computer has set up. That might be a video call app, a softphone or nothing at all. So report desktop taps separately from phone taps. Never count either as calls.
Do I need paid software to start measuring phone enquiries?
No. Pair a GA4 phone_click event with a disciplined call log. That gives you taps by page and outcomes by enquiry, with less attribution detail than a tracking platform. Pay for a platform when you need source level attribution across channels. You also need the volume to make it meaningful.
Should I replace my main business number to use call tracking?
No. Tracking numbers replace the display on your website. The main number stays everywhere else.
The question to ask before you sign is about porting. A provider may want your main number moved onto its platform. If so, get in writing how you take it back when you leave.
Next steps
Test the tap on your own phone today
Open your main service page on a phone and tap the number. Check where the call lands and who picks up. Then do it again with the cookie banner open. Whatever fails goes to the top of the list, ahead of any new campaign.
