Prove which channels bring revenue, not clicks.
You get asked to justify the budget with numbers your analytics cannot give you. Lead Source ties every enquiry to the campaign that produced it, so the report writes itself.
Said in every budget review.
“I am asked what the spend returned and I can only show sessions.”
Enquiries, named, with the campaign that produced each one.
“Everyone assumes that channel works and nobody has actually checked.”
Channels ranked by customers won, not clicks delivered.
“Form submissions arrive with no context at all.”
Source, campaign and full page journey attached at submission.
“Budget review is in three weeks.”
The report is already written, per channel and per campaign.
Leads that arrive qualified.
- Longer forms that still get completed, so sales stops chasing the basics.
- Our forms produce 3x the ROI of a standard form, measured across our own accounts.
- Every form on the site, whatever it was built in, with no per-form setup. How form tracking works.
- More completed enquiries from the traffic you already pay for.
The report you get asked for, already written.
- Enquiries, not sessions. The unit your finance team recognises.
- First touch and last touch both visible, so you can show what opened the door and what closed it.
- Per campaign, per channel and per landing page.
- Export it, or push it into the CRM you already run.
The conversion lever that costs nothing extra.
- Speed to lead is the one improvement you can make without asking for more budget.
- Replies go out in seconds, with the lead's source and page history attached.
- Sales gets the name, the email and the context.
- Same spend, more of the leads you already generate turning into work.

Every channel in the budget, tracked.
Whether they call, chat or fill in a form, the enquiry arrives with the marketing that produced it.
Sessions do not pay wages. Customers do.
Get the report before the review, not after.
One line of code. No dev ticket.
Paste it into the site head once. Nobody rebuilds conversion goals or tag manager triggers each time the site changes.
That one line is all lead source tracking needs.
<!-- in your <head> --> <script src="https://app.leadsource.co/ft.js" data-site="your-site-id"></script>
Four reasons it survives the review.
No tag manager project.
Nothing to configure, nothing to maintain when the site changes.
Works with your stack.
Sits alongside your CRM, your form tool and your analytics.
Data you can defend.
Server-side capture at submission, so the numbers survive ad blockers and consent refusals.
Five minutes.
Not a quarter-long implementation.
Reporting to someone else, or reporting for a client? There is a version for agencies, business owners, insurance agencies, MSPs, law firms, or start at all use cases.
Marketer questions, answered.
How is this different from GA4?
GA4 measures sessions and needs events configured before it measures anything useful. Lead Source captures the enquiry itself, server-side, with the source attached, and needs no configuration. Most teams run both. Side by side: Lead Source vs Google Analytics.
Does it work with my CRM?
Yes. Source data attaches to the lead record, so attribution lives where your pipeline already lives.
First touch or last touch?
Both. You see the source that first brought them and the source that was last in play before they enquired, plus every page in between.
Can I get this past IT?
It sets no cookies and stores nothing client-side. Capture happens server-side at submission. That is usually a shorter conversation than the one about tracking scripts.
Isn't this just UTM tagging I could set up myself?
Partly. Hidden fields plus strict UTM discipline gets you some of it, and most marketing teams have tried. The tags drop off when an ad blocker fires, when consent is refused, or when a link is copied into a message. They record nothing about the pages that persuaded the lead. And somebody on your team maintains the setup on every form for as long as the site exists. Lead Source records the source server-side when the form is submitted, adds the page journey and the person, and needs no per-form setup.
Can Google Analytics track form submissions?
It counts them as events. It will not tell you who submitted, or keep the source against that person, because Google Analytics is not built to hold personal data. Analytics gives you the total. Form tracking gives you the name.
What about a form embedded in an iframe?
Page scripts cannot read inside a form served from another domain. Browsers enforce that for every tool, this one included. What still works is passing values in through the embed URL before the iframe loads, which is what the LeadConnector setup does.
What is a good lead response time?
Minutes, not hours. Answer while the enquiry is still warm and before a competitor does, because the first reply tends to win the work.
Show them what the budget actually bought.
Free to start, no credit card. Paid plans carry a 90-day refund.
Start freeFree to start ยท no card











