Basics
Master the core concepts of SenseFolks to create effective surveys and gather meaningful user insights. This guide covers essential terminology, architecture, and best practices.
Core Concepts
What is a Survey?
A survey is a configured questionnaire with one or more steps. Each survey has a unique key (UUID) that identifies it when embedded on your site. Surveys are created in the dashboard and rendered by web components.
What are Survey Components?
Survey components are custom HTML elements (web components) that render your surveys. Each component type is optimized for a specific research goal:
<sf-fastpoll>— Quick polls and validation<sf-userchoice>— A/B preference research-
<sf-pricepoint>— Van Westendorp pricing research -
<sf-openfeedback>— Qualitative feedback collection -
<sf-featurepriority>— Feature prioritization ranking
What is a Survey Key?
Every survey has a unique identifier (UUID) called the survey key. This key connects your embedded component to your survey configuration and routes responses to the correct dashboard.
<sf-fastpoll survey-key="a1b2c3d4-e5f6-7890-abcd-ef1234567890"></sf-fastpoll>What are Responses?
When users complete a survey, their answers are stored as responses. View and analyze responses in the dashboard, export them to CSV/JSON, or access them via API for custom integrations.
Platform Architecture
SenseFolks consists of three main parts that work together:
Dashboard
Web application for creating surveys, configuring questions, and analyzing responses with real-time charts.
Web Components
Embeddable survey components that render on your website. Framework-agnostic and under 15KB.
APIs
Backend services that store survey configurations and collect responses securely.
Terminology
| Term | Definition |
|---|---|
| Survey | A configured questionnaire with one or more steps |
| Step | A single screen or question within a survey |
| Response | A completed survey submission from a user |
| Component | The web component that renders a survey type |
| Survey Key | Unique identifier (UUID) for a survey |
| CSS Parts | Styling hooks exposed by components for customization |
| Completion Message | Text shown to users after submitting a survey |
Survey Best Practices
- ✅ Keep surveys short (1-3 questions)
Micro-surveys get 2-3x higher completion rates than long forms
- ✅ Embed contextually
Place surveys where users can provide informed feedback (pricing page, feature area, etc.)
- ✅ Match component to research goal
Use PricePoint for pricing, FeaturePriority for roadmap, FastPoll for quick validation
- ✅ Test before launching
Preview surveys and verify the user experience across devices