Framework · conversions · measurement · framework
Decide which calls, forms, messages, bookings, and offline outcomes to count as Google Ads conversions, and how to choose primary versus secondary actions.
Count the deepest outcome the business can define, record, and send reliably. The mistake is counting the easiest event and then calling it the business result.
The short answer
A page view is not a lead. A button click is not a conversation. A form submission is not automatically qualified. A phone call is not automatically a booking. A booked job is not automatically completed or paid. The right conversion to count is the deepest outcome the business can define, record, and send reliably: a qualified enquiry, a booked job, a completed job, or a paid job, and it should match the decision the campaign is supposed to help make.
Google’s documentation describes qualified leads as Google-generated leads that have been further qualified offline in a CRM or internal system, and converted leads as leads that have completed a chosen step in the lead-conversion process, typically offline, such as a sale, closed deal, or other defined conversion step. This page feeds every other tracking page: get the definition right here, and the audit, the checklist, and the call-tracking setup all have something honest to measure.
The useful sequence runs from the shallow platform event to the deep business outcome.
| Stage | Example | Where it usually lives | Always the primary conversion? |
|---|---|---|---|
| Ad interaction | Click, call interaction, message interaction | Google Ads | No. It is an activity signal. |
| Contact | Form, call, message, booking request | Google Ads, phone system, CRM | Not automatically. Check quality. |
| Tracked enquiry | Deduplicated contact tied to a source | CRM or lead log | Sometimes, if reliably meaningful. |
| Qualified enquiry | Service, area, intent, and basic fit confirmed | CRM or internal system | Often a stronger candidate where reliably recorded. |
| Booked job | Date, time, or defined commitment recorded | Calendar, CRM, dispatch | Strong outcome; practical as a bidding goal only when data is reliable. |
| Completed job | Work delivered | Dispatch or job system | Stronger outcome but often delayed. |
| Paid job | Payment or collection confirmed | Invoice or accounting system | Strong economic outcome but may arrive too late or too sparsely for bidding. |
| Estimated contribution | Revenue multiplied by stated margin | Profit Ledger | Owner decision metric; not automatically known by Google. |
The “best” conversion is not the deepest theoretical event. It is the deepest event the business can measure consistently enough to use responsibly.
Different campaigns may have different intended outcomes, so decide what each campaign should learn from before you set a single action to primary.
| Campaign purpose | Possible primary goal | Useful secondary observations |
|---|---|---|
| Emergency phone demand | Qualified call or booked job where data is reliable | All calls, missed calls, service fit, area fit |
| Scheduled estimate requests | Qualified enquiry or estimate appointment | Form submit, call, quote issued, landing-page engagement |
| High-ticket replacement | Qualified consultation, estimate, or converted lead | Calls, forms, quote requests, booked site visits |
| Recurring service acquisition | Activated recurring customer or qualified lead | Trial or first service, plan acceptance, retention |
| Existing CRM optimisation | Qualified or converted offline lead | Early contact and intermediate stages |
| Measurement repair | No scaling goal until tracking is validated | Test events and diagnostics |
Do not set every event as primary merely because it appears in a report. Google says primary actions are included in the Conversions column and can be used for bidding when the standard goal is used, while secondary actions are generally observation-only and appear in All conversions. A phone call can be a primary conversion for one campaign and a secondary diagnostic event for another. The label is not a judgment about whether calls matter; it is a decision about what the campaign should learn from.
Google can measure calls from ads and websites. Website call conversion tracking can use Google forwarding numbers to replace the displayed business number after an eligible ad interaction, and Google says it can help identify which keywords, ads, ad groups, and campaigns lead to calls. Google also allows calls from ads to be counted when they last longer than a minimum duration selected by the advertiser, and its current call-measurement documentation describes AI analysis of eligible call recordings for high-quality leads, with duration fallback when recording is unavailable.
A workable definition is a call that reaches the business through the intended tracking path and satisfies the documented diagnostic rule, then receives a separate owner classification for service fit, qualification, booking, completion, and payment. Do not define a phone conversion as “every ring,” and do not treat a duration threshold as proof of a booked job. Review duration buckets against actual outcomes rather than trusting the length alone.
| Call group | Record separately |
|---|---|
| Missed | Returned, not returned, voicemail, later booking |
| Very short | Misdial, spam, wrong number, real quick enquiry |
| Medium | Service fit, qualification, booking |
| Long | Quote, booking, unresolved discussion, existing customer |
| Repeat | New customer, existing customer, follow-up |
Google says advertisers can import call-conversion information when another system tracks calls that lead to sales or other valuable actions.
A form submit can be a useful contact event. It becomes a stronger conversion only when the business can verify that the form was received, the contact information is usable, the requested service is offered, the location is serviceable, the request is from a potential customer rather than spam, employment, a vendor, or a duplicate, and the team can follow up and record the outcome.
Use separate events where the system supports them, rather than five versions of the same form event through multiple tags:
form_submit → form_received → qualified_enquiry → estimate_or_consultation → booked_job → completed_job
Test for duplication before using a form event for bidding.
Messages and booking requests can be meaningful contacts. They are not automatically qualified or successful jobs. Record the message or booking timestamp, the service requested, the customer location, the response status, the qualification, the appointment or job date, any cancellation or no-show, and completion and payment. Local Services Ads have their own lead and billing rules, so do not combine an LSA charged lead, a Google Ads form, and a CRM booking into one total without deduplication and source rules.
A qualified lead is an offline business classification, not merely a platform event. For a local-service business, qualification may require the correct service, the correct area, real customer intent, workable timing, a job type the business accepts, and the minimum information needed to proceed. Google’s qualified-lead documentation specifically describes further qualification offline in a CRM or internal system. A qualification definition should be written before the reporting period begins. Otherwise a business may count only the contacts that feel promising after the result is known.
Google describes a converted lead as a lead that completes a selected step in the conversion process, such as an offline or online closed deal or another step the advertiser defines as conversion. For local services, the business may define that step as a booked job, a completed job, a paid job, an accepted replacement estimate, an activated recurring plan, or a completed consultation. The definition should be visible in the conversion-action name and documentation. “Converted lead” without a business definition is not enough.
Sometimes. A booked job is closer to the business result than a click or form submit, and it may be a strong primary goal when the business has a reliable calendar or CRM, consistent booking definitions, a source identifier or matching process, enough records for the chosen bidding system, acceptable conversion delay, and a process for corrections, duplicates, cancellations, and no-shows.
A booked job may not be practical as the immediate primary goal when the business has very few jobs, inconsistent records, long sales cycles, or a weak integration. In that case, use the strongest reliable earlier signal while keeping booked outcomes in the Ledger and working toward better offline measurement. Do not pretend a deeper goal is reliable when the business cannot send it consistently.
A completed or paid job is economically closer to the owner’s outcome, but it may arrive too late or too infrequently for a campaign to learn efficiently. Use a staged design: start with a reliable contact or qualified-enquiry signal, validate that the event is deduplicated and meaningful, import booked or converted outcomes when the business can provide them, compare platform optimisation with owner-confirmed bookings and payments, and move the primary goal deeper only when the evidence supports it. This is not an argument for optimising to shallow leads forever. It is an argument for moving the primary goal in stages rather than skipping the measurement work.
Where an account sits on this ladder decides which conversion it can honestly count today.
Repairing measurement, or a simple lead path
Lead quality varies materially
Data quality and attribution are adequate
An HVAC campaign produces 30 tracked contacts in a month.
| Event | Count |
|---|---|
| Form submissions | 12 |
| Tracked calls | 15 |
| Booking requests | 3 |
| Deduplicated contacts | 25 |
| Qualified enquiries | 14 |
| Booked jobs | 7 |
| Completed jobs | 5 |
| Paid jobs | 4 |
| Confirmed revenue | $4,800.00 |
A shallow conversion design might report 30 conversions. A more useful design shows 25 deduplicated contacts as an observation metric, 14 qualified enquiries as a stronger lead-quality metric, 7 booked jobs as a business outcome, 5 completed and 4 paid jobs as deeper outcomes, and $4,800.00 of confirmed revenue in the Ledger. If the owner states a 35% contribution margin:
$4,800.00 × 35% = $1,680.00
That is an estimated contribution figure, not verified net profit. The owner must compare it with the defined acquisition cost and include the limits of attribution.
| Failure | Why it causes trouble | Repair |
|---|---|---|
| Every phone tap is primary | Counts intent as success | Separate call interaction, diagnostic, qualified call, and booking. |
| Every form submit is a sale | Includes spam, duplicates, and poor fit | Add receipt, qualification, and booking stages. |
| Multiple tags fire for one action | Inflates the main conversion signal | Test and deduplicate tags, imports, and thank-you events. |
| Calls and forms counted twice | One customer appears as two conversions | Use contact IDs, phone numbers, timestamps, and a deduplication rule. |
| Offline event has no matching key | Google cannot connect the later outcome | Preserve the click or call identifier and test the import. |
| Weak event is primary because it is frequent | Bidding learns volume, not value | Keep weak events secondary; define a stronger primary when feasible. |
| Booked job is undefined | Different people count different outcomes | Write the booking definition before launch. |
| Revenue is treated as profit | Margin and job costs are missing | Report confirmed revenue separately from estimated contribution. |
| No unknown category | Missing data is silently scored | Show unknown outcomes explicitly. |
Conversion QA checklist
0 of 22Before launch
During the test
At month-end
Use calls, forms, messages, and booking requests as contact or diagnostic events. Use qualified leads when the business can confirm quality offline. Use booked, completed, and paid jobs as deeper business outcomes when the records and data flow support them. Google can optimise toward a configured conversion. It cannot automatically know whether the technician arrived, whether the customer paid, or whether the job produced enough contribution. The goal is not the deepest label. It is the deepest verified outcome.
The Profit Ledger
The Ledger does not upgrade a call into a booking or a booking into profit. It counts the deepest outcome the evidence supports and labels the rest unknown.
Write the definition down before you change any settings, then check the conversion tracking audit to confirm the platform is counting the event you actually chose.
Count the deepest outcome the business can define, record, and send reliably. That may be a qualified enquiry, a booked job, a completed job, or a paid job, depending on the sales cycle, tracking system, conversion delay, and data quality. The mistake is counting the easiest event and then calling it the business result. A page view is not a lead, a form submission is not automatically qualified, and a phone call is not automatically a booking.
A call that reaches the business through the intended tracking path and satisfies a documented diagnostic rule, then receives a separate owner classification for service fit, qualification, booking, completion, and payment. Google can measure calls from ads and websites and can count calls that last longer than a minimum duration you select. Do not define a phone conversion as every ring, and do not treat a duration threshold as proof of a booked job.
A form submit is a useful contact event. It becomes a stronger conversion only when the business can verify the path. The form was received, and the contact information is usable. The requested service is offered, and the location is serviceable. The request is from a potential customer rather than spam or a vendor. The team can follow up and record the outcome. Test for duplicate tags before using a form event for bidding.
A qualified lead is an offline business classification, not merely a platform event. For a local-service business, qualification may require the correct service, the correct area, real customer intent, workable timing, a job type the business accepts, and the minimum information needed to proceed. Google describes qualified leads as leads further qualified offline in a CRM or internal system. The definition should be written before the reporting period begins.
Google describes a converted lead as a lead that completes a selected step in the conversion process, such as an offline or online closed deal or another step the advertiser defines. For local services, that step may be a booked job, a completed job, a paid job, an accepted replacement estimate, an activated recurring plan, or a completed consultation. The definition should be visible in the conversion-action name and documentation.
Sometimes. A booked job is closer to the business result than a click or form submit. It can be a strong primary goal when the business has a reliable calendar or CRM, consistent booking definitions, and a matching process. It also needs enough records for the bidding system, acceptable conversion delay, and a process for duplicates, cancellations, and no-shows. When jobs are few, records inconsistent, or the integration weak, use the strongest reliable earlier signal and keep booked outcomes in the Ledger.
A completed or paid job is economically closer to the owner's outcome, but it may arrive too late or too infrequently for a campaign to learn efficiently. Use a staged design. Start with a reliable contact or qualified-enquiry signal, and validate it is deduplicated and meaningful. Import booked or converted outcomes when the business can provide them. Move the primary goal deeper only when the evidence supports it.
Start here
Send what you have. A missing number is not a blocker. Working it out is part of the audit. No contracts, ever. I reply within 12 hours.
Send the numbers
Spend, leads, and what you suspect is going wrong. I reply within 12 hours.