Start Free Tier

Basics

This page explains the core SenseFolks concepts and the practices that help you collect useful data.

How SenseFolks Works

Keep it simple: set up one website container, launch surveys, then read all responses in one dashboard.

  • 1. Add your website

    Create a website container in the dashboard. It keeps related surveys and insights together.

  • 2. Create and embed surveys

    Choose a survey type, copy the survey key, and embed the component where users make decisions.

  • 3. Review insights and decide

    Responses sync in real time, so your team can spot patterns and act quickly.

Core Concepts

Surveys

A survey is a configured questionnaire with one or more steps.

Each survey belongs to a website container and has a unique key (UUID) that identifies it when embedded on your site.

You create surveys in the dashboard and they render on your site as web components.

Survey Components

Survey components are custom HTML elements (web components) that render your surveys on any page. Each type is built for a specific research goal:

  • <sf-pricepoint> — Find the right price (Van Westendorp, Gabor-Granger)
  • <sf-userchoice> — See which trade-offs people prefer (Conjoint Analysis)
  • <sf-featurepriority> — Sort features by what users care about (Kano, MaxDiff, Bradley-Terry)
  • <sf-fastpoll> — Get a quick signal on any question
  • <sf-openfeedback> — Collect open-ended feedback
  • <sf-reaction> — Test reactions to content (emoji, binary, or single-icon)

Survey Keys

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.

html 
<sf-fastpoll survey-key="a1b2c3d4-e5f6-7890-abcd-ef1234567890"></sf-fastpoll>

Responses and Insights

Survey submissions are stored as responses. You can view them in real time, filter by date or survey, and export to CSV or JSON.

Terminology

Term What It Means
Website A container for your surveys and insights. Add one per product or site.
Survey A configured questionnaire with one or more steps, living inside a website container
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 on your page
Survey Key Unique identifier (UUID) that connects an embedded component to its survey
CSS Parts Styling hooks exposed by components so you can customise appearance
Insights Dashboard Where aggregated results from all surveys within a website are displayed

Best Practices

  • Keep each survey focused on one decision

    Ask one clear question per survey so responses are easier to interpret and act on.

  • Embed where decisions happen

    Place surveys at relevant moments in your product for clearer, higher-intent responses.

  • Keep surveys short (1-3 questions)

    Short surveys usually get better completion rates and cleaner data.

  • Match the survey type to your question

    Use PricePoint for pricing, UserChoice for trade-offs, FeaturePriority for roadmap priorities, and FastPoll for quick checks.

  • Don't combine unrelated goals

    Mixing pricing, usability, and feature prioritisation in one survey makes results noisy and hard to trust.

  • Don't skip preview and QA

    Test wording, layout, and device behaviour before publishing. A confusing question produces confusing data.

Next Steps