Originally published: January 17, 2021 · Last updated: August 17, 2026
Knowing which pages people visit before submitting a lead form can help explain what content assists conversion. But “track the user journey” can easily turn into collecting far more personal data than the business needs.
A useful measurement plan starts with a question, not a tracking plugin.
Define the decision you want to make
Examples include: Which service pages lead to enquiries? Does a case study assist form submissions? Are visitors abandoning a long contact page? Which traffic sources produce qualified leads?
If the answer will not change a decision, the data may not be worth collecting.
Track meaningful page and event sequences
For many sites, standard analytics plus a form-submission event is enough. You can compare landing pages, previous pages, traffic sources and conversion paths without storing a detailed personal dossier for every visitor.
Separate anonymous behavior from lead data
A form contains personal information. Analytics usually works best when that personal data is kept out of analytics event parameters and URLs. Do not send names, email addresses, phone numbers or message contents into analytics simply because the tools make it technically possible.
Use form events carefully
Distinguish between viewing a form, starting it, encountering validation errors and successfully submitting it only when those stages are genuinely useful. A “submit button click” is not necessarily a successful lead if validation fails or the request never reaches the server.
Watch the pages that assist conversion
The most valuable insight may be that visitors repeatedly read pricing, process, FAQ or portfolio pages before contacting you. Those pages deserve maintenance even if they are rarely the final page before submission.
Qualify leads outside basic analytics
Ten form submissions are not automatically better than five. If possible, connect marketing analysis with lead quality: valid enquiries, sales opportunities, purchases or another business outcome. That prevents optimization toward spam or low-value submissions.
Respect consent and retention requirements
Tracking requirements depend on jurisdiction, technology and the data collected. Configure analytics and consent tools according to the site’s legal obligations and keep retention proportionate to the purpose.
A practical small-site setup
For many WordPress sites, start with page views, acquisition source and one reliable successful-form-submission event. Add extra events only after a real question appears. This keeps reporting understandable and reduces implementation errors.
Bottom line
Lead-journey tracking should explain which content and acquisition paths contribute to useful enquiries. Measure enough to improve the site, but resist the assumption that more granular tracking automatically produces better decisions.