# Letting visitors tell you who they are

URL: https://kywi-docs-production.up.railway.app/targeting/letting-visitors-tell-you-who-they-are
Type: docPage

What happens to a self-ID answer: it decides audiences on the server, is kept only with consent, and the page reflects it on the next load.

Self-ID is a visitor answering directly instead of being inferred from behaviour: you ask what brings them here, they pick, and their answer feeds the same audience rules everything else does. What they submit is written to a cookie the server reads back on every later render — arm selection happens there, so an answer only the browser knew about couldn't change what actually ships.

## The page changes on the next load, not in place

Submitting does not rearrange the page in front of the visitor. Every variant container you can build today is resolved on the server and ships only the arm that won, so there is nothing in the page for a client-side script to swap to (pages still carrying the pre-0.13.0 variant module are the one exception). What the submit does is record the answer and re-resolve the visitor's audience, so the *next* request — a navigation, a refresh — is rendered against it.

Design the widget with that in mind. If answering should visibly change the page, send the visitor somewhere afterwards rather than leaving them looking at content that hasn't moved. Without JavaScript this is automatic: the form posts and the browser is redirected straight back to the page, which the server then renders with the new answer.

## A pin behaves differently from a stored answer

A submission produces two things, governed differently. The *answers* themselves are stored data, so they fall under the personalization consent category: without consent they are not kept at all. The *pin* — the direct link from the submission to one audience — is a control the visitor operated by hand, so it is always honoured, but its lifetime depends on consent. Without consent it lasts the browser session: it changes the pages they are reading now and is forgotten when they close the browser. With consent it becomes durable, and the visitor stays in that audience across visits.

## Opting out beats a self-ID pin

A visitor who has turned personalization off can't be re-personalized by answering a self-ID form — opt-out is checked before the pin is written, so no pin is set and the answer has no effect on what they see.

## A submission that matches nothing clears the pin

If a visitor's answers don't resolve to any audience a self-ID pin could target, the existing pin is cleared rather than left pointing at whatever they answered before — a visitor who changes their mind mid-way doesn't get stuck on a stale answer.
