Name the action before you count it
A click from Google Ads, a successful form and a booked job tell you different things. If all three appear under a broad lead label, the campaign report can look healthy while the team waits for useful conversations. Decide which actions the campaign should measure before relying on their total.
Define the Google Ads lead action
Write a plain description. “A visitor successfully sends the project inquiry form” is more precise than “contact conversion.” Add where the record comes from and what could make it unreliable. The business should be able to explain the number to somebody who has never opened an analytics account.
Choose a completed contact action
Choose the contact step the campaign should measure and confirm the setup required for it. Calls have several measurement options; a phone-number click is not automatically proof of a completed conversation. Have the implementer show which action your record actually represents.
Identify the measurement source
Record whether the number comes from the ads account, a website measurement setup or an inquiry log. Include the relevant action name. Consistent labels make it easier to investigate a difference between systems later.
Note what this count cannot prove
Record what the chosen measure leaves unknown. A form submission does not establish that the request suits your service or became a job. Keep that limit next to its definition so the review can use the count without turning it into a broader sales claim.
Separate interest from an inquiry
An article view or brochure download can show interest. A person sharing contact details and asking about your service is a different kind of action. Both can help you understand the site, but they serve different purposes in your review.
Decide what counts as supporting activity
The Google Ads total depends on the actions and counting settings selected for the report, and some reported conversions may be modeled. Ask the implementer to show the settings behind your lead figure. Keep supporting interactions available for diagnosis without quietly adding them to the campaign’s inquiry total.
Inspect a supporting interaction
Choose a supporting interaction that answers a specific question about the route. It could show that somebody reached the contact area, while the main inquiry action records a completed request. Document that distinction before comparing their totals.
Compare it with an inquiry
Compare one supporting interaction with the actual customer request it may precede. The two records serve different purposes. A visitor opening a page does not establish that they shared contact details or asked for the advertised service.
Keep qualification visible
Qualification is a business judgment your team makes after reviewing the request. Record whether it fits the service, area and agreed project criteria. Keep the assessment beside the campaign record so the person reviewing spend can distinguish a counted interaction from a suitable prospect.
Add the qualification after contact
Define the qualification criteria with the staff who handle Google Ads inquiries. Service, area, project type and the customer’s requested action may matter. Write the criteria clearly enough that colleagues can discuss a borderline request and explain their decision.
Record the reason when something is unsuitable. A recurring pattern of requests outside your area may call for changes to your page or campaign. Unrelated service requests might point to unclear wording. Don’t use a vague “bad lead” label when a more specific reason would help the next marketing decision. Leave unknown details marked as unknown until someone confirms them.
Test what the record actually measures
Ask whoever manages Google Ads lead tracking to demonstrate the actual action on the website. Test a successful form submission and a failed attempt, then confirm what appears in the campaign measurement. Check which form is covered and whether another action could trigger the same recorded conversion.
Test the action end to end
Check the business side of that same test. Did the message reach the right destination? Was a test record created in the CRM? Could a duplicate message create two records? Keep technical test entries marked so the team can remove them from its business review. Repeat the test when the form, booking tool or confirmation process changes.
Check a failed submission
Try the form with a required field missing, then complete a successful test. Confirm which action creates the recorded conversion and which creates a delivered inquiry. The customer should receive understandable feedback in both cases.
Inspect duplicate behavior
Check what happens when the submission is repeated. Ask the implementer to demonstrate how the setup treats that situation instead of assuming the totals are deduplicated. Record the behavior and its implications for your review.
Mark the test record
Use clearly marked test details and keep those records separate from genuine requests. Note the test date and the person who checked the result. Repeat the check when the form or its measurement setup changes.
Review the route rather than one total
Bring website activity, actual inquiries and later outcomes together at an agreed review. Compare the definitions and time periods before comparing totals. A website event recorded today and a job agreed weeks later belong to different points in the customer’s process. Explain those timing differences in the report.
Start with a small measurement plan your team can maintain. List the action, its definition, where it is recorded, who owns it and how it is tested. Make sure account access and customer information are handled through the business’s existing controls. Choose one important contact action and document it fully before adding a longer list of events that nobody has checked.
If you’d like your Google Ads lead tracking checked against real inquiries, see our Google Ads management.

