Conversion Insights
Conversion Insights is the LeadGuard pillar that shows how real visitors move from viewing a pathway, to interacting with it, to a confirmed conversion. It is scoped to protected pathways and it deliberately does not capture the values typed into your website forms.
By LeadGuard Product Team · Published 15 July 2026 · Editorial policy
General web analytics answers a broad question: how many people came to the site and what did they do overall. Conversion Insights answers a much narrower one: on the specific pathways that create enquiries, how many people saw them, how many engaged, and how many reached a real confirmed outcome.
That narrower question is what most service businesses actually need to answer. A quiet month is only diagnosable if it can be split between fewer visits, fewer interactions or fewer completions.
The event model
LeadGuard records a small, deliberately-limited set of event types on protected pathways. Each event carries pathway metadata, but never the content typed into form fields.
| Event | Meaning |
|---|---|
| Visitor | An anonymous visitor identity used to correlate events within a session and across a short window, without persistent user identification. |
| Pathway view | A source page containing a protected pathway loaded for a real visitor. |
| Pathway interaction | The visitor engaged with the pathway: focused a form field, opened a booking link, tapped a call button, expanded a modal CTA. |
| Form start | The visitor made a first meaningful engagement with a form: focused a field or selected a control. |
| Form progress | The visitor engaged with additional fields or controls after the start, giving an indication of how far they got. |
| Submit attempt | The visitor pressed the submit action on a form. This alone is not treated as a confirmed conversion. |
| Confirmed conversion | An outcome event supported by an outcome source, such as landing on a linked confirmation page or triggering a learned inline success message. |
Outcome sources and verification
A submit click is easy to observe but is not by itself proof that a submission succeeded. Forms can throw silent errors, third-party processors can fail, and validation logic can block a submission after the visitor thinks they have completed it. Conversion Insights therefore treats confirmed conversion as a separate class of event, supported by an outcome source.
Outcome sources include a linked confirmation URL, a learned inline success message on the same page, and downstream indicators for pathways that route through an external booking or checkout system. The feature page on conversion verification explains how these are set up and learned.
Journeys and drop-off
Because each event is tied to an anonymous visitor and a canonical pathway, Conversion Insights can present a per-pathway funnel: view, interaction, form start, progress, submit attempt and confirmed conversion. Drop-off between adjacent stages is where diagnosis usually starts.
- A large drop between view and interaction usually points to visibility, mobile layout or CTA-copy issues rather than a broken form.
- A large drop between form start and submit attempt usually points to a friction or validation problem, or a payment or verification step that visitors abandon.
- A large drop between submit attempt and confirmed conversion usually points to an outcome-source failure: a broken thank-you page, a stopped success message, or a downstream processor error.
Protected-pathway scope
Conversion Insights only reports on pathways an account has chosen to protect. This is deliberate: it keeps the data commercially meaningful, limits event volume to what matters, and avoids implying LeadGuard is a general analytics platform. Discovering a new pathway on a site does not automatically start recording events against it; a protected pathway does.
What is deliberately not captured
- No keystroke logging, mouse-tracking heatmaps or session replay video.
- No persistent cross-site identity for the visitor.
- No CRM record creation and no lead scoring judgement.
- No revenue or attribution figures; LeadGuard does not attempt to match events to downstream sales.
Difference from general web analytics
General analytics is scoped to the whole site and every visitor. It is optimised for acquisition analysis, content performance and audience reporting. Conversion Insights is scoped to a small number of pathways and a narrow event vocabulary. It is optimised for one question: are the pathways that create enquiries still converting real visitors, and where are the drop-offs?
The two tools work together. General analytics answers whether a change in traffic composition explains a drop. Conversion Insights answers whether the pathway itself has changed behaviour.
Honest limitations
- Live visitor identity is anonymous by design; LeadGuard cannot tell you who submitted a form, only that a confirmed conversion occurred.
- Events on pathways behind third-party embeds depend on what those embeds expose to the browser and, in some cases, cannot be observed directly.
- Ad-blockers and privacy tools that block first-party scripts can suppress passive events; active pathway checks are unaffected.
- Confirmed conversion is only as reliable as the outcome source it is linked to; a misconfigured thank-you page can produce false negatives.
How to start
The free protection check inventories pathways on a submitted URL. Protecting a pathway and installing the LeadGuard site tag on the same site are what turn on Conversion Insights for that pathway.
FAQs
- Does LeadGuard record what visitors type into forms?
- No. Event data confirms an interaction happened; it does not include field values.
- Can Conversion Insights show me who submitted a form?
- No. Visitor identity is anonymous by design. LeadGuard reports that a confirmed conversion occurred; identifying the individual is a job for CRM or form-fulfilment tooling.
- How does a submit attempt differ from a confirmed conversion?
- A submit attempt is the visitor pressing the submit action. A confirmed conversion additionally requires an outcome source, such as landing on a linked confirmation page or triggering a learned inline success message.
- Does it work if the LeadGuard site tag is blocked?
- Passive events depend on the tag being loaded. If a visitor blocks first-party scripts entirely, LeadGuard cannot record their interactions. Active pathway checks are independent of the tag.
Related content
- featurePathway MonitoringPathway Monitoring continuously checks the forms, CTAs, booking links and confirmation paths a business depends on, using safe active checks plus real visitor evidence.
- featureWebsite form monitoringLeadGuard form monitoring checks that your contact and quote forms are present, visible, reachable and verifiable, without ever submitting a test enquiry.
- featureConversion verificationLeadGuard conversion verification uses confirmation pages, learned inline success messages and downstream indicators to prove a submission truly succeeded.
- guideHow LeadGuard monitors lead pathways without creating test leadsThe LeadGuard methodology: six check families, canonical pathway identity, real-visitor evidence and the safety rules that keep active checks non-invasive.
- glossaryLead pathway monitoring glossaryDefinitions for lead pathway, conversion verification, form monitoring, monitoring confidence and related terms used in LeadGuard.