Lead Reporting
Part of B2B website conversion paths
Tracking assisted enquiry journeys across the website
A B2B enquiry often follows several visits and pages.
Record a completed enquiry submission or confirmed booking as a GA4 key event. Then open the Key events attribution paths report and review the recorded touchpoints leading to that event, rather than judging the journey by the final form page alone.
Treat those paths as evidence, not causal proof. The final form page can hide earlier content that helped, while crediting every earlier page can overstate its role.
Tracking Assisted Enquiry Journeys in GA4
- Define the end eventRecord a completed enquiry submission or confirmed booking as a key event in GA4.
- Review attribution pathsUse the Key Events Attribution Paths report to examine touchpoints leading to the key event.
- Identify recurring touchpointsLook for common pages such as service pages, case studies or pricing information across journeys.
- Account for referral data limitationsUTM parameters override referrer data; use them on partner links to track external sources accurately.
- Validate with sales insightsCompare analytics data with sales notes to understand real buyer influences and fill gaps.
Define the end event
Choose the successful submission or confirmed booking as the outcome, then mark its collected event as a key event in GA4. Check GA4 recommended events guidance when naming the event, but do not count a failed form, duplicate click or booking-page view as a completed enquiry.
Keep personal form content out of analytics events. Where enquiry types have separate completion events, compare the recorded paths for each outcome.
Inspect the path and its gaps
In the Key events attribution paths report, select the key event and review the touchpoints recorded before completion. Look for recurring touchpoints across the enquiry types you track, and check whether service pages, case studies or pricing information recur in those journeys.
For external links, GA4’s default referral classification uses the HTTP Referer header; same-domain referrers are treated as session continuation. UTM parameters take priority over referrer data, so use them on partner links when you need to distinguish the external source, medium or campaign.
Referral data can be affected by configuration: an excluded external domain can be classified as direct, and a visit without referrer data may also appear as direct. Cookie limits, device changes, offline conversations and direct visits can leave gaps, so an absent touchpoint is not proof that it had no influence.
Compare the analytics view with sales notes for a sample of real enquiries. Ask what the buyer says influenced the decision and whether the route matched their need; sales notes can add context where an online path is incomplete.
Use those findings to improve navigation and content links, then review paths again under the same event definition. The aim is a more coherent visitor journey, not a claim that one page single-handedly created the lead.
GA4 Referral Classification vs. UTM Parameters
- Default Referral Source
- HTTP Referer header (e.g., google.com, linkedin.com)
- Same-Domain Referrers
- Treated as session continuation (not a new source)
- UTM Parameters Take Priority
- Override referrer data; use for accurate campaign tracking on partner links
- Common Data Gaps
- Cookie limits, device changes, offline conversations, direct visits can obscure touchpoints
Key Considerations for Accurate Journey Tracking
- Avoid over-attributing final form page
- It may hide earlier influencing content
- Do not count failed forms
- Only record successful submissions or confirmed bookings
- Use UTM parameters on external links
- Ensure accurate tracking of partner campaigns
- Validate with sales team feedback
- Sales notes provide context missing from digital data
