Test whether an extra form question earns its cost in qualified leads

A question needs a business purpose

Write the question's purpose before writing its wording. It might identify a requested service, check an operational condition or route the enquiry to the right team. If nobody uses the answer, the field is merely another obstacle. Consider whether the information belongs on the page, in an optional field or in the first reply instead. Ask only what is necessary for the defined decision; a qualification test is not permission to collect sensitive or unrelated details.

Track the path from form starts to submissions, unique enquiries, processed enquiries and qualified outcomes. Add processing effort when it can be measured consistently. A field can improve the qualification percentage by shrinking the denominator so much that total useful volume falls. Equally, fewer submissions can be acceptable if useful volume stays stable and handling effort falls. State that business trade-off before reading the result.

Educational example: Version A receives 100 starts, 40 submissions and 12 qualified enquiries after $600 of spend. Version B receives 100 starts, 30 submissions and 15 qualified enquiries after the same spend. Completion is 40% versus 30%; cost per qualified enquiry is $50 versus $40. Those arithmetic figures explain the desired measurement path. They do not establish significance, predict improvement or justify B without examining allocation, quality definitions and time to assessment.

Use an appropriate comparison design. Keep offer, traffic source, device context and handling rules comparable where possible. Document whether the versions were assigned randomly or merely observed at different times. Google provides campaign experiment options, but a form test may require website tooling and a separate implementation. Do not imply that a platform campaign experiment automatically randomises website fields or that AdAce Ads provides a particular testing feature.

Customer, business and operational effects

• Customer effect: form comprehension, starts and completions. It reveals whether the question is an obstacle and whether visitors understand what information is requested.
• Business effect: compatible qualified volume and outcome cost. It prevents a higher qualification percentage from masking the loss of valuable requests.
• Operational effect: assessment coverage, response delays and processing effort. It shows whether the question helps staff make a useful decision rather than simply filling a database.

Test the whole path to a qualified outcome

1. Define the decision that uses the answer and the minimum information needed. Remove ambiguity from the wording and explain why the question is relevant.
2. Write the primary business outcome and guardrails before launch. Include broken submissions, unacceptable customer confusion and handling backlog as stop conditions.
3. Validate tracking for both versions without advertising writes where possible. Ensure the same enquiry and outcome are not counted twice through different events.
4. Plan allocation, spending boundaries, review dates and outcome maturity. Keep exploratory daily observations separate from the preplanned conclusion.
5. Assess all submitted enquiries with the same rubric and response process. Report unknown and unprocessed outcomes instead of treating them as automatically unqualified.
6. Decide retain, revise, remove or inconclusive from the complete path. Record implementation costs and the limits of the comparison, then keep only a field that serves an actual business purpose.

Completion rate alone cannot pick a winner

Sources and further reading

• Google Ads: experiments
• Google advertising policy: data collection