Measure Enquiries Before Optimizing Your Ads

Define the business outcome first

Complete this sentence: “An enquiry is useful when the person requests a service we offer, in an area we serve, with enough information for a meaningful response.” Adapt the definition to your business rather than counting everything that arrives.

For a mobile appliance-repair company, a suitable contact needs the right appliance type and a service address in coverage. A supplier solicitation, duplicate submission, or question about a brand the company cannot repair should not be confused with that outcome. Record those categories so a report can explain the difference.

Know what the conversion actually measures

Google supports website, call, and offline conversion measurement. Document the trigger for each action in your account. A form-button click can happen without successful submission; a recorded submission can still be spam or an unsuitable request. The business needs both technical verification and lead review.

Separate primary goals from observation

Primary actions are generally used for bidding when their standard goal is included, while secondary actions generally appear in All conversions for observation. Custom goals are an exception: included actions can be used for bidding regardless of primary or secondary status. Review the actual campaign goal setup.

Test the path deliberately

Our suggested test sheet includes action, device, expected result, observed result, and follow-up. Submit a clearly labelled test enquiry and confirm that the business receives it. Check what happens after successful submission, after an error, and after revisiting a confirmation page. Ask the person responsible for tracking to verify that the intended event is recorded correctly.

For calls, identify the measurement method. Google distinguishes several phone-call conversion methods, including calls from ads, calls to a website number, and phone-number clicks. These do not all establish the same thing about whether a conversation occurred.

Reconcile a fictional week

Suppose a dashboard reports twelve form events while the inbox contains nine distinct requests. Before changing bids, investigate duplication, incomplete submissions, or a tracking trigger that fires too early. Then classify those nine requests: suitable, outside coverage, service unavailable, duplicate, or spam. These numbers are a made-up diagnostic example, not a performance benchmark.

Keep the lead log simple enough for staff to maintain. Record date, service requested, area, source where known, suitability, response status, and booking outcome. Use your normal controlled business system rather than putting customer details in a public report.

You may not reconcile every record perfectly because measurement and attribution have limitations. Document what is known and what remains uncertain instead of silently treating platform counts as an exact customer ledger.

Optimize after the signal is credible

Our recommendation is to repair broken or misleading measurement before making major performance judgements from it. If the campaign is rewarded for an easy action that has little business value, more of that action may leave the owner dissatisfied.

Review whether the chosen goal still fits as the business matures. Early enquiry tracking can later be complemented by qualified-lead or booking outcomes when the operating process can reliably support them.