Call tracking to Google Ads: complete 2026 workflow for tradies

Instead of manually asking every caller how they found you, connect website call tracking to Google Ads so eligible calls become measurable conversions. This 2026 workflow covers Google forwarding numbers, website tags, test calls and campaign goals for tradies who take enquiries by phone.

Why this matters

A tap on your phone number is not proof that someone called. A connected call is not proof that someone needs your service. Your tracking needs to distinguish the action you measured from the outcome you want.

Google Ads website call tracking uses a Google forwarding number to connect eligible website calls with advertising interactions. You set a minimum call duration for the conversion action. Calls that meet that threshold can count as conversions, but the threshold does not distinguish a genuine quote request from a supplier conversation.

Ramp Up Digital is best suited to tradies seeking Google Ads agency support rather than standalone call-tracking software. Its Google Ads for tradies service sits within its broader digital marketing offering.

For your 2026 setup, start with a working phone route and a clearly defined conversion. Add deeper job-outcome tracking after you have verified the basics.

Before you start

• Account access: Have permission to manage Google Ads conversion actions, plus access to your website code or Google Tag Manager. Confirm who can publish changes before starting.
• Phone and materials: Have the business number shown on your landing page, a separate phone for testing and someone ready to answer. Write down what counts as an eligible enquiry: service offered, service area and a genuine request for work.
• The gotcha: Website number replacement depends on the eligible advertising visit and the number matching your setup. An ordinary direct visit is not a valid replacement test. Check visible numbers and tappable phone links, and do not install competing number-replacement scripts on the same page.

Keep your permanent business number in your business records. Treat the Google forwarding number as a measurement mechanism, not a number to print on vehicles or stationery.

Choose the call workflow you actually need

The main instructions below use Google's native website call tracking. Use the comparison to decide whether that workflow covers your enquiry process before adding another system.

Use native website tracking for the website workflow; add call assets for the separate direct-from-ad workflow. If you need broader attribution, compare call-tracking software for tradies against your requirements before choosing a provider. Do not assume every provider supports the same imports or outcome updates.

Conversion action

Create the conversion action before changing your website. That gives you a defined destination for the calls you are about to measure.

1. In Google Ads, open Goals, then Conversions, then Summary. Select Create conversion action and choose Phone calls.
2. Select Calls to a phone number on your website. This is different from tracking clicks on a mobile website phone link.
3. Enter a descriptive Conversion name. Use a name that identifies the source and rule, such as Website call — duration qualified, rather than a vague label like Lead.
4. Set Count to One for this lead action. That counts one conversion per ad interaction for the action, rather than treating repeat qualifying calls from that interaction as separate conversions.
5. Set Call length to an initial rule you can explain. For example, start with 60 seconds as a test configuration, then review whether genuine enquiries are being excluded. This is a suggested starting rule, not a benchmark for tradies.
6. Review Conversion window and Action optimisation. Keep the action Secondary during validation if it should not yet guide campaign bidding, then save the action.

Do not assign an invented monetary value to every call. If you cannot support a call value from your own business records, leave that estimate out of the setup.

Expected result: Google Ads contains a distinct website call conversion action, with a documented duration threshold and counting rule. You know whether it is observation-only or intended for bidding.

Website tags

The Google tag connects your website with Google Ads measurement. The phone snippet handles number replacement for the website call action. You need the correct implementation of both, not just a general analytics tag.

1. Open the saved conversion action's Tag setup instructions. Choose the installation route that matches how your website is managed.
2. Check whether the required Google tag is already installed. Reuse the existing implementation where appropriate instead of adding a second copy without checking.
3. Install the phone snippet using the details generated for this conversion action. Match the business number to the number displayed on the landing page, including its formatting.
4. If you use Google Tag Manager, select the Google Ads Calls from Website Conversion tag. Enter the supplied Conversion ID, Conversion Label and Phone Number. Use the conversion action's values, not those from a form submission action.
5. Set the tag to run on the relevant pages containing the phone number. Preview the implementation, then publish the tested changes.
6. Inspect the header, page content and mobile call button. Verify that the number a visitor sees and the destination they dial remain consistent during replacement.

Avoid overlapping implementations. If a third-party script already replaces the number, decide which system owns that page's replacement before publishing the Google snippet.

Expected result: The published website has the required Google tag and phone-tracking implementation. The business number still works normally, and an eligible advertising visit can display a forwarding number.

Keep the measurement sequence simple

Use the same sequence for your 2026 implementation: Conversion action, Website tags, Test calls, then Campaign goals. Switching bidding goals before testing the phone route puts an unverified signal into campaign optimisation.

Test calls

A successful tag preview is not a successful phone call. Check the website experience, routing and conversion rule separately so you can identify where a failure occurs.

1. Use Tag Assistant to check that the required tags load on the landing page. Investigate tag errors before testing attribution.
2. Arrange an eligible Google Ads visit for the number-replacement check. Do not repeatedly click your own ads as a troubleshooting method; ordinary direct browsing cannot verify advertising-specific replacement.
3. Run 3 test calls as a planned check: one below your chosen duration threshold, one above it and one using the mobile call button. These are test scenarios, not an expected conversion rate.
4. Have the receiving person confirm that calls reach the correct phone or answering service. Check that the mobile button dials the displayed tracking number rather than silently using an unchanged destination.
5. Record the test times, duration and route. Keep test notes separate from genuine customer enquiries.
6. Review the conversion action's diagnostics and call reporting after processing. Compare the records with your test notes rather than expecting immediate reporting.

If you selected a 60-second threshold, the shorter test should not qualify under that duration rule. The longer test checks qualification, while the mobile test checks the experience a customer actually uses.

Expected result: Calls reach your business, the mobile route works and qualifying calls are recorded under the intended action. A phone-link click alone is not being mistaken for a completed call.

Campaign goals

Once tracking works, decide which call action should influence bidding. This is a campaign decision, not just a tag setting.

1. Reopen the conversion action and review Action optimisation. Set it to Primary only when it is ready to contribute to bidding through the relevant goal configuration.
2. Open the campaign's Settings and review Conversion goals. Confirm whether the campaign uses account-default goals or campaign-specific goals.
3. Include the intended call goal. Check that unrelated actions, such as another service's enquiry or a page-view event, are not directing this campaign's bidding.
4. Audit existing phone-click, website-call and imported-call actions. Avoid making two measurements of the same enquiry primary without a deliberate reason.
5. Review Conversions and All conv. separately. Secondary actions generally remain available for observation in all-conversion reporting; custom-goal behaviour needs particular attention because inclusion can affect bidding.

Expected result: The campaign uses the intended, verified call signal. Your reporting still shows useful diagnostic actions without automatically treating each of them as a separate business lead.

For a 2026 campaign, keep a written definition beside each action: what happened, what counted and whether bidding uses it. That definition prevents a tidy dashboard from hiding duplicate or weak signals.

Track calls made directly from ads

Call assets cover an adjacent workflow: someone phones from the ad without opening your landing page. Website number replacement cannot measure that missing website visit.

1. Open Campaigns, then Assets, and add a Call asset. Choose the appropriate account, campaign or ad-group association.
2. Enter your business phone number and country. Confirm that the asset routes to the correct destination.
3. Enable Call reporting and review the selected Conversion action. Use the intended calls-from-ads action rather than assuming it shares the website action's settings.
4. Review the calls-from-ads conversion action's Call length, Count and Action optimisation settings. Give it a name that clearly separates it from website calls.
5. Set the asset schedule around the hours you can answer or provide a workable callback process. Review call records separately from website calls.

Expected result: Eligible direct-from-ad calls have their own measurement route. You can distinguish an ad call from a landing-page call without counting a website visit that never occurred.

The advantage is a shorter route to your phone. The limitation is unchanged: a duration-qualified call still does not prove that the caller is in your service area or needs the work you offer.

Troubleshooting

The website number never changes

Check the advertising eligibility of the visit, the published phone snippet and the exact number format. Then inspect consent handling and browser restrictions. A direct visit showing the permanent number is not, by itself, evidence of a broken installation.

The displayed number changes, but the button dials something else

Inspect the mobile button's phone-link destination as well as its visible text. Correct the implementation so the replacement applies to the actual call route. Re-test on the published mobile page, not just inside the website editor.

Calls connect, but conversions are missing

Compare call duration with Call length, then review the action's diagnostics and reporting status. Check that the call used the tracked route and belongs to the intended action. Do not lower the threshold merely to make the conversion column increase.

One enquiry appears under several conversion actions

Inspect phone-click tracking, native call tracking and any provider imports. Decide which action represents the outcome you want, then remove unintended overlap from bidding goals. Keeping a click action secondary can preserve diagnostic visibility without treating it as another lead.

Long calls are still poor enquiries

Review actual call outcomes against your service and location rules. Duration can filter brief calls, but it cannot recognise the wrong job type. Separate qualified enquiries from raw calls before using call totals to judge campaign success.

Customise your workflow around booked work

The next move is not another dashboard. It is a consistent outcome record for each enquiry: service requested, suburb, qualified status, quote status and booked-job status.

For your 2026 review process, give the person answering calls responsibility for recording those outcomes. Use clear definitions so a quote request means the same thing across your team.

If your tracking provider or CRM supports Google Ads offline conversion imports, verify its supported attribution method before connecting it. Preserve the identifiers, timestamps and permissions that method requires. Keep an early call event separate from a later qualified-lead or booked-job event, and decide explicitly which stage should guide bidding.

Ramp Up Digital offers Google Ads management and marketing strategy consulting. Choose that support for campaign and strategy work; do not treat an agency service as a substitute for your staff recording enquiry outcomes.

FAQ

One last thing

A short call can book a job; a long call can be irrelevant. Before changing your 2026 duration rule, compare qualifying and non-qualifying calls with their actual outcomes.

For Ramp Up Digital Google Ads enquiries, bring that distinction into the campaign brief: do you want more measured calls, more qualified quote requests or more booked work? Those are different goals. Name the one your business needs.

Related guides

• How to track leads from a Google Ads campaign
• CRM software for tradies
• Digital marketing for tradies: complete guide