Home › Guides › Conversion path tracking

Conversion Path Tracking for Small Business

Published September 5, 2026 · BuyerJourney.net

A conversion path is everything that happened before the conversion — and in most small-business analytics, almost all of it is missing. The form fill gets recorded; the ad impression, the three research sessions, and the device switch that preceded it usually don't survive as one connected sequence. Here's how to track paths properly: the free discipline that helps, the GA4 tools and their real limits, and what it takes to see whole paths.

What a conversion path actually contains

For anything considered — B2B, high-ticket DTC, services — a realistic path looks like: ad impression (not clicked) → search visit to a guide → comparison session two days later on a different device → email click → pricing page → form fill → sales conversation → closed deal. Seven touches, two devices, maybe two weeks. The conversion report shows the last two. Everything upstream — the part your budget actually paid for — is the part path tracking exists to recover.

Start with the free layer: UTM discipline

Before buying anything, fix the cheapest failure mode: untagged links. Every link you control — ads, emails, social posts, listings — carries utm_source, utm_medium, utm_campaign, applied from one shared naming sheet. This costs nothing and makes every session's entry point attributable. Its limit is equally clear: UTMs describe how a session started, not how sessions connect. They cannot join Tuesday's phone visit to Friday's laptop conversion.

GA4's path tools — useful, and where they stop

GA4 gives you two relevant views: conversion-path reporting in the Advertising section and path exploration in Explore. Both are worth using, and both share the same structural limits:

• Aggregate patterns, not individual paths. You see that "organic → direct → direct" is common — not which prospects took it or what they did within it.
• Cookie-scoped. A cleared cookie or a device switch starts a new "user"; the path resets. This is why conversion paths skew short and why direct swells — broken trails get bucketed as direct, a measurement symptom that masquerades as a channel.
• On-site only. Ad impressions that were seen but not clicked, and pre-visit research, don't exist in the path at all. The path starts mid-story.

Use GA4 paths for what they're good at — spotting gross patterns and funnel leaks (more in journey analytics vs GA4) — and don't ask them for causality they can't carry.

Whole paths: rebuild them around a person, not a cookie

The reason paths fragment is that the join key — a cookie — is fragile. Person-level path tracking replaces it with identity: each touch resolves to a verified individual, so the sequence survives devices, days, and cookie loss. Concretely, with BuyerJourney.net:

• Cross-device, cross-day touches join one sequence — deterministic identity resolution on 75–85% of matched traffic, no probabilistic guessing.
• The path starts before the visit — ad impressions and off-domain intent signals appear at the front of the sequence, where the story actually begins.
• History is recovered, not discarded — earlier anonymous sessions are retroactively stitched in once the person is identified.
• Paths end at revenue — closed-won deals connect back through the sequence, so each touchpoint carries an outcome, which is what makes path data usable for budget decisions. (That's also the foundation for attribution without cookies.)

FAQ

What is a conversion path?

The full sequence of touchpoints one person accumulates before converting — ads, visits, emails, across devices and days. The causal story lives in the path, not the final click.

How do I track paths in GA4?

Advertising → conversion paths, and Explore → path exploration. Both are aggregate, cookie-scoped, and on-site only — good for patterns, blind to individuals and off-site touches.

Why is "direct" so big in my conversion paths?

Broken trails: cookie loss and device switches sever history, and the converting session arrives with none. Direct-heavy conversion paths are usually a measurement artifact.

What does person-level path tracking add?

Paths rebuilt around verified individuals: cross-device joins, pre-visit touches, retroactive stitching, and revenue at the end. See the tracking-tools guide for where this sits in the stack.