An event experience can respond to a visitor without learning who they are. Let someone choose a goal, a product use case, or a difficulty level, then show a result for that choice. That is session-level tailoring. It differs from storing an identity, building a profile, or connecting a visit to later marketing. Choose the lightest level that answers the visitor's question, then test whether people use it.
The distinction matters because a feature can sound valuable in an interview and still be skipped in use. In a University of Washington master's thesis, Gracie Loesser interviewed 34 visitors at the Cleveland Museum of Art's Gallery One. Interviewees valued personalization, yet most did not use the particular personalization features. This is a small qualitative museum study, not a controlled event test; it warns against treating stated appreciation as feature adoption. Loesser, 2016 university summary.
Sundar and colleagues ran a 2×2×2 experiment with 126 participants in an online virtual museum, varying customization, live chat, and 3D navigation. Customization was associated with a sense of agency and control, but combining all the tested affordances tended to undermine their distinct benefits. The context was an online gallery, not an event kiosk; it does not prove that any particular live-event choice improves conversion. Sundar et al., International Journal of Human–Computer Interaction, 2015.
Choose one of three levels
Same answer for everyone. Use this when the core idea is a shared demonstration and choices would add work without changing the answer. Choice during this session. Ask one or two meaningful questions and give a result that visibly changes. Keep the choices understandable and include a default path. Remember the person. Link a result to an email, account, badge, or later visit only when that continuing relationship is part of the agreed outcome. These levels are an Archv planning framework, not a finding or prescription from the studies.
If personal information is proposed, specify the purpose and retention owner before adding a field. The FTC's business data-protection guide advises keeping information only for as long as there is a legitimate business need. This is general U.S. guidance, not a compliance determination for an event in another jurisdiction. A visitor can choose “I want to see the compact option” without the organizer needing their name or contact detail.
Test the value of the choice
Prototype a plain route and a short choice route. Ask first-time visitors to reach the result unaided. Watch whether they notice the choice, whether they understand why the result changed, and whether extra questions cause them to leave. Afterward, ask them to explain the result in their own words. Report use of the feature separately from stated liking, reflecting the thesis's central limitation. If the choice does not change a decision or understanding, remove it.
For shared devices, test that the next person starts fresh; the kiosk reset guide covers that handoff. If a visitor requests a follow-up, the event-to-website guide covers the later path. Keeping these decisions separate helps the interaction feel relevant without making an unnecessary identity system part of the first touch.