How to set up call tracking for a Google Ads campaign

A phone click is not a booked job. A connected call is not automatically a qualified lead. A long call is not automatically revenue.

Call tracking connects the ad interaction to the call path, so you can see which keywords, ads, campaigns, and landing pages produce phone activity. The business record then tells you whether that activity became a qualified lead, a booked job, finished work, and confirmed value.

• Track the call, then track what happened.Google identifies where the call came from; your CRM, calendar, or dispatch log records whether it booked. Join the two before judging cost per booked job.
• Call length is a filter, not a quality signal.A minimum duration removes misdials, but a long call can be irrelevant and a short one can book. Set the threshold from your own call history.
• Test before launch.Make a real test call through every route the ad can send, and check it lands as the right conversion.

The setup has five decisions: which call interactions you want to measure, which system collects the event, what counts as a conversion for reporting or bidding, how the call gets reconciled with the business record, and how consent, privacy, and data handling are managed.

Phone calls are an important conversion path for many local-service businesses. That is a reason to measure them properly, not a licence to quote a percentage nobody can source.

The call path, end to end

The four call paths, compared

Most accounts need a combination, not a single path: call assets for the ad itself, website-call tracking for the landing page, and imported outcomes when a CRM can send bookings back. Choose by the question you need answered, and reconcile every path in one ledger so the same client is never counted twice.

Google describes several ways to track phone-call conversions: calls from ads, calls to a website number, clicks on a mobile website number, clicks on call ads or assets, and imported call conversions. Four of those are architectural choices an owner actually makes.

Those descriptions come from Google’s own documentation for call assets, call campaigns, website-call tracking, and imported call conversions.

Choose the path that matches the question. If you only need to know whether someone clicked the phone link, mobile click tracking may be enough. If you need to know which calls became work, imported outcomes are usually the stronger path when the call system and CRM support them.

In many local-service accounts the correct answer is not one path. It is call assets plus website-call tracking plus call-system records plus offline outcome reconciliation. The question is not which path creates the most calls. It is which combination lets the business identify a real client, answer the call, book the work, and measure the result without double-counting.

Whichever combination you run, the capability boundaries are the same decision read one level deeper:

A platform call conversion and a booked job are different records.

Google forwarding numbers and Dynamic Number Insertion

A Google forwarding number replaces the site number for ad visitors, routes to the real business line, and reports the call with its source. Test the replacement on every page that shows a number, then call it and reconcile the record; a replacement proves the logic ran, nothing more.

When supported in the account and country, Google forwarding numbers can help measure calls from ads and calls to a phone number on a website, and Google’s website-call process can dynamically replace the website number for a visitor who arrived after an ad interaction.

The visitor should still reach the real business number. The tracking number is a measurement layer, not a new customer-service number to publish without checking the implementation.

1. Create the website-call conversion action in Google Ads

   Name it by outcome and source before anything is installed.

2. Install the Google tag, or configure it through Tag Manager

   Then add the phone snippet or compatible website-call tag.

3. Enter the exact number displayed on the site

   Formatting differences are a common cause of a replacement that silently never runs.

4. Verify that the number changes after an eligible ad visit

   Confirm the coverage across every page that displays a number, not just the landing page.

5. Call the displayed number from a test device

   Confirm the business phone rings, the right person answers, and the caller ID or tracking record is sensible.

6. Confirm the record appears where you expect it

   In the Google Ads call details, the call platform, or both.

7. Reconcile the test call against the call log

   If the owner could not identify this call next month and mark it booked or not booked, the setup is incomplete.

Google notes that website call tracking needs a website you can edit and an eligible country for forwarding numbers, and documents implementation considerations for multiple phone numbers and number formatting. If the site shows several numbers on one page, do not assume the default implementation tracks all of them. Test each one, or use a system designed for the actual structure.

A number replacement proves that the replacement logic ran. It does not prove that the call connected, that the request was relevant, or that the caller booked.

Choosing between native measurement and a third-party system

There is no universal best tool, and no ad-spend figure that decides it for you. Start from the business question and the evidence you need.

Define the event before installing anything

Write each event’s definition and its limitation before any code is installed: a click is not a call, a connected call is not qualified, and a booked job is not revenue. Set weak events secondary and reserve the main conversion for the deepest outcome you can reliably measure.

Write down what each event means, and what it does not prove.

One call can create more than one record in a tracking system. Decide how duplicates, transfers, missed calls, repeat clients, and callbacks are handled before the first report.

Google says main conversion actions are reported in the “Conversions” column and can be used for bidding, while secondary actions are generally observation-only and appear in “All conversions.” Do not set a weak call event as main merely because it is easy to generate.

Duration thresholds are proxies, not truth

A minimum call length is a filter, not a quality signal. It removes short misdials and menu calls, but a long call can still be irrelevant and a short call can still book. Set the threshold provisionally from your own call history, name the conversion action after what it records, and review it against real booked and unbooked calls.

Google allows call conversions from ads and website calls to use a minimum call length, and calls shorter than the selected duration are not counted for that conversion action. Google’s call-reporting guidance supports counting calls of a specified duration as conversions and using automated bidding to increase the likelihood of those conversions.

That makes duration a filter. It does not establish that every call above the threshold is valuable, or that every short call is worthless. A 10-second call may be someone who reached the wrong extension. A 90-second call may be a quote request that never books. An emergency caller may need less time than a replacement prospect.

Do not copy a threshold from another trade. Choose a provisional one from your own call history, the greeting and menu length, staff knowledge, and the outcome you are trying to approximate. Google suggests reviewing call history, asking staff what a high-quality call generally looks like, and accounting for automated menus and greetings.

Then review it against real calls.

If a duration rule is in use, name the conversion action after what it actually records, a call-duration conversion, not after a booking the business record has not confirmed.

Google’s current call-measurement documentation also says call reporting can use AI analysis of recordings to identify high-quality leads, with duration as a fallback when recording is unavailable, and says call recording eligibility is currently limited to calls where both parties are in the United States or Canada, governed by supplemental terms. Do not present AI call qualification or recording as universally available, and do not build a tracking plan that depends on recording the business cannot lawfully or operationally use.

Call classification owners will actually complete

A useful call log is short enough to finish and detailed enough to decide from.

Use fixed fields and a short note for exceptions. Do not ask the call handler to write an essay.

A call becomes a booked job only when the business’s booking definition is satisfied: the client is a real service opportunity, the service and location fit, scope or price has been discussed enough for the business’s process, and a date, time, or defined commitment is recorded. A request for information with no appointment is not a booking.

Qualified-call rate = qualified calls ÷ tracked calls
Booking rate from qualified calls = booked jobs ÷ qualified calls
Cost per booked job = defined attributable acquisition cost ÷ confirmed booked jobs
Cost per finished job = defined attributable acquisition cost ÷ finished jobs

State the denominator. “Cost per phone lead” can mean all calls, calls above a duration, answered calls, qualified calls, or owner-confirmed leads. Those are four or five different numbers wearing one label.

A worked call reconciliation

A campaign spends $1,000.00 during a defined month and produces 20 tracked calls.

The $1,050.00 estimated contribution is the figure to compare against the defined acquisition cost. The $3,000.00 revenue line is not payback, and the 20-call line is not a lead count. If you stop at “20 calls” you have measured activity. If you can show 20 calls, 11 qualified, 6 booked, 5 finished, $3,000.00 confirmed revenue, and $1,050.00 estimated contribution at the stated margin, you have a business record with visible evidence boundaries.

Offline conversions and CRM reconciliation

If the business tracks calls in another system and records sales or other valuable actions, Google says it may create an imported calls conversion action. Google’s offline conversion documentation explains that a click or call can begin a customer journey that ends in an offline sale, such as at the business or over the phone.

A stronger implementation sends later events back: qualified lead, booked job, finished job, paid job, or a value-bearing outcome whose value definition is documented. For each one, document:

• The event name and the event date.
• The source identifier or matching method.
• The value definition.
• The attribution window.
• Whether repeat clients are excluded.
• The main or secondary setting.
• The correction and deduplication process.

The import is not a substitute for the Ledger. A platform can report an imported conversion. The owner still confirms the booking and the revenue.

Ask one question of the whole system every month: could the owner identify a given call next month and mark it booked, not booked, finished, or unknown? If not, the tracking is incomplete even when the platform shows a conversion.

Business hours, routing, and the numbers nobody documented

Google says call assets can be configured to show only when the business can accept calls. An ad schedule is not the same as call coverage. A business that advertises calls at 9 p.m. and cannot answer them has created a measurement problem and a customer-experience problem at the same time.

For every phone path, test business hours, after-hours behaviour, weekends, holidays, voicemail, missed-call alerts, call forwarding, recording rules, tracking-number display, caller ID, and dispatcher or answering-service routing.

Google also says that when location assets and call assets are both used, ads featuring specific business locations may direct calls to numbers associated with those locations rather than the number set in the call asset. So document every number in play: call-asset number, location-asset number, website number, Google forwarding number, tracking-provider number, main business number, and which system owns the call record for each. If different numbers route to different teams, that belongs in the booked-job reconciliation.

The pre-launch test path

Reporting may not be immediate. Record the test time, allow for the platform’s processing behaviour and the conversion window, and do not declare the setup sound because a number changed and something appeared soon after. Use a controlled route for testing so you do not create accidental chargeable clicks or phantom leads.

Troubleshooting

Common failure modes

Counting every call click as a conversion. A click on a phone option is not a connected call or a booked job. Name the event for what it records.

Tracking website calls but not the number path. If the user clicks the ad, visits the page, and calls a number that was never replaced or measured, the source attribution is gone.

Using call duration as lead quality. The caller may still be outside the area, asking for a service you do not offer, or unable to book.

Running calls outside coverage hours. The platform can generate demand the team cannot answer. Review missed calls and callback outcomes.

Double-counting one client. A person may click a call asset, visit the site, call the main number, submit a form, and call again. Deduplicate the journey before counting booked jobs.

Comparing paths with different service intent. Emergency calls, scheduled estimates, maintenance, and replacement work should not be compared without service-line context.

Call data and privacy

Call tracking may involve phone numbers, caller details, recordings, transcripts, locations, and CRM outcomes. Tell users what data is collected and how it is used, and follow the applicable consent, recording, retention, access, and data-sharing requirements. Google states that advertisers must provide clear information about data collection and get consent where needed by law or applicable policy.

Do not record, transcribe, upload, or share calls merely because a tool makes it possible. Use the least data needed to reconcile the job, and confirm that staff and clients receive the needed notice.

How to judge call-tracking quality

A setup is not judged by the number of calls it reports. It is judged by the evidence path.

If the numbers still do not reconcile after this, the next step is the conversion tracking audit, which works through duplicate counting, count settings, and reporting lag in order.

What to do next

Once calls are tracked end to end, run the tracking checklist to confirm nothing else in the chain is undercounting, then put the numbers to work with the CPBJ calculator.