Skip to content
TRACKING05 / 50

Lead tracking should follow the lead past the form

Useful lead tracking connects the original source and campaign to the form, lead record, qualification, and outcome. Count successful actions rather than treating every CTA click as a lead.


Insights
Traffic sources connected to a website lead record and a confirmed outcome.
Editorial visual / 05

What should lead tracking connect?

Most website tracking stops too early.

  • The business sees traffic.
  • The analytics tool records a form submission.
  • A conversion gets counted.
  • The report says the campaign generated leads.

Then sales says the leads were poor.

Now both teams have a different version of what happened.

A useful lead tracking setup connects the visitor's source to the outcome the business cares about.

That means the path should not stop at the form.

It should continue through qualification, sales activity, and the final result where the business process supports it.

Google Analytics already gives a useful starting point. Its recommended lead events include generate_lead, qualify_lead, disqualify_lead, and close_convert_lead.

That sequence matches the real question better than page views alone.

  • How many people showed intent?
  • How many were a fit?
  • How many moved forward?
  • How many became customers?
A form submission is a marketing event. A qualified lead is a business outcome.

Track the whole path

Start with campaign source.

For tagged campaigns, keep a consistent UTM structure. Google Analytics supports fields such as source, medium, and campaign so traffic from email, paid ads, partners, and other activity stays identifiable.

The naming needs discipline.

linkedin and LinkedIn should not become two separate sources because different people typed them differently.

Next, track the landing context.

  • Which page did the visitor enter?
  • Which page held the form?
  • Which service or offer were they reading?
  • Which CTA did they use?

A lead from a pricing page carries different context from a lead that arrives after reading a broad article.

Next, track the form event.

Do not count a button click as a successful lead when the form still fails validation or the integration breaks. The event should reflect a completed action.

Then preserve the source information when the lead enters the CRM or lead system.

This is where a lot of attribution falls apart.

  • The website knows the campaign.
  • Analytics knows the session.
  • The CRM only says "website."

That leaves the sales outcome disconnected from the acquisition source.

Next, track the lead status.

  • New.
  • Contacted.
  • Qualified.
  • Not a fit.
  • Proposal sent.
  • Won.
  • Lost.

The exact stages change by business. The principle stays the same.

A marketing source becomes more useful when the business sees lead quality, not only volume.

Ten leads from one campaign might look better than four leads from another campaign. If the first ten were poor fit and the second four produced two strong opportunities, the raw lead count tells the wrong story.

Audit the lead record

Keep the first version small.

  • Track the main action.
  • Keep source, medium, campaign, landing page, and form name.
  • Send the lead into a reliable record.
  • Define the first few sales stages.
  • Review source to qualified lead.
  • Add deeper revenue tracking later when the business process is stable.

This also keeps the website work focused.

  • The designer does not need to own the entire CRM.
  • The SEO specialist does not need to own the sales pipeline.
  • The sales team does not need to debug analytics tags.

They do need a shared definition of the handoff.

For a website project, I want to know three things before launch.

  • What action counts as a lead?
  • Where does that lead go?
  • How will the team know whether the source produced useful business?

Once those answers exist, tracking starts supporting decisions instead of creating more numbers.

Discuss a Project