01

A cheaper enquiry can still be an expensive outcome

Your campaign report looks encouraging. Forms are coming in and the cost per enquiry has fallen. Then the sales team explains that several contacts wanted a job, a free service or something you do not sell. The dashboard and the business are telling different stories.

The useful question is not simply how many people completed a form. It is how many relevant people became a meaningful sales opportunity. This guide explains a practical workflow for connecting those stages. It is a planning guide, not a promise that changing conversion settings will increase sales.

02

1. Agree on what a qualified lead means

Start with a short discussion between whoever manages advertising and whoever speaks to prospects. Write a definition that both can apply consistently. For a service business, that could mean a genuine business contact with a relevant requirement, a serviceable location and willingness to discuss a realistic project.

Keep the definition specific enough to review. A salesperson saying that an enquiry feels weak is useful context, but it is not a repeatable status. Record why the lead does or does not meet the agreed criteria. Our lead quality measurement guide explains the wider metrics.

03

2. Separate enquiries, qualified leads and customers

A form submission records an initial action. A qualified lead records a later assessment. A customer records an outcome after the sales process. Treating these as separate events helps you see where progress stops.

Google supports qualified-lead and converted-lead goals using deeper funnel information. Its official lead-stage guidance explains the platform concepts. Your business still needs to define its own criteria and maintain accurate records.

Do not mark someone as a customer because a meeting was booked. Equally, do not reject a relevant lead simply because the person did not buy immediately. A longer decision process needs a different follow-up expectation.

04

3. Make a small, useful lead record

A CRM can support this process, but a carefully controlled sheet may be enough for an initial review. Choose fields that answer a business question rather than collecting everything available. Give each enquiry a stable internal identifier.

Useful operational fields include enquiry date, requested service, source information when available, assigned owner, current status, status date and rejection reason. Keep personal contact data in the appropriate secured system. A public reporting dashboard should not expose names, email addresses or private messages.

Assign one person to keep status definitions clear. Otherwise, one colleague may use qualified to mean contactable while another uses it to mean ready to sign.

05

An illustrative example: two campaigns with different outcomes

Imagine two campaigns each spending ₹20,000 over a comparable period. Campaign A produces 40 enquiries and four qualified leads. Campaign B produces 20 enquiries and eight qualified leads. These are invented numbers to explain the calculation, not DMB client results.

Campaign A has a ₹500 cost per enquiry and ₹5,000 cost per qualified lead. Campaign B has a ₹1,000 cost per enquiry and ₹2,500 cost per qualified lead. The campaign with cheaper forms has the higher qualified-lead cost in this example.

That is a reason to investigate, not an automatic instruction to move the entire budget. Check lead age, sales coverage, campaign intent and eventual outcomes before deciding.

06

4. Review the capture and import method

Google describes enhanced conversions for leads as a way to supplement offline conversion measurement with user-provided data. Review its current setup documentation with the person responsible for your tags and account.

The implementation should fit the account, website and CRM. Do not paste a random tracking snippet into the site and assume the entire sales journey is connected. Check which identifiers are collected, which outcome is imported and how the source record maps to the event.

If you are planning a new API integration, ask the developer to verify the currently supported Google Data Manager route. Existing integrations and new integrations can have different migration requirements. This article does not prescribe a legacy API endpoint.

07

5. Test the event before using it for decisions

Create a controlled test record that can be distinguished from real prospects. Confirm that a successful form produces the expected enquiry record, that the status can be updated and that the intended outcome reaches the reporting system.

Review duplicate submissions, repeated imports and conversion timestamps. A refresh of a thank-you page should not silently turn one conversation into several independent prospects. Confirm how your chosen system handles updates rather than assuming every tool works the same way.

Use the diagnostics and import reports available in the account. An automation reporting success means it ran; you still need to confirm that the expected business event was processed.

08

6. Keep privacy choices part of the implementation

Contact information is personal data even when the reporting goal is commercial. Before connecting systems, review the data you need, the notices and choices presented to people, access permissions and the platform requirements.

Hashing an identifier is not permission to collect or share it without the appropriate basis. Do not send private sales notes or unrelated sensitive information into advertising tools. Ask the responsible technical and privacy owners to review the actual setup.

The practical aim is a reliable measurement process with clear responsibilities. It is not to capture the maximum possible information from every visitor.

09

7. Read the result with the sales team

Set a regular review that includes both campaign performance and what happened after the enquiry. Group outcomes by campaign and service, then look for recurring reasons a lead did not progress. Separate a poor fit from a slow response or a missed call.

If relevant prospects repeatedly ask for something the landing page does not explain, review the offer and form wording. Our clicks without leads guide covers that earlier buying journey. Landing page work can address a message or contact-flow problem.

Keep the discussion practical: what did we observe, what might explain it and what change will we review next? Avoid treating an attribution report as a complete record of every influence on a sale.

10

Common questions before connecting the systems

Should every conversion become a bidding goal? No single setup fits every account. Review which actions are useful for observation and which represent the outcome you actually want to optimise. Ask your campaign manager to explain the trade-off before changing the goal configuration.

What if sales take several weeks? Compare groups with similar time to mature. A lead received yesterday has not had the same opportunity to become a customer as one received last month. Record the normal sales delay alongside your reports.

Can this replace a sales process? Tracking can show where progress is missing, but it cannot answer calls, clarify a proposal or resolve a poor offer. Use the information to improve those responsibilities rather than expecting an import connection to perform them.

11

Your first implementation checklist

Choose one important service and one campaign group. Agree the qualification definition, name the status owner, test the record journey and review the current import method. Establish a baseline before changing several campaign settings together.

Then document one decision and its review date. For example, revise an unclear service requirement in the form and compare the resulting mix after enough leads have matured. Do not announce an improvement from a handful of fresh enquiries.

For support, explore Google Ads management and marketing analytics and reporting. Ask for a clear measurement scope, ownership and testing plan before implementation.

Editorial note: this original guide was prepared with AI assistance on 27 October 2026. The worked example is hypothetical. The featured image is an AI-generated editorial scene, not a screenshot of a client account.