What Pages Did This Lead Visit Before They Enquired

A named form fill lands in your inbox. You can see the source badge and the page that held the form. What you still cannot see is the ordered path between arrival and enquire. Did they read pricing, then case studies, then the contact page? Or did they bounce from one service page straight into the form?

That is a real WordPress question, not a dashboard wish. A Stack Overflow thread on tracking user flow in PHP asks for the same thing without Google Analytics. The asker wanted page 35, then 31, then 84, in order, for each visitor. Aggregate session counts do not answer that. A single form-page URL does not answer it either.

This post separates the form page from the landing page from the full page path, shows what free Lead Source 1.0.8 already stores on each enquiry, and shows when Lead Source Pro journey tracking is the honest upgrade for path depth.

Why the form page alone does not show what they read

Most form plugins store the URL of the page that held the form. That is useful. It is still only the converting page.

A visitor who arrived on a service page, read a comparison page, opened pricing, then submitted on /contact/ leaves one URL in the form entry. The form page says /contact/. It does not say which pages they opened before they typed their name.

Analytics can show aggregate pageviews. It rarely ties an ordered path to the named person who enquired. When you only have the form page, you guess which content persuaded them. Guessing is how agencies overfund the wrong page and underfund the page that actually sat in the middle of the path.

The form page answers where they submitted. It does not answer what they read first.

Landing page versus the full page path

Keep three jobs apart.

Landing page is the first URL on your site for that session. If a Google Ad opens /services/repairs, that URL is the landing page even after they click through /about and /pricing.

Form page (conversion page) is where the form submitted. If the form lives on /contact/, that is the form page no matter which service page started the visit.

Full page path is the ordered list of pages viewed before enquire. Landing page plus form page are two points. The path is the middle and the order.

Post How Do I See Which Landing Page Produced Each WordPress Lead owns the first job. It shows why free Lead Source already stores the landing page URL on each named fill, separate from the form page. This article owns path depth. Do not mash the two posts together. Entry URL and ordered journey answer different questions.

If you only need to know which first page produced the lead, stay on the landing-page post. If you need to know which pages they read in order before they asked, keep reading here.

What free Lead Source already stores on each enquiry

The free Lead Source plugin on wordpress.org is version 1.0.8 today. It hooks the form plugins you already use. Native hooks are Contact Form 7, WPForms, Gravity Forms, Ninja Forms, Formidable Forms, Fluent Forms, Elementor Pro Forms, Everest Forms, and Forminator. You do not add shortcodes or maintain hidden UTM fields for those builders.

Capture runs in the visitor’s browser. A small vanilla script reads the URL on page load and stores traffic source data in a first-party session cookie. On a successful native submit, the form hook attaches that session data to a Lead Source row.

Free 1.0.8 can store UTM keys when you set them (utm_source, utm_medium, utm_campaign, utm_term, utm_content) and the click IDs named in today’s readme (gclid, fbclid, msclkid, li_fat_id, ttclid). Traffic can be labelled as Google Ads, Meta Ads, LinkedIn Ads, Microsoft Ads, TikTok Ads, Organic – Google (or another search engine), Referral, or Direct. Landing page is the first page the visitor arrived on. Referrer has a server-side fallback.

How It Works also lists Form Page as the page where the form was submitted. So free already gives you landing page and form page next to the named fill. That is two anchors, not an ordered middle path.

Attribution on free is same session only. The cookie ends when the browser closes. It is not first-plus-last touch and not a 90 day window. That honesty is covered in Same Session Attribution vs 90 Day UTM Cookies. The overview for form capture is in How to Track Lead Sources in WordPress Forms.

Free also includes a dashboard, unlimited stored entries, per-submission email notifications, and daily, weekly, and monthly summary emails. Free Lead Source is fully functional on its own. It is not a trial.

What free does not claim is a reconstructed ordered journey of every page viewed before enquire. Do not invent that. If the job stops at landing page plus form page plus source, free 1.0.8 already answers it.

What Lead Source Pro adds for the visitor journey

Lead Source Pro is US$99 per year. Free stays fully functional. Pro adds full lead-journey tracking. That means every page a lead viewed before enquiring, tracked natively, with no extra journey plugin.

On the Pro lead detail view, the visitor journey reconstructs what that visitor read before enquiring, session by session, with scroll depth and tags for the landing and converting pages. That is the answer the Stack Overflow asker was building by hand with session arrays. Source alone cannot show which middle page sat between the ad click and the form.

Soft-sell Pro only for that path depth. Soft-sell good-lead marking separately in How Do I Mark Good Leads and Rank Channels by Quality Not Volume. Do not buy Pro to unlock landing page, UTMs, or click IDs. Those already ship in free 1.0.8. Do not buy Pro because a screenshot month-end feels hard either. Agency branded scheduled reports are a different Pro job covered in How Do Agencies Send Branded Monthly Lead Reports Without Screenshots.

Pro settings can also choose how many days a visitor’s original traffic source is remembered. Free readme still describes same-session until the browser closes. Do not blur those windows when you brief a client. Journey pages still depend on capture running in the visitor’s browser on pages you control. Cross-origin iframe embeds sit outside native WordPress form hooks. That wall is in Why Embedded Forms and iFrames Lose UTM and Click IDs.

How to read a journey next to a named lead

Use this sequence when you already capture leads on a native form hook.

1. Confirm free capture is working. Submit a test lead after a tagged landing page and open the Lead Source row. Source, landing page, and form page should match that session.
2. If you only needed the first URL versus the form URL, stop. The landing-page post already covers that split.
3. When the real ask is ordered pages, confirm Lead Source Pro is active and journey tracking is on for the site.
4. Open the lead detail for a named fill. Read the journey below the attribution block. Note the landing tag, the converting page tag, and the middle pages in order.
5. Compare two leads from the same campaign. Same source badge can hide different paths. One may have read pricing. Another may have skipped straight to contact.
6. Use that path when you decide which middle page deserves a clearer CTA, not only which ad deserves more spend.
7. Keep the session window honest. Free is same-session. Pro can use a multi-day attribution window for source. Say which product window you used when you report the journey.

You are reading a named person next to an ordered path. That is different from an Analytics funnel that never joins the form row.

What this still does not do

Free Lead Source 1.0.8 does not store the full ordered page path. It stores landing page and form page (plus source, UTMs, and click IDs when present). Claiming free journey export is false.

Neither free nor Pro invents install-count claims for your pitch. Do not quote Forge client roll-out numbers as wordpress.org installs.

This plugin does not upload offline conversions into Google Ads or Microsoft Ads. There is no Ads upload button in free or Pro for that job.

This plugin does not push contacts into HubSpot or Salesforce by itself. CRM field mapping is a separate job.

Free does not keep a 90 day cookie. Free does not stamp first touch and last touch as two separate values. Free does not capture gbraid or wbraid. Those names are not in today’s readme.

Journey tracking still needs pages you control. An embedded form in a cross-origin iframe is outside the native hooks. Fix the embed before you blame the journey view.

Short checklist

1. Separate form page, landing page, and full page path before you buy anything.
2. Confirm the form is one of the nine native hooks in free 1.0.8, including Forminator if that is your builder.
3. Install free Lead Source, finish the wizard, and verify a test fill carries source, landing page, and form page.
4. Keep free when the job is entry URL plus form URL plus source on a named fill.
5. Add Lead Source Pro (US$99/year) only when the job is ordered pages viewed before enquire.
6. Open a Pro lead detail and read the journey with landing and converting tags before you change page content.
7. Soft-check Pro for path depth only. Soft-check free for landing page and UTMs.

You do not need another Analytics screenshot to answer which pages a named lead read. Free Lead Source already stamps landing page and form page on each hooked fill. Lead Source Pro adds the ordered journey when path depth is the real question. That is the honest split. Entry URL is free. Full page path before enquire is Pro.