How do I track a prototype with Fiuto?
Fiuto tracking adds an event stream from an instrumented prototype to the attached launch. Ask the agent that can edit the prototype to install the tracker, then verify it before sharing the study.
The current tracker does not bind these events to an individual Fiuto response. Review the tracker event stream separately from respondents’ block answers.
What tracking does
Section titled “What tracking does”The tracker records:
- Click selectors and accessible names.
- Route changes, with query strings and URL fragments removed.
- Form focus, blur, and submit events, without entered values.
- Task-completion signals configured by the prototype.
- Browser errors after redaction.
Each event includes a timestamp. Fiuto does not currently provide a respondent-by-respondent journey that combines these events with study answers.
When tracking fits
Section titled “When tracking fits”Use tracking when your agent built a live web prototype and you want an event stream from it. For a static image or Figma prototype, use a First-click test, Image click test, or Live prototype block instead.
Add tracking
Section titled “Add tracking”Ask the agent that can edit the prototype:
“Add Fiuto tracking to this prototype. Attach it to my study called ‘Onboarding flow test’.”
The agent finds the prototype’s entry point, installs the tracker, and attaches it to a Fiuto launch. Anyone who opens the instrumented prototype can generate tracker events, whether they arrived through the study or opened the prototype directly.
A typical workflow
Section titled “A typical workflow”- Build the prototype in your agent of choice.
- Create the Fiuto study.
- Ask the agent to attach tracking to the study and install it in the prototype.
- Open the instrumented prototype and click through it.
- Ask the agent to verify the tracker and read the latest tracker events.
- Share the study when the expected events appear.
You can build the prototype or study first. Attaching the tracker connects the prototype’s event stream to the launch.
Verify the tracker
Section titled “Verify the tracker”- Open the instrumented prototype.
- Click and navigate through it.
- Ask your connected agent to verify the tracker.
- Ask the agent to read the latest tracker events for the attached study.
If those events appear, tracking is working. Repeat this check after a change that may have replaced the prototype’s entry point or removed the tracker.
Default privacy behaviour
Section titled “Default privacy behaviour”- Entered field values are not captured by default.
- Route events omit URL query strings and fragments.
- Tracking does not guarantee that events contain no personal information. Accessible names, field names, paths, and redacted error metadata can still identify someone.
- Tracking only fires inside the instrumented prototype. It does not record activity in other tabs or apps.
If typed input matters to the research, collect it in a study question instead.
When the agent cannot add tracking
Section titled “When the agent cannot add tracking”The agent needs access to the prototype’s code and a clear browser entry point. It also needs an active Fiuto connection. If one of those is missing, fix it and ask the agent to attach the tracker again.
If you are stuck, write to help@fiuto.ai with the tool that built the prototype and what happened when the agent tried to add tracking.
Tell respondents what is recorded
Section titled “Tell respondents what is recorded”Tell respondents that activity inside the prototype will be tracked before they open it. Name the events you collect and explain how you will use them. Do not promise that tracker events cannot contain personal information: field values and query strings are omitted by default, but accessible names, field names, paths, and error metadata can still carry it.