A lead form must deliver a usable record, not just a platform count
Check that supported advertising forms deliver the expected contact and source fields. A successful ad-platform submission may be unusable if the receiving system loses the relevant context.
Native ad forms can produce a submission even when the downstream notification or intake connection fails. Verify field mapping, routing and record availability separately from the platform’s conversion total.
A worked example
A hypothetical campaign produces 15 accepted submissions, but a mapping error leaves the contact email blank in the intake system. The ad report is not evidence that the team can successfully follow up with all 15.
How to apply it
- Run a labeled controlled submission and inspect required fields at the destination.
- Check identifiers, timestamps, source context and delivery failures.
- Review duplicates and suitability before counting verified new inquiries.
What the result can establish
Keep test records separate from genuine results. Do not automatically retry actions that could duplicate submissions. A successful connection test confirms delivery behavior, not future lead quality or campaign profitability.
Reference: Google Ads: conversion measurement.
Supporting documentation
Google Ads: conversion measurementW3C WAI: validating formsGoogle Analytics: measurement documentation