What a journey looks like when you stop counting clicks

Pull up any customer's journey in your analytics tool and you'll see a series of events: page viewed, button clicked, form started, form abandoned, page viewed again. It looks like a story. It isn't. It's an inventory.

An inventory tells you what happened. A story tells you what mattered. The difference is enormous, and almost every analytics setup is optimized for the first while pretending to deliver the second.

Here's a pattern we keep seeing. A SaaS company tracks 40 or 50 events per visitor session. They aggregate those events into conversion funnels, maybe score them with some intent model. The dashboard says "this person visited pricing 3 times, opened 2 case studies, and watched the demo video to 80% completion." The lead gets a high score. Sales calls. The person is polite and not at all ready to buy.

Meanwhile, someone else visited the site twice over two weeks. The first time, they read a single documentation page for 9 minutes. The second time, they went straight to pricing, toggled between two plans, and submitted a form. That person closes in 4 days.

The click counts on these two journeys are not even close. The first person generated 15x more events. But the second person's path had something the first one didn't: a recognizable shape. A question, then a return with apparent conviction. Two visits, one arc.

When we say "the journey is the unit," we mean something specific. Not that you should look at journeys instead of sessions — most tools already stitch sessions together. We mean you should read the journey as a single gesture, the way you'd read a sentence instead of counting its letters. The letters matter, but only because they form words, and the words matter only because they form a meaning. Counting letters faster does not improve your reading.

The habit of counting clicks comes from an era when getting any behavioral data at all felt like a superpower. And it was. Knowing that someone visited your pricing page was, for a long time, genuinely useful signal. But that era is over. Now everyone tracks everything, and the problem has flipped. You're drowning in letters and starving for sentences.

What changes when you treat the journey as a shape instead of a sum? For one, you start noticing pauses. The 6-day gap between visit one and visit two becomes information, not dead air. A person who disappears for a week and comes back to a different part of your site is telling you something — they went and talked to someone, or tried a competitor, or got budget approval. You can't know which, but you can see that the pause exists and that what follows it is different from what came before. That transition is the interesting part. No click counter will surface it.

You also start noticing repetition differently. Three visits to the same integration docs page looks like engagement in a click model. Read as a journey, it might be confusion. The person can't find what they need. The high event count is actually a distress signal, not a buying signal.

There's a fair objection here: shapes are harder to automate than counts. You can't easily set a threshold on "this journey has a recognizable arc." That's true. And it means this kind of reading doesn't scale the way a lead score does. But the question worth asking is whether the lead score was actually scaling insight or just scaling confidence. A number that goes up feels like knowledge. Often it's just motion.

None of this requires throwing away your event tracking. The events are the raw material. But raw material arranged on a shelf is a warehouse, not a workshop. The difference is whether someone is reading what the material says — patiently, in sequence, with attention to the silences between the clicks.

The most interesting customer paths are almost never the busiest ones. They're the ones with a clear beginning, a visible turn, and a quiet resolution. You just have to be willing to read them slowly enough to notice.