How to track lead source in your website forms

Your contact form collects a name, an email address, and a message. Someone wants a quote. But you don't know whether they found you through Google Search, a Meta ad, or a newsletter.

An analytics report can help. For example, Google Analytics 4's Traffic acquisition report shows traffic sources and can report form events you've configured as key events.

You might see 17 enquiries from paid search and five from organic search. That's useful for comparing enquiry volume. To judge lead quality, you also need to connect those enquiries with what happened afterward.

Consider these example records in a CRM:

Now you can follow each lead from its recorded source to its sales outcome. As more records come in, you can see which channels bring suitable enquiries and paying customers.

Analytics and lead tracking can work together. GA4 has more detailed reporting options too. The task here is to keep source information with the named enquiry in the place where you manage sales.

Source, medium, and campaign describe where a visit came from. A source journey and visited pages add context about what happened before the enquiry.

Source and medium belong together. “Google” alone doesn't tell you whether someone clicked an ad or an unpaid search result. Campaign adds detail when campaign information is available.

A journey is useful when someone visits more than once. Imagine a visitor clicks a Google ad, reads your service page, and leaves. A few days later, they return through an email and request a quote.

If you save only the final source, you may see the email visit. The recorded journey can also show the earlier Google Ads visit. Pages visited can show that they read your services and pricing before contacting you.

That gives you context for the enquiry. It doesn't mean every interaction has been captured; visits on another device or sources that pass no identifying information can leave gaps.

The basic flow is: capture the visit information, keep it until submission, include it in the form, and save it with the lead. Here's how to approach each part.

1. Give your campaign links clear labels

Use UTM parameters on links you control, such as ads and newsletters. These labels identify the source, medium, and campaign.

For a Google Ads campaign, example values might be:

• utm_source=google
• utm_medium=cpc
• utm_campaign=spring_services

Keep the names consistent. If the same campaign appears under three spellings, its results become harder to compare. Google's campaign URL guide explains these parameters and confirms that their values are case-sensitive.

UTMs are one source of tracking information. A setup may also capture referrer information and click IDs. For example, Google Ads auto-tagging adds a gclid to the landing-page URL after an ad click.

Capturing a click ID and knowing the campaign name are different things. Check what your tracking method can actually identify. Leave unavailable details empty rather than filling them with guesses.

2. Keep the information as the visitor browses

Someone may arrive on a blog post and submit a form on your contact page. By then, the contact-page URL may no longer contain the original campaign tags.

Your tracking method needs to capture the information when the visitor arrives and keep it available until they submit. Depending on your needs, you might use a native form feature, a tracking tool, or a custom setup.

If you want context across return visits, check that the method records those visits too. Keeping campaign values for one visit and recording a source journey are different capabilities.

Also decide what your main source value means. First touch describes the first recorded arrival. Last touch describes the arrival closest to the enquiry. Keep the definition consistent when comparing leads; a journey can show additional sources alongside it.

3. Include the captured data in the form submission

Hidden fields let you send extra information with a form without adding visible questions for the visitor. Your tracking tool or form feature fills them with the captured values before submission.

An empty hidden field doesn't track anything by itself. MDN's hidden input reference explains how these fields carry values in a submitted form.

For a quote request, the visible fields might collect the person's name, email, and project details. The hidden fields can carry the source, medium, campaign, and other recorded visit context. Both sets of information should reach the same saved enquiry.

4. Save the source alongside the lead in your CRM

If your form sends enquiries to a CRM or spreadsheet, include the hidden field values in that transfer. Match the submitted information to the relevant destination fields.

Check the final record, not just the form notification. A source visible in an email is little help for reporting if your CRM drops it during the transfer.

A spreadsheet is enough to start. Keep one row per enquiry, with its source information and a sales status such as new, qualified, won, or lost. If you already use a CRM, record those outcomes there.

5. Test the full route before relying on the reports

Open a campaign link with recognizable test values. Visit another page, then submit the form. Check that the saved enquiry contains the expected source, medium, and campaign.

If your setup records journeys, return through a different tagged link and check how the earlier and later visits appear. Compare the saved page history with the pages you actually opened.

Finally, check the CRM or spreadsheet record. The test is complete when the information reaches the place where you'll use it.

When something is missing, check where it stopped: the arrival, the form submission, or the transfer to your CRM. Repeat the test after changing your forms or website.

TrackLeadSource is designed to capture a visitor's source, medium, campaign, source journey, and visited pages, then pass the captured information through hidden form fields with the enquiry.

Its tracking approach includes UTM parameters and click IDs such as gclid, fbclid, ttclid, and li_fat_id. The aim is to keep useful source information with the lead, rather than leave it behind when the visitor moves between pages.

You add hidden fields to your forms and map the submitted values to your CRM or spreadsheet. Sales outcomes are recorded in that destination. Connecting those outcomes with the source data helps you understand which channels bring customers.

Once the source is saved with each lead, update the record as the sale progresses. Agree on what makes a lead qualified: for example, the right service, location, or budget. Then record whether the enquiry becomes a customer and the revenue from the sale.

Here's a hypothetical comparison of two paid campaigns, each with $1,000 in ad spend:

Meta brought more leads and had a lower cost per lead: $20 compared with $50. Google brought more customers and had a lower ad spend per customer.

That's the difference source data can help you uncover once it's connected to sales outcomes. Looking only at form submissions could push you toward the campaign bringing fewer customers.

Compare leads from the same period and give them time to complete your sales process. Check deal values too: two large customers may bring more revenue than five small ones. Revenue and costs are needed to assess returns; a lead count alone doesn't tell you ROI.

Use those patterns to review your campaigns and budget. If one source repeatedly brings unsuitable enquiries, check its targeting and message. If another brings fewer leads but more sales, it deserves a closer look.

Capture the source information, pass it with the submission, and check the saved lead. Then keep its sales outcome up to date.

With those two pieces together, you can begin to see which channels bring the enquiries that turn into business.