Why does our lead tracking not tell us where enquiries came from?
Lead tracking fails when the acquisition journey and the business outcome are recorded in separate systems or when important actions are never captured. The fix begins with a clear event model, consistent campaign attribution and testing from click through conversion.
What this can look like in practice
A single symptom rarely tells the whole story. These are some of the signs worth checking before deciding what needs to change.
Form submissions exist but source data is missing
Campaign clicks cannot be reconciled with enquiries
Multiple systems report incompatible totals
Important phone or message actions are invisible
Tracking was installed but never end-to-end tested
What to check next
Start with the parts that can be verified. This helps avoid expensive changes based on assumptions.
Inventory every real lead action
Identify where attribution data is lost
Standardize campaign parameters and event names
Test each path using controlled visits
Reconcile analytics with actual business records
Decision point
The practical takeaway
A smaller trustworthy measurement system is more useful than a large dashboard built on broken event chains.
Decision field guide
Find where identity or event context disappears from the lead journey.
Lead tracking breaks at handoffs: campaign to page, page to form, call to record, booking to CRM, or CRM to sale. Diagnosis should follow a controlled test through every system and compare what each layer records rather than treating a dashboard discrepancy as one error.
FIELD 01
Create a conversion specification
List every lead-producing action and define when it counts. A button click, form start, successful submission, qualified phone call and accepted opportunity represent different states. Give events consistent names and state which business record confirms the outcome.
FIELD 02
Run controlled end-to-end tests
Use known test campaigns or parameters, complete the customer action and inspect the browser, server, analytics and downstream record. Repeat for forms, phone calls, messaging and bookings that matter. A test should confirm notification and business receipt in addition to analytics collection.
FIELD 03
Reconcile systems with known limitations
Time zones, duplicate events, consent, ad blockers, routing, spam filtering and integration delays can create differences. Document expected tolerances and known gaps. A trustworthy system can contain unknowns; the reporting problem begins when those gaps are hidden or counted twice.
Evidence worth collecting
Event and conversion definitions
Controlled test IDs and timestamps
Analytics and platform records
Form, call or booking destination records
CRM or customer outcome records
Questions that sharpen the decision
Why can a form submission appear in analytics and never reach staff?
The browser event and business notification are separate parts of the journey. Test the server-side submission and recipient routing as well as the analytics event.
Should button clicks count as leads?
Only when the business intentionally defines them that way. A successful enquiry is usually stronger evidence than an interaction with the button.
How often should tracking be tested?
Test after changes to websites, forms, analytics, consent, campaigns or integrations and on a routine schedule suited to business importance.
DSDillon Commercial Intelligence Advisory. Information is provided to help businesses investigate a problem and make a more informed decision. Outcomes depend on the facts and circumstances of each business.
DSDillon Intelligence Pathways
Continue investigating
Related evidence-led briefs selected from search demand DSDillon has measured.
Explore more about Why Lead Tracking Is Not Working
Practical answers for businesses losing traffic, leads or customer confidence. Use the related paths below to find supporting information, practical tools and the next step that fits your needs.
