For a local service business, a phone-button click is not a customer.
It does not tell us whether the caller got through, whether they were inside the service area, whether the company had the right product in stock or whether the enquiry became a paid job.
A WhatsApp click has the same limitation. It records an intention to start a conversation, not the commercial result of that conversation.
That difference matters because Google Ads uses the conversion actions we select to decide what kind of traffic to pursue.
If we ask it to generate phone and WhatsApp clicks, it will find people likely to click those buttons.
If we give it a consistent record of completed, paid jobs, we can gradually teach it to optimise closer to the outcome the business actually wants.
This is how I applied that approach to roadsidetyrefit.co.uk, a UK emergency mobile tyre fitting and puncture-repair business.
The lesson was not that phone clicks should never be tracked. In fact, they were useful during the launch of a new campaign. The important change was moving from those early, high-volume signals to qualified-job data once enough real outcomes had accumulated.
The problem with counting every contact action as a lead
Mobile tyre customers often need help immediately. They may call several providers, ask for a price and book the first suitable fitter. Others may be outside the coverage area, require a tyre that is unavailable or decide not to proceed.
Google Ads cannot see any of this from a telephone-link click.
At the beginning, our campaigns counted several actions as primary conversions:
- Phone-button clicks on the website
- WhatsApp-button clicks
- Calls made directly from Google Ads
- Paid jobs uploaded as qualified leads
This gave a new campaign enough conversion activity to start learning. However, it also meant that a five-second WhatsApp enquiry and a completed £150 job could both initially appear as successful outcomes.
The campaign could report a strong conversion rate while the actual number of paid jobs remained disappointing. That is the gap we needed to close.
What we counted as a qualified job
For this account, a qualified job was not merely a promising enquiry. It was a job that:
- Came from a Google Ads interaction.
- Was accepted by the customer.
- Was completed by the business.
- Was paid for.
Cancelled bookings and unconverted enquiries were not uploaded as qualified jobs.
This is slightly stricter than the everyday meaning of “qualified lead.” In Google Ads terminology, it may also be described as a converted lead because it represents the closed commercial outcome.
The label is less important than the definition being consistent: the bidding signal represented money received for a completed job.
Google recommends using lead-generation goals such as qualified leads or converted leads when they reflect meaningful offline progress.
Its guidance also recommends choosing a goal close to the final sale while maintaining sufficient, fresh conversion volume. See Google’s guidance for generating high-quality leads.
How we connected an advert click to a paid job
The tracking system recorded visits and contact-button interactions in a Google Sheet. When available, it stored the advertising click identifier, including the GCLID, alongside information such as:
- Interaction time
- Landing page
- Phone or WhatsApp action
- Click identifier
- Conversion time
- Completed job value
At the end of each day, completed jobs were matched to the recorded interactions. Each genuine job was then uploaded to Google Ads with its click identifier, conversion time and actual value.
Where a usable click identifier was unavailable, first-party customer information such as the telephone number could be used through a correctly configured enhanced-conversions-for-leads setup.
Google requires this data to be formatted and hashed according to its implementation requirements; a plain telephone number should not simply be inserted into a GCLID field.
Google describes enhanced conversions for leads as an upgraded offline import that supplements click identifiers with privacy-safe, hashed first-party data. See Google’s offline conversion import documentation.
The daily routine was deliberately simple:
- Review that day’s completed and paid jobs.
- Match each job to its Google Ads interaction.
- Record the actual amount paid.
- Upload the conversion with the correct conversion time.
- Exclude cancellations, quotations and conversations that produced no work.
Consistency was more important than sophistication. A basic process completed every day was more useful than a complex CRM integration that was delayed or only partially maintained.
The uploads were processed successfully without recurring import failures, which meant the campaign received a dependable qualified-job signal rather than a partial dataset.
We did not switch a new campaign straight to qualified jobs only
A newly created campaign has no history of paid-job imports. If qualified jobs are its only conversion goal from the first hour, the bidding system may have very little data from which to learn, particularly in a small location or low-volume market.
Our rollout normally followed three stages.
Stage 1: Build conversion volume
During the first weeks of a new campaign, phone clicks, WhatsApp clicks, calls from ads and qualified jobs were all available as primary conversion actions.
The campaign generally used Maximise Conversions or Target CPA through a portfolio bidding strategy. Where Target CPA was used, the portfolio strategy also allowed us to set a maximum CPC limit.
At this stage, the shallower actions provided immediate signals while the qualified-job action began accumulating real outcomes through daily uploads.
Stage 2: Remove shallow signals gradually
After the campaign had operated for a couple of months and had received a consistent stream of job imports, we reduced its dependence on contact-button actions.
Phone clicks, WhatsApp clicks and calls from ads were removed from the campaign goals one at a time. This prevented the bidding target from changing from a large volume of instant actions to a much smaller volume of delayed outcomes overnight.
Another successful approach was to create a new location-specific campaign, remove that location from the established campaign and launch the new campaign with qualified jobs as its only goal.
This worked best when the new territory was wide enough to generate sufficient demand.
Stage 3: Bid for paid jobs
In the mature configuration, the campaign used only the offline qualified-job action as its primary bidding goal.
Phone clicks and WhatsApp clicks could still be measured for diagnostic purposes, but they were not included in that campaign’s bidding goal. This distinction matters.
Google defines primary conversion actions as actions used in the Conversions column and for bidding when the associated goal is selected.
Secondary actions are normally observation-only, although actions placed inside a custom goal can still be used for bidding. See Google’s explanation of primary and secondary conversion actions.
For that reason, it is important to inspect the campaign’s actual goal configuration, not simply change an action to Secondary and assume it can no longer influence bidding.
What happened after we optimised for qualified jobs
The campaign did not automatically become restricted just because we replaced phone and WhatsApp clicks with a deeper conversion signal.
When the selected location had sufficient demand, Target CPA was realistic and the maximum CPC ceiling allowed entry into the necessary auctions, the campaign could start delivering from its first day in the qualified-job-only configuration.
The main change was the quality of traffic. We required fewer clicks to produce useful work because the campaign was no longer being rewarded for every person who merely opened a contact channel.
One 30-day roadsidetyrefit.co.uk reporting period produced:
| Result | 30-day figure |
| Google Ads clicks | 759 |
| Completed paid jobs | 60 |
| Uploaded job value | £5,440 |
| Click-to-paid-job rate | 7.91% |
| Average recorded job value | £90.67 |
| Recorded job value per click | £7.17 |
These figures are not presented as a controlled before-and-after experiment. Location demand, competition, bidding limits and customer urgency all change over time.
They are a real operational snapshot showing what became measurable once completed jobs, not contact-button activity, were used as the core outcome.
The most valuable result was not a prettier Google Ads conversion rate. It was that campaign reporting became connected to genuine work and revenue.
We could see whether advertising was producing paid jobs, calculate the value associated with those jobs and make decisions using commercial results rather than interface activity.
Fewer clicks were not necessarily a negative result
Advertisers are naturally concerned when traffic falls after a conversion-goal change. But the objective of a local lead-generation campaign is not to buy the largest number of clicks. It is to buy enough of the right clicks to generate profitable jobs.
Consider two hypothetical traffic patterns:
| Campaign behaviour | Clicks | Phone/WhatsApp actions | Paid jobs |
| Optimised for contact clicks | 300 | 75 | 15 |
| Optimised for qualified jobs | 210 | 38 | 18 |
This table is illustrative, not roadsidetyrefit.co.uk account data. The second campaign appears weaker if it is judged by clicks or contact actions. It is stronger if it produces more paid work from less traffic.
That was the practical improvement we observed: fewer low-value interactions and more jobs relative to the number of clicks received.
Target CPA worked without requiring Target ROAS
Because each completed job had a value, Maximise Conversion Value or Target ROAS was technically possible. It was not automatically the best strategy.
Target CPA remained effective when the immediate objective was to generate as many completed jobs as possible at an acceptable acquisition cost.
It also tolerated differences in job value without forcing a lower-volume campaign to learn both conversion probability and value patterns at the same time.
Google describes Target CPA as an automated strategy that sets bids to generate as many conversions as possible around the selected average CPA. It can be applied to a single campaign or through a portfolio strategy. See Google’s Target CPA documentation.
For this type of campaign, my preferred starting structure is:
- Target CPA or Maximise Conversions
- A portfolio strategy when a maximum CPC safety limit is needed
- A realistic Target CPA based on actual completed jobs
- Qualified jobs uploaded daily
- Actual job values recorded even when bidding is not yet value-based
Google cautions that bid limits can restrict automated optimisation. That is true, but high-CPC emergency-service auctions can also spend aggressively.
I therefore use the maximum CPC limit as a safety control and set it high enough for the campaign to compete, rather than using an artificially low ceiling.
Maximise Conversion Value can be tested after the account has enough accurate value data. It should not be treated as a required upgrade.
A campaign can respond very differently when its bidding objective changes, so delivery, job volume and revenue must be monitored after the switch.
What we checked when a campaign did not deliver
If a new qualified-job campaign had very low delivery for five days, we did not immediately conclude that offline conversions were the problem.
We checked two practical restrictions first.
1. Was the location too narrow?
A small postcode group may not generate enough eligible searches, especially when combined with exact keywords, restrictive schedules or limited service availability.
Our first response was often to widen the service area while keeping it commercially sensible. A larger location gave the campaign more auctions in which to apply what it had learned from the qualified-job history.
2. Was the maximum CPC too low?
Emergency mobile tyre searches can be competitive. If the maximum CPC limit prevented the campaign from entering valuable auctions, increasing the ceiling restored room for Target CPA to work.
The purpose of the limit was to prevent extreme bids, not to force every click below an unrealistic price.
We also reviewed:
- Whether the Target CPA was achievable
- Whether the correct qualified-job goal was selected at campaign level
- Whether imports were arriving every day
- Whether conversion times were accurate
- Whether recent jobs had enough time to appear because offline results are delayed
- Whether the campaign had sufficient geographic and keyword coverage
Why the gradual transition mattered
The approach worked because we treated conversion quality as a progression.
At launch, the campaign needed quick behavioural signals. Later, it needed commercial truth. Attempting to use only one of those stages for the entire life of the campaign would create a trade-off:
- Optimising indefinitely for phone and WhatsApp clicks provides volume but can reward weak enquiries.
- Optimising a brand-new, narrowly targeted campaign only for delayed paid jobs may provide too little initial information.
By uploading qualified jobs from the beginning, we built the deeper dataset while the early campaign was still using contact actions.
We could then remove shallow actions gradually instead of starting the measurement system on the day we wanted to change the bidding goal.
Google’s current guidance similarly emphasises choosing qualified or converted leads while maintaining sufficient conversion volume and fresh uploads.
As a general benchmark, Google recommends that the chosen action generate at least 15 conversions in the previous 30 days at account level.
That is useful guidance, not a guarantee: campaign size, conversion delay, territory and competition still affect performance.
Mistakes that can undermine this approach
Treating every caller as a qualified lead
If missed calls, price enquiries and cancelled jobs are uploaded as qualified, the new action recreates the same problem under a more impressive name.
Uploading jobs inconsistently
Uploading ten jobs one week and forgetting the next week creates an incomplete picture. Daily uploads kept the signal fresh and made account reporting more dependable.
Using the wrong conversion time
The conversion record should contain the correct time associated with the offline outcome and follow Google’s import requirements. Incorrect times can prevent attribution or place results in misleading reporting periods.
Removing all early signals too soon
A campaign needs enough qualified-job history before its shallow conversion actions are removed. We normally allowed the new campaigns to gather data for a couple of months and then made the transition gradually.
Launching in an area with too little demand
A qualified-job-only campaign cannot create search volume that does not exist. Starting with a reasonably broad service territory improved its chance of delivering.
Setting a restrictive Target CPA and CPC limit together
An ambitious Target CPA combined with a low maximum CPC can leave the bidding system very few auctions in which it is allowed to compete.
Changing several major settings at once
Changing the goal, bidding strategy, Target CPA, CPC ceiling, location and budget together makes the result difficult to diagnose. Gradual changes produce clearer evidence.
The framework I now use for local lead-generation campaigns
The process can be summarised as follows:
- Track phone clicks, WhatsApp clicks and calls from ads from launch.
- Capture the click identifier and interaction time wherever possible.
- Upload every completed, paid job daily with its actual value.
- Build qualified-job history while the campaign uses higher-volume actions.
- Remove shallow conversion actions gradually after sufficient data accumulates.
- Use qualified jobs as the mature campaign’s primary bidding goal.
- Start with Target CPA or Maximise Conversions; test value bidding only when the data supports it.
- Use a sensible maximum CPC safety limit through a portfolio strategy where appropriate.
- If delivery is weak after approximately five days, review geographic reach, CPC ceiling, Target CPA and goal configuration.
- Judge performance by completed jobs, job value and profit, not by button clicks alone.
The wider lesson
Google Ads cannot optimise for a business outcome it never receives.
If the platform is told that every phone-button or WhatsApp click is a success, it will pursue more people likely to perform those actions. That may increase the conversion count without improving revenue.
When roadsidetyrefit.co.uk began feeding completed paid jobs back into Google Ads consistently, we could move the campaign towards a much more valuable objective.
Phone and WhatsApp tracking remained useful for understanding the journey, but paid jobs became the signal that determined success.
The result was not simply “more conversions.” It was better alignment between advertising activity and the work the business actually completed: more useful jobs from fewer clicks, clearer revenue reporting and bidding decisions based on customers rather than contact-button activity.
If your Google Ads account reports plenty of calls or form submissions but you cannot identify which enquiries become paying customers, I can help you audit the conversion setup and build an offline lead-quality process.
Frequently Asked Questions
Should phone clicks be primary conversions in Google Ads?
They can be useful as primary actions during the early stage of a new lead-generation campaign because they provide faster and higher-volume signals.
Once sufficient qualified-job data has accumulated, phone clicks can be removed from the campaign’s bidding goals and retained for observation.
What should count as a qualified lead?
The definition should represent meaningful commercial progress and remain consistent. In this roadsidetyrefit.co.uk implementation, only completed and paid jobs were uploaded. Enquiries, quotations and cancelled bookings were excluded.
Can Google Ads optimise using offline jobs?
Yes. Advertisers can upload offline outcomes using click identifiers and, with the appropriate enhanced-conversions-for-leads configuration, hashed first-party customer data. The qualified or converted lead can then be selected as a campaign bidding goal.
Should I use Target CPA or Target ROAS for qualified leads?
Target CPA is suitable when the main objective is generating completed jobs at an acceptable acquisition cost. Target ROAS or Maximise Conversion Value may be appropriate when job values are accurate, sufficiently frequent and materially different.
Value bidding is not mandatory simply because values are available.
How often should offline conversions be uploaded?
Uploads should be consistent and reasonably fresh. roadsidetyrefit.co.uk reviewed and uploaded completed jobs at the end of each day so that bidding and reporting received a dependable stream of outcomes.
Why did my qualified-lead campaign stop receiving impressions?
Common causes include a location with insufficient search demand, an unrealistic Target CPA, a maximum CPC limit that is too restrictive, delayed or missing imports, or an incorrectly selected campaign goal. These restrictions should be checked before assuming the offline conversion action itself is responsible.
Join the discussion
Comments