Reading support tags beside the funnel

Application analytics teams sometimes treat the funnel as the whole story. Support teams treat tags as the whole story. Session quality sits between them.

The table we draw

For each critical step we list:

1. Exit rate or hesitation signal from your analytics export.
2. Top support tags created within twenty-four hours of that step.
3. One verbatim (redacted) sentence from a session or call that illustrates the tag.

When step two and step three disagree with step one, we dig. Often the funnel step is too coarse — “payment” hides a shipping estimator that updates after card entry — while support has already named the real object.

Why this helps session quality

People who recover still complete. Charts forgive them. Support tags remember the confusion. Putting both on one page stops teams from “fixing” the wrong surface.

Try it before you hire anyone

Export thirty days of tags for one path. Sit with a product manager for an hour. If you cannot map tags to screens, you already know what a Session Quality Audit would attack first: vocabulary alignment.

We use this table on nearly every Sydney engagement. It is unglamorous. It works.