Survey Operations
Treat the dashboard configuration and the embed in your codebase as two parts of the same survey. Update both when you launch, replace, or remove a study.
Survey Lifecycle
- Drafting — define the research question and survey type
- Embedded Collection — gather responses wherever your website or app renders the survey component
- Removed from the page — stop rendering the embed in your own codebase
- Deleted — permanently remove a survey you no longer need
Dashboard and Codebase Actions
- Create — launch a new survey from the dashboard wizard
- Edit — revise copy, options, or settings for active studies
- Copy Embed Instructions — retrieve the public key and framework-neutral component instructions
- Remove Embed — stop rendering the component everywhere it appears in your website or application
- Delete — clean up old studies with a destructive-action confirmation
Before You Change a Live Survey
- Use a descriptive name with the location and goal, such as “Pricing page — acceptable range”
- Track major configuration changes in release notes or internal docs
- Avoid editing live surveys during critical reporting windows
- Remove superseded survey embeds from your product code
What Happens When You Delete a Website?
Website deletion is permanent. SenseFolks deletes the website's data and marks every survey inside it as disabled. Each embed checks that status whenever it loads and shows “Survey has been permanently disabled” instead of accepting a response.
Before you confirm deletion:
- Make sure you no longer need the website's survey data.
- Find every active or embedded survey owned by the website and remove it from your product code.
- Confirm that your deployed pages no longer render those embeds.
Deleting the website does not remove code from your site. If an old embed remains, visitors will see the permanent-disable error until you remove it.