Lead Source Tracking: See the Campaign Behind Every Enquiry

Thirty-six enquiries came in last month. The agency says the ads brought them. Your gut says most were referrals. The receptionist remembers "a lot of people mentioned Instagram". All three are guessing, because nobody can open a list where each enquiry sits next to the channel, campaign and keyword that produced it.

Lead source tracking is the practice of attaching that origin to every single lead: every form submission, every phone call, every email click. This guide covers why most service businesses genuinely do not know where their leads come from, what "how did you hear about us" can and cannot tell you, how to set up tracking without a developer, and what it looks like when the enquiry list finally answers the Monday-morning question by itself.

Why do businesses not know where their leads come from?

Because the standard tools each hold one piece and none holds the lead. GA4 counts events in aggregate: it can report that generate_lead fired 26 times, but it is built around privacy rules that forbid personal data, so it will never show that the enquiry at 17:06 on Tuesday was Jure from the Invisalign campaign. The CRM holds Jure, but its lead-source field says whatever someone typed into it, if anyone typed anything. Phone calls, often the highest-intent leads a service business gets, bypass the website analytics entirely.

The result is three parallel realities: analytics counts, CRM anecdotes and front-desk memory. Budget meetings then run on the loudest of the three. The fix is not another report; it is stitching the origin onto the lead itself, at the moment it arrives.

Does asking how did you hear about us still work?

Yes, and you should keep asking, but treat the answers as a signal rather than the record. Self-reported attribution catches what no software sees: a colleague's recommendation, a podcast mention, a post in a private group. The catch is precision. People answer from memory, and answers cluster into vague buckets like "Google", which could mean a paid ad, an organic result or a maps listing; three very different budget decisions.

The practical setup is both at once: tracked attribution for the measurable journey, one open question on the form for the invisible one. Ruler Analytics found that combining tracked data with the "how did you hear about us" field covered lead origins far more accurately than either source alone. When the two disagree, that disagreement is information: it usually points at word of mouth doing work your dashboards credit to "Direct".

How to set up lead source tracking without a developer

Lead source tracking needs three pieces, and none of them requires code if you pick the right tools:

1. Tag everything that leaves your hands. Every ad, email and social link carries UTM parameters (we covered the naming rules in UTM tracking for email; the same discipline applies everywhere). Untagged links are how "Direct" becomes your biggest channel.
2. Make GA4 count the right moments. Mark your enquiry events (generate_lead, form_submit, phone and email clicks) as key events, so channels compare on enquiries instead of raw traffic.
3. Attach the origin to the lead, not just the pageview. This is the step most businesses miss. The visitor's source has to be captured when the form is submitted or the phone number is tapped, and stored with the lead's name, so the origin survives after the session is gone. Hidden form fields feeding the CRM, call tracking numbers, or a platform that does it automatically all solve this; a GA4 report alone never will.

Point three is the difference between "Paid Search sent 26 enquiries" and "these 26 people came from these campaigns"; the first is a chart, the second is a call list for tomorrow morning, which matters because speed decides who wins the lead.

Phone call leads: the enquiries your analytics never sees

For many service businesses the phone is the main door, and the analytics stack treats it like a side entrance. BIA/Kelsey's often-cited finding puts it bluntly: phone calls convert to revenue 10 to 15 times more often than web leads, and 61% of businesses rate their inbound calls as excellent leads.

The tracking options, in increasing order of effort: count taps on your phone number as an event (every mobile visitor who taps to call gets recorded with their source); use dynamic number insertion, where a call-tracking service shows each visitor a different number so even calls dialed by hand get attributed; or log calls manually against the CRM lead. The first option takes minutes, covers the mobile majority, and turns the most invisible lead type into a row with a source and a campaign next to it.

How Enalitica shows the source behind every enquiry and call

Enalitica gives a service business two views of the same truth. The campaign table shows every Google Ads campaign with its cost and its actual enquiry events side by side: submitted forms, pricelist downloads, phone clicks, email clicks, with cost per conversion for each campaign, and Search campaigns separated from Performance Max, with an honest note that Google does not disclose PMax's internal split, so last-click numbers there are a floor, not the full story. What Performance Max hides and what you still control is written up separately.

The Kontakti view goes where GA4 cannot: individual enquiries with a name, an email, a timestamp, and the channel and campaign that brought each one. A phone click at 14:22 from the All-on-4 campaign is a row, not a unit in a bar chart. Each lead carries a status (new, qualified, won), so a month later the table answers the better question: not which campaign sent the most enquiries, but which campaign sent the ones that became customers. The whole list exports to CSV for the CRM.

The same status grading feeds the next division: divide each campaign's spend by its qualified enquiries and you get cost per qualified lead, the number that regularly flips the channel ranking that raw lead counts suggest.

Setup is connecting GA4 and Google Ads; the enquiry events, the per-campaign breakdown and the contact list build themselves from there. And because every enquiry carries its arrival time, the same data feeds the enquiry-hours heatmap that shows when leads arrive relative to when your phone is actually answered.

Book a demo and bring last month's enquiry count; we will show you the campaigns and keywords behind it.

Frequently Asked Questions

What is the best way to track where leads come from?

Combine tracked and self-reported attribution: UTM-tag every link, mark enquiry events as key events in GA4, capture the source on the lead itself at submission time, and keep one open "how did you hear about us" question for the touchpoints software cannot see. Each method alone has a known blind spot; together they cover most of the journey.

Can GA4 show which campaign a specific lead came from?

No. GA4 reports aggregated event counts and its terms prohibit storing personal data, so it can say 26 enquiries came from Paid Search but never which person came from which campaign. Lead-level source data has to be captured outside GA4, at the moment the enquiry happens; that is exactly the gap Enalitica's contact list fills.

How do I track leads that come by phone?

Start by recording taps on your phone number as an event with the visitor's source; on mobile, where most calls start, this attributes the majority of them in minutes. Dynamic number insertion services go further by showing each visitor a unique number, attributing even desktop calls dialed by hand.

Should I trust "how did you hear about us" answers?

Trust them for direction, not for measurement. Answers come from memory and cluster into vague labels like "Google", but they are the only window into referrals, communities and word of mouth. The reliable picture comes from reading them next to tracked sources and investigating where the two disagree.