Capture the campaign context
Use consistent source, medium and campaign tags on eligible links. Record how first and later known sources are assigned. Test a new visit, a return visit and a request where attribution is unavailable. Keep an explicit unknown value so missing information is visible.
Trigger the event on confirmed success
Use an analytics event such as generate_lead when the application confirms a successful save. Repeat the form journey after a slow response, double tap and refresh, then check that these cases leave one accepted enquiry. Optional analytics may be unavailable due to consent or browser conditions.
Make sales qualification explicit
Set up clear stages for pending, duplicate, invalid, qualified and quoted. Agree who may change them and when a repeat request opens a new opportunity. Use a consent-aware plan for connecting approved identifiers across reports and keep email, names and phone numbers out of GA4 parameters.
Reconcile a sample before publishing
Compare the successful form reference and timestamp to the stored record. Check channel, landing page and sales status, including a case where analytics was unavailable. A separate operational count gives the sales team a reference for accepted forms.
Account for calls and assisted enquiries
Record what a call button click represents and who can confirm whether a conversation occurred. Use agreed manual entry fields for leads created by phone or a sales representative. Give these records the same qualification criteria.
Use outcomes to fix the right stage
If form starts increase while accepted requests fall, inspect page errors and validation. If accepted requests rise while quality drops, review offer fit and campaign targeting. If qualified leads wait too long, review routing and follow-up responsibilities.