What is a visitor journey?

Short answer

A visitor journey in Linkbreakers is the record of how far one visit (a scan or a click) got through a link's workflow. For each visit, Linkbreakers stores how many of the workflow's steps the visitor reached, how many steps were on their path to an exit, and whether they reached the end.

The journey is a fact about the visit. It is not a score and not a judgment of the visitor. You decide what "qualified" means by designing the workflow steps, and the journey tells you how far each visitor went through them.

Quick summary

• Every visit records steps reached, steps on the path, and whether the visitor reached an exit
• Conditions are not counted because visitors never see them
• The dashboard Live view shows a "Journey" column with a progress wheel
• CSV exports include journey_steps_reached, journey_steps_total, journey_completed, and journey_progress
• Webhooks, Slack notifications, the API, and the MCP server all carry the same journey data

Understanding the journey

What the journey measures

A link's workflow is a sequence of steps such as forms, password gates, multi-link pages, and contact cards, ending in an exit (the final destination). Each visit follows one path through that workflow. The journey records three facts about that visit:

Conditions (country, device, time, scan/rescan, visitor data) route visitors between steps, but visitors never see them, so they are not counted as steps.

Why it is not a score

The journey does not rate visitors, predict conversion, or weigh signals. Two visits that both stop at step 2 of 5 have the same journey, whatever device or location they came from. What makes a visitor a good lead is up to you: the visitor record holds the free key/value attributes your workflow collects, and the steps you put on each link decide what a visitor must do to get through.

Where to find the journey

In the dashboard

The Live view has a "Journey" column with a progress wheel for each visit. The wording reads like this:

• "Reached the end · 4 of 4 steps"
• "Stopped at step 2 of 5"
• "No steps recorded for this visit yet"

In CSV exports

Event CSV exports include four journey columns:

In webhooks

Each event payload sent by webhooks carries a journey object:

{
  "journey": {
    "stepsReached": 2,
    "stepsTotal": 5,
    "completed": false
  }
}

In Slack notifications

Slack notifications include a journey line, for example "Journey: Stopped at step 2 of 5" or "Journey: Reached the end · 4 of 4 steps".

In the API and MCP server

Request events with the journey included:

GET /v1/events?include=journey

Each event then returns a journey object with stepsReached, stepsTotal, and completed. The same data is available through the MCP server with the events_list tool and the journey include.

Using the journey in practice

Qualify visitors with workflow steps

Put the questions that matter to you on the link's workflow: a form that asks for company size, a step that only serious prospects will go through, a password gate for invited guests. A visitor who reached the end has gone through every step you put on their path.

Spot where visitors drop off

"Stopped at step 2 of 5" tells you exactly where a visit ended. When many visits stop at the same step, that step is the one to shorten, reword, or move. For aggregated drop-off per step, see how to measure QR code funnel performance.

Route follow-up with automation

Because webhooks, Slack, and the API carry completed and the step counts, your own tools can act on them. For example, a Zapier filter can send visits that reached the end to your CRM and send visits that stopped early to a retargeting list.

Frequently Asked Questions

Is the journey a score?

No. Linkbreakers does not score or rank visitors. The journey only records how far a visit got through the workflow. Qualification comes from the steps you design and the attributes you collect.

Why are conditions not counted?

Conditions route visitors silently and are never shown to them, so counting them would make progress look different for visitors who saw the same pages.

Why does "steps total" differ between visits on the same link?

Steps total counts the steps on that visitor's path to an exit. If conditions send visitors down different branches, each branch can have a different number of steps.

What does "No steps recorded for this visit yet" mean?

The visit exists but no workflow step has been recorded for it yet.

Can I export journey data?

Yes. Event CSV exports include journey_steps_reached, journey_steps_total, journey_completed, and journey_progress, and the API returns the journey with include=journey.

What's the difference between a journey and a visitor profile?

A visitor profile holds identity and attributes across visits. A journey belongs to one visit of one link. A visitor who scans three times has three journeys.

Limits and caveats

• The journey describes one visit, not the visitor across all visits.
• Conditions are not counted as steps.
• The journey is not a score, a ranking, or a prediction of conversion.