Lead form telemetry: what to measure before an e-commerce campaign

A contact form looks simple until the team starts buying traffic, launching a partner campaign or sending warm visitors from a founder profile. At that point you need to know more than whether a lead arrived. You need to see where the user stopped: contact page view, brief start, consent block, captcha issue, API error or thank-you page.

Minimum event chain

For a commercial WGP page, the baseline is not one goal but a sequence: contact page view with UTM, form start, submit attempt, successful submit, submit error, validation block and thank-you view. This helps separate a weak offer from a technical issue.

What to send with the event

Each event should carry locale, request direction, budget range, catalog size and UTM fields. For e-commerce and replatform work this matters because a 1C-Bitrix, integration or search request has a different value and a different next step.

Why it affects sales

Without measurement the team only sees an empty inbox and may decide the page is not trusted. In reality the problem can be captcha, an API error, a confusing budget field or lost UTM data. Measurement should be in place before traffic scales, not after the first ambiguous month.

How we use it at WGP

The WGP contact flow leads to a discovery-first process: base scope, risks, budget range and a small work slice before estimating custom development. We do not promise a fixed price before discovery for replatform, integrations or non-standard websites, but we do make the lead path measurable from source to thank-you and form errors.

If you are preparing a campaign for a complex store, start with a small funnel audit: send your site and get scope in 48 hours. For context, see how WGP runs projects and e-commerce development.