---
title: "How to save visitor data from any workflow step?"
description: "Turn on Save to visitor profile on a workflow step to record a tapped choice, a milestone or the scanned link's context on the visitor, without asking another question."
canonical: "https://linkbreakers.com/help/article/how-to-save-visitor-data-from-any-workflow-step"
last-updated: 2026-10-03
---

# How to save visitor data from any workflow step?

> Turn on Save to visitor profile on a workflow step to record a tapped choice, a milestone or the scanned link's context on the visitor, without asking another question.

## Short answer

Open a step in your workflow, or create one, and switch on **Save to visitor profile**. From then on, every visitor who goes through that step gets the values you chose saved on their profile: the button they tapped, the date they reached a milestone, or details of the QR code they scanned. Forms already save every answer; this works on the other steps, so you can qualify a lead without asking more questions.

## Quick summary

- Available on every step a visitor goes through: the link visit, multi-link pages, password steps, forms, message pages and every exit. Conditions don't have it.
- Switching it on fills in sensible defaults. You can rename keys, change values or add more, up to 20 per step.
- Saved values appear on the [visitor](https://linkbreakers.com/help/article/what-is-a-visitor-in-qr-analytics-and-why-it-matters), in visitor filters, in [visitor data conditions](https://linkbreakers.com/help/article/how-to-use-visitor-data-conditions) and in [webhooks](https://linkbreakers.com/help/article/how-do-webhooks-work-in-linkbreakers).
- Each step's entry in the activity timeline shows what it saved.

## What gets saved by default

When you switch it on, the step starts with a value that matches what it does:

| Step | Saved by default | Example |
|---|---|---|
| Multi-link page | The button the visitor tapped, under a key taken from your question | "What are you looking for?" saves `looking_for = Buying` |
| Redirect, contact card, thank-you, social links, message page, password, form | The date and time the visitor reached, unlocked or submitted it | "Book a viewing" saves `visited_calendly_at = 2026-10-03 14:32` |
| Link visit (entry) | Each metadata value set on the link | A yard sign with `property_id: AMS-1943` saves `property_id = AMS-1943` |

Keys are suggested from attributes your workspace already uses, so the same answer collected on different links lands on the same attribute.

## What a value can contain

A value is plain text, or one of these placeholders, filled in when the visitor goes through the step:

- **Button tapped**: the label of the button they chose (multi-link pages only)
- **Date and time**: when they reached the step
- **Link name**: the name of the link they scanned
- **Link metadata**: any metadata value set on the link, such as a property ID, a store or a car's VIN

Pick a type for each value (text, choice, number, yes / no or date) so you can filter and compare on it later. Tick **Keep first value** to record first-touch facts that later scans should not overwrite.

## Example: qualifying a buyer from a yard sign

1. Give each sign's link a `property_id` in its metadata, and switch on saving at the link visit. Every visitor records which property they scanned.
2. Add a multi-link page asking "What are you looking for?" with Buying, Renting and Just looking. Switch on saving: it records `looking_for`.
3. Connect the Buying button to a "Book a viewing" redirect. Switch on saving there: it records when they asked for a viewing.
4. In Visitors, filter on `looking_for` equals Buying to see every buyer, with the property they came from.

## Limits and caveats

- Conditions don't have this setting, since they only route on what is already known. On a form, it saves on top of the answers, which forms already save.
- A failed password attempt or a skipped form saves nothing.
- A value that comes out empty, such as a metadata key the link doesn't have, is skipped rather than saved blank.
- Keys can use letters, digits, `_`, `-` and `.`. Email, phone and name are set by forms and the API, not by this setting.
- Values are saved within seconds of the visitor going through the step, so a condition placed immediately after the step may not see them yet.

## FAQ

**Do I have to configure keys myself?**
No. Switching the setting on fills in a key and a value based on the step. Rename them only if you want to.

**Can the Assistant set this up?**
Yes. Describe what you want to record, for example "save which option they pick", and the Assistant configures the step, reusing keys your workspace already has.

**Can I turn it off without losing my settings?**
Yes. Switching it off stops saving but keeps the keys and values you configured.

**Is this available through the API?**
Yes. Send `attribute_capture` when creating or updating a workflow step through the REST API, the SDKs or the MCP server.