If your website shows a different telephone number after a Google Ads click, it may be doing exactly what your call tracking was designed to do. The important questions are whether the replacement is intentional, whether it reaches the correct business line and whether the reporting describes what actually happened.
Start by separating a number that looks unfamiliar from a call that goes somewhere wrong. The first can be expected. The second needs prompt investigation, especially when paid traffic is still reaching that page.
Why Google Ads can change your website number
A Google forwarding number sits between the caller and your business telephone number. Google uses it to measure calls generated by advertising, then routes the call to your business. The UK is included in Google’s current list of supported countries. See Google’s explanation of how forwarding numbers work.
That means two people can report different experiences of the same page: a customer arriving through advertising sees a tracking number, while a colleague checking the website through another route sees your usual number. This difference alone does not establish a fault.
Ask whoever manages your advertising and website to confirm which call-tracking system is intended to operate. If nobody can explain the replacement, investigate its source before treating it as legitimate.
Identify which kind of call you are measuring
Google’s current phone-call conversion setup separates calls made directly from adverts, calls from website visits and calls supplied through uploads. Within the website route, it distinguishes calling a number shown on the site from clicking a website call link.
These routes need separate checks. A number inside a search advert is not the same website element as the telephone link in your mobile header. Establish where the customer first saw the number and what they tapped.
Also check what the reported action proves. Google explains that tracking clicks on a mobile website number measures the clicks rather than the telephone calls themselves. A tap can open a dialler without producing a connected conversation.
Keep your investigation focused: are you trying to repair the visible number, the destination of the call or the conversion record? One can be correct while another is wrong.
Collect a repeatable example before changing anything
A useful fault report lets your developer reproduce the same journey. Record:
- The page address and where the visit started, such as an advert or a direct visit.
- The device, browser and approximate time, including the time zone.
- The number displayed on the page and the number placed in the mobile dialler.
- Which header, footer, contact section or floating call button you used.
- Whether the call rang, who answered and which team should have received it.
Include the visitor’s cookie choice as part of the test conditions. Compare like with like rather than changing browser, visit route and cookie choice together. Keep these notes within the team handling the repair; customer telephone numbers do not belong in a public support post.
If a caller reaches the wrong business, arrange an immediate review of the affected advert or landing-page route. Decide how to protect incoming enquiries while the fault is investigated, rather than leaving spend running without a confirmed working contact route.
Check the replacement and the mobile link together
Match the intended number and tracking configuration
Google’s website call-tracking instructions require the number being matched to correspond to the number on the page. Check the conversion ID and label too. For Google’s standard Tag Manager website-call tag, the guidance specifies national formatting without the plus sign; do not assume every installation method uses identical formatting.
Give your developer a list of the places customers can call from. Include desktop and mobile headers, the contact page, service pages and any sticky call button. Ask them to check each location against the intended destination, particularly if different branches or teams use different lines.
Test what happens after a tap
The same Google instructions say a clickable mobile implementation must replace both the displayed number and the number called by the link. Read the number in the dialler before placing the test call. A visually correct replacement does not prove the link underneath is correct.
For a button labelled “Call us”, make the destination part of your acceptance check even though the button does not display digits. Test the customer action itself, rather than approving a repair from a screenshot of the page.
Look for competing implementations
If you use a separate call-tracking provider, ask your developer to inspect its configuration alongside the Google implementation. Check for old plugins, embedded snippets and published tag-container versions as possible sources of number replacement.
This is a diagnostic check, not a reason to remove every tracking component. Document which system should supply the number, which business line should answer and who owns the configuration. Make a targeted change, then repeat the same journey.
Prove that the call reaches the right team
Arrange a short test while somebody can answer the intended line. For a business with several departments, “the phone rang” is not enough: establish that the right person or queue received it and that any normal greeting or menu worked.
Google’s website-call setup guide describes testing after an advert click and warns that the click is chargeable. Have your advertising manager coordinate any necessary live test. Avoid repeatedly clicking your own adverts as an informal troubleshooting method.
Use a simple acceptance sequence:
- Open the agreed customer journey on the target device.
- Check the visible number and mobile dialler destination.
- Place the call and confirm the receiving team.
- Note the time and outcome so the reporting can be checked.
- Repeat on the other important call entry points and confirm your normal direct contact route still works.
Google lists start time, duration, missed or received status, call source and campaign among the available fields in its Call details report. Compare the relevant record with your test notes. A reporting entry is useful evidence, but the person answering confirms the real destination.
A connected call is not automatically a conversion
For website calls measured through a Google forwarding number, Google allows a minimum call-length threshold in its website phone-call conversion tracking. Calls must meet that threshold to count as conversions. Check that setting before concluding that a connected call has gone missing from conversion totals.
Choose the threshold around how your business handles calls. A long conversation could still be unsuitable; a short call might resolve a genuine customer’s question. Treat duration as a measurement rule rather than proof of lead quality.
After repairing routing, review the next genuine enquiries with the team answering them. Are the calls reaching the correct service? Are they useful requests? Our guide to connecting conversion reporting with enquiries and sales explains how to carry that assessment beyond the call count.
Keep your permanent number separate
Google says its forwarding numbers belong to Google and can change or be reassigned. Do not copy one into your permanent website content, email signature, printed material or business listings. Use the business number you control for those purposes.
Ask for a brief handover record after the repair: the permanent number, intended receiving line, tracking provider, responsible person and test outcome. Include call testing when you change your telephone service or rebuild the website.
If your website number changes unexpectedly or paid enquiries are reaching the wrong line, contact BuzzBoost Digital. We can help review the website and advertising journey, identify the source of the replacement and agree how to verify a working call route.
Featured image: AI-generated editorial artwork, not a photograph of a real BuzzBoost office, client or result.
