Agree the event definitions first.
Write an event dictionary with a trigger, owner and business meaning for each event. A form-open event describes interest in the next step. A validated submission attempt describes an action. Only an accepted delivery should be treated as a successfully sent enquiry, and even that does not prove final inbox receipt.
Keep qualified opportunity and paying-client decisions in the business’s sales process. They require information that a page interaction alone cannot establish. Decide how those later outcomes will be reconciled with the original enquiry.
Test both success and failure.
Use a controlled test recipient and clearly marked synthetic data. Verify what happens with valid details, incomplete input, a network error and a rejected delivery. An error must retain the visitor’s information where possible and explain the result honestly. Do not fire the same success event simply because a button was clicked.
- The expected event occurs once for the intended action.
- A failed submission does not report a received lead.
- Repeated clicks do not create uncontrolled duplicate sends.
- The receiving team can identify and remove synthetic tests.
- The form remains usable when optional measurement is unavailable.
Keep the context useful and proportionate.
Agree which source and campaign fields help the team assess enquiries. Avoid copying unnecessary personal details into analytics events. Tracking choices, retention and consent requirements should be reviewed against the tools and markets actually used. A measurement plan should document these decisions rather than assume every script is appropriate.
Check links, redirects and language switching so the intended source context is not lost. Treat campaign parameters as attribution clues; they do not prove that a particular advertisement caused a sale.
Read the funnel together with sales feedback.
Review the progression from visits to enquiries, qualified conversations, proposals and wins. A higher form-completion rate can still produce worse commercial results if the offer attracts unsuitable projects. Add reasons for disqualification so the page and campaign can be improved deliberately.
For a low-volume premium service, qualitative evidence from real conversations can be more useful than a premature experiment winner. Keep the test conditions and reporting period visible, and avoid claiming a lift from a handful of submissions.
Questions before you start
Questions before you start
Should opening the lead overlay count as a lead?
No. It is an interaction. A lead submission should be recorded only after the relevant submission and acceptance conditions have been met.
Can you verify our existing setup?
Yes, within an agreed scope and with access to the relevant tools. We inspect event definitions, test paths and the connection to the receiving workflow.
Does a perfect Lighthouse score verify conversion tracking?
No. Lighthouse checks aspects of page quality. Form delivery, event accuracy and sales qualification require separate end-to-end tests.