Guide

How to connect website forms to your CRM and keep the lead source

A practical walkthrough for getting enquiries into your CRM with the campaign that produced them still attached.

Short answer: To connect website forms to your CRM and keep the lead source, tag campaign links with UTM parameters, capture the source when the visitor lands, carry it through to the form submission, then create or update the contact and open a deal with that source attached. The most common failure is losing the source between landing and submitting, so test the whole path.

Updated 25 September 2026 · 6 min read

Why does the lead source get lost?

The lead source is the channel or campaign that brought a person to you: a paid search ad, a newsletter, a social post. It is easy to record at the moment someone lands on your site and surprisingly easy to lose before they submit a form.

A typical setup has a website, a form plugin, an email notification and a CRM, joined by copy-and-paste or an integration tool. Each join is a chance for the source to fall away. The lead still arrives, but as "website enquiry" with no idea which campaign produced it.

What information should travel with a lead?

FieldWhat it tells you
UTM source, medium and campaignWhich campaign link the visitor clicked
Ad click IDThe specific ad click, for sending conversions back to the ad platform
ReferrerThe site that sent the visitor when there was no tagged link
Landing pageWhich page or offer first caught their attention
Form and page submittedWhat they asked for and where
Consent stateWhat the visitor agreed to, which decides what can be linked to them

UTM parameters are tags added to the end of a link, such as utm_source and utm_campaign, that tell your analytics where a click came from. If you want a primer on the terms used here, see the glossary.

How do you connect forms to your CRM step by step?

  1. Tag your campaigns consistently

    Add UTM parameters to every paid, email and social link using one agreed naming convention.

  2. Capture the source on arrival

    Record the UTM parameters, ad click ID and referrer when the visitor lands, before they navigate away from the landing page.

  3. Carry it to the form

    Pass the captured source into the form submission, either as hidden fields or as a reference to the visitor's tracked session.

  4. Match or create the contact

    Look up the contact by email address, create them if they are new, and keep both their original and their latest source.

  5. Open the deal and assign it

    Create a deal in the right pipeline, assign an owner and log the submission on the contact's activity timeline.

  6. Report on outcomes, not just leads

    Report won deals and revenue by source, so marketing is judged on results rather than form fills.

What usually breaks, and how do you test for it?

  • Untagged links. Email and social links posted without UTM parameters arrive as referral or direct.
  • Redirects that strip parameters. A vanity URL or domain redirect can drop everything after the question mark.
  • Multi-page visits. If the source is read only from the current page URL, it is gone by the time the visitor reaches the contact page.
  • Forms on another domain. Embedded third-party forms often cannot see what your site captured.
  • Payment and booking hops. A trip to a payment or booking provider can make the return visit look like a referral from that provider.

To test, click a tagged campaign link in a private window, browse two or three pages, submit the form, and check the CRM record itself. If the source is only in the notification email, it is not in your reporting.

How does consent affect the lead source?

The lead itself is information the person chose to send you, so it reaches your CRM regardless. The journey behind it is different: joining their earlier visits to the submission relies on analytics tracking, which needs consent under PECR. Expect some leads to arrive with a source and some without, and report the two honestly rather than guessing. Our guide to why analytics undercounts after cookie consent explains why.

What should you do with the source once it is in the CRM?

Use it to prioritise and to report. Sales can see what the lead read or clicked before getting in touch. Marketing can report on the deals and revenue each channel produced, not just the number of enquiries. Once you have outcomes, you can compare channels under different attribution models.

Where uForge fits

In uForge the website, the tracker and the CRM are one platform, so a form submission creates or updates the contact, can open a deal in the right pipeline and carries a reference to the visitor's tracked journey, where they gave analytics consent. Automation rules can then assign an owner, create a task or send a follow-up. See CRM and automation in uForge.

Book a demo

Questions we get asked

What are hidden fields in a form?
Hidden fields are form fields the visitor does not see. A small script fills them with information such as UTM parameters or the landing page, and they are submitted with the visible fields. They are a common way to carry the lead source into a CRM, although the script needs to run reliably and the values must survive the visitor moving between pages.
Why does my CRM show so many leads as direct or unknown?
Usually because the source was lost between landing and submitting. Common causes are campaign links without UTM parameters, redirects that strip query strings, forms hosted on a different domain, and the visitor browsing several pages before the form so the landing-page parameters are gone. Visitors who declined analytics consent will also arrive without a tracked journey.
Should I store first-touch or last-touch source on the contact?
Both, if you can. The original source tells you which channel introduced the person; the latest source tells you what brought them back to enquire. Overwriting one with the other on every new submission destroys information you will want later when you report on attribution.
Can I use a form plugin and an integration tool instead?
You can, and many businesses do. The trade-off is that every connection is another place for data to be dropped or mismatched, and the integration usually passes only the fields you remembered to map. If you go that way, test with real campaign links and check that the source arrives on the CRM record, not just in the notification email.