To see which pages a lead viewed before filling your form, you need a tool that connects the form submission to the visit it came from: it records the pages and clicks of every visit, and when someone submits a form with their email, it attaches that visit — page by page — to the new lead. In Clicktics this happens automatically: open any lead and the Journey tab shows where they came from, every page they viewed in order, the buttons they clicked, the moment they filled your form, and a recording of the visit. This guide shows how it works with a real example, how to read a lead's journey, which forms need a small extra step, and how sales and marketing teams use this information.
Key takeaways
- Form tools and CRMs see only the submission. The pages before it tell you what the lead compared, what convinced them, and what to say on the first call.
- Clicktics captures standard website forms automatically and attaches the visit's full page trail to the lead — no form plugin or CRM integration needed.
- When the same person submits again, the new visit joins the same lead, so you see the journey across days and channels.
- "Came from" is the source of their first captured visit; each later visit shows its own source, so you can credit both channels.
- Forms inside iframes (Typeform, HubSpot and Google Forms embeds) and app sign-ups need one line of code:
clicktics.identify().
Why the pages before the form matter
A form submission tells you who someone is. The pages they viewed first tell you what they want. Two leads can send exactly the same "Contact us" message:
- One arrived from a blog post, read it, and filled the form on the way out.
- The other came from a comparison search, viewed your pricing page three times, opened the case study for their industry, and then filled the form.
They need very different replies, and the second should probably be called first. Seeing the pages before the form gives you:
- Context for the first reply. If they read the team-pricing page, answer the team-pricing question before they ask it.
- A priority signal. Pricing, comparison and checkout pages show buying intent; a single blog post usually doesn't. If you score leads, the pages are your strongest input — our guide to scoring leads on SEO intent signals builds a full model around them.
- Proof of which content converts. When the same page keeps appearing just before submissions, that page is doing your selling.
- Early warning of confusion. A lead who hit a broken page or bounced between two pages before asking a question is telling you something your website didn't answer.
Why your form tool or CRM can't show this
A form plugin receives the fields someone typed, and nothing about the visit around them. A CRM receives whatever the form sends it. Google Analytics records the visit but works with anonymous, aggregated data, and Google's policies don't allow personally identifiable information such as email addresses to be sent to it — so it can't tell you that the person who filled your form is the same person who viewed pricing three times.
To connect the two, one tool has to see both: the visit, as it happens, and the form submission at the end of it.
How to see a lead's page history in Clicktics
Step 1: Install the tracking script
Add the Clicktics script to your site once. It records every visit — pages, clicks and a session recording — and watches for form submissions. There's nothing to configure per form.
Step 2: Let visitors fill your forms as usual
When someone submits a form that contains an email field, Clicktics creates a lead with their name, email, phone and company where the form asks for them, plus every other answer they gave. Password, card and other sensitive fields are never saved. The visit they were on — every page and click up to the submission — is attached to the lead at that moment.
If the same email submits again later, Clicktics doesn't create a duplicate. The new visit is added to the existing lead, and the newest answers replace the old ones without wiping fields they left blank this time.
Step 3: Open the lead
Go to Leads and open the person. The Overview tab shows what they submitted, the page they landed on, the page where they filled the form, and when they first and last visited:

Step 4: Open the Journey tab
The Journey tab is the full story. At the top: how many times they came and when, how many pages they viewed, where they are, the source of their first visit, the page they landed on, their device, when they were first seen and when they became a lead. Below, every visit in order, step by step:

Each step shows how far into the visit it happened, so you can see where people spend their time before deciding. Pages are numbered across all visits, so the journey reads as one path even when it spans several days. Clicks are labelled with the button's own text ("Request a quote", "Add to cart") rather than code, and any page that returned a "page not found" error is flagged.
Step 5: Read the page flow
Scroll down to see the later visits and a compact Page flow — every page the lead viewed in order, with a "Form Filled" badge on the pages where they submitted:

Reading a lead's journey: a worked example
Here's what the journey above tells a sales rep in about thirty seconds, before they write a single word back to Maria:
- She found you through the newsletter — the autumn clubs campaign, according to the UTM tags on her first page. That campaign is producing leads.
- She started as a single buyer. She opened the Trail Runner Jacket and clicked "Add to cart" — then followed the "Need 10 or more?" link. The team offer caught her mid-purchase.
- She spent about a minute on the team orders page before asking for a quote: 30 runners, the club's green, a logo, needed before the March relay.
- Three days later she came back through a Google ad, went straight to team pricing, and sent a sharper request: 32 jackets, with the logo setup included.
The reply writes itself: confirm the 20%-off tier for 25–49 pieces, confirm that logo setup is free above 25 pieces, and give a delivery date before March. Without the journey, the rep has a name, an email and "Can you quote 32 jackets?" — and probably asks three questions she already answered on your website.
For your marketing team, the same journey shows that the newsletter started the conversation and paid search brought her back to finish it. Both deserve credit — which is the next point.
First touch, last touch, and every visit in between
The Came from field on a lead is the source of the first visit Clicktics linked to them — "Newsletter" for Maria. Each visit in the journey also shows its own source, so you can see the channel that started the relationship and the one that brought them back. If you tag your campaigns, the full UTM parameters appear on the first page of each visit; our guide to UTM tracking explains how to set them up so every campaign is distinguishable.
One thing to know: the journey is built from the visits Clicktics can link to the person — the visits in which they submitted a form or were identified. A visit from weeks earlier, before they ever gave you an email, stays an anonymous visit in your reports and isn't joined to the lead. The landing page and source you see are from the first visit in which they became known.
Forms that need one extra line
Clicktics captures forms that are submitted the standard way — most website contact, quote and sign-up forms, including typical WordPress form plugins. A few kinds of form are invisible to any tracking script running on your page:
- Forms inside an iframe — embedded Typeform, HubSpot, Google Forms and similar widgets run on another company's domain, and browsers don't let your page see inside them.
- "Forms" that aren't forms — a set of input boxes with a button that sends the data with JavaScript, without ever firing a form submission.
- Sign-ups and logins in a web app, where you know who the person is but no website form is involved.
For all three, call identify once you know the visitor's email — for example in the form tool's "on submit" callback, or right after a successful sign-up:
window.clicktics.identify('[email protected]', 'Maria Lopez');
That links the current visit, with every page before it, to the lead exactly as a captured form would. Calling it on every visit for logged-in users adds each of their visits to their journey.
Five ways teams use lead journeys
- Reply to the question behind the question. Read the journey before the first reply. Mention the page they spent the longest on.
- Prioritise the queue. Leads who viewed pricing, a comparison page or a case study go first; leads who read one blog post get a nurture email.
- Find your converting pages. Open your last twenty leads and note the page before the form. The pages that keep appearing deserve more traffic — and the ones that never appear may not be helping.
- Fix what confused them. If a journey shows a "page not found" error, or a lead going back and forth between two pages, watch the recording — it usually shows the gap in a minute or two. For a faster way through many recordings, see how to see what visitors do on your website.
- Learn from the ones who didn't submit. Journeys show the people who made it. Pair them with form abandonment tracking to see where the others gave up, and with button click tracking to count how many started the same path.
What about privacy?
Linking a visit to a named person is processing personal data, so treat it that way. Tell visitors in your privacy policy that you record visits and connect them to enquiries, run the tracking script behind your consent banner where the law requires it, and only keep what you use. In Clicktics, form fields are masked in session recordings, sensitive fields are never saved with a submission, and you can exclude pages or visitors from recording entirely. Our comparison of GDPR-compliant session replay tools covers the setup in detail.
Frequently asked questions
Can I see which pages a lead visited before submitting a form?
Yes, with a tool that records visits and links them to form submissions. In Clicktics, open the lead and choose the Journey tab: it lists every page they viewed in order, the buttons they clicked, the source of each visit, the moment they submitted, and a recording of each visit.
Does it work with WordPress and other website forms?
Most website forms are captured automatically, as long as the form contains an email field and is submitted as a normal form. Forms embedded from another service in an iframe — such as Typeform, HubSpot or Google Forms — need one line of code: call clicktics.identify() with the visitor's email when the form is submitted.
Will I see visits from before the lead filled the form?
You'll see every page of the visit in which they filled the form, from the page they landed on. Separate anonymous visits from earlier days aren't joined to the lead, because there was nothing to identify the person yet. Every later visit in which they submit again, or are identified, is added to the same journey.
What happens when a lead fills the form twice?
It stays one lead. The second visit is added to their journey, their newest answers replace the old ones, and fields they left blank the second time keep their earlier values.
Can I watch what a lead did on the website?
Yes. Each visit in the journey has a Play recording button that opens the session replay, with form fields masked, so you can watch how they moved through your pages before getting in touch.
See the story behind every lead
Clicktics attaches every page, click and recording to the leads your forms capture — with source, landing page and the answers they gave in one place. Open your next lead knowing exactly what they read before they wrote to you.
Start a free 14-day trial → No credit card needed — see every lead feature on the features page.
Tomás García
Tomás García writes for the Clicktics blog about session replay, analytics engineering, and building privacy-first products that agencies love. Reach the team at [email protected].