Troubleshooting

Why does my survey not appear?

1. Load the package that matches the survey tag, using type="module" for CDN scripts.
2. Check that the component bundle loads and the console has no registration errors.
3. Use the active survey's UUID as survey-key.
4. In SSR frameworks, load the package in the client lifecycle.
5. If the survey requires Session Data, assign the complete object before setting the key.

See embedding examplesand the Session Data guide.

Why is my survey permanently disabled?

Deleting a website permanently disables its surveys. Remaining embeds show “Survey has been permanently disabled” and cannot collect responses.

Remove the old embed. To collect new responses, create a website and survey, then install the new embed. Deleted data cannot be restored.

See survey deletion rules.

Why do my survey styles not apply?

Shadow DOM blocks ordinary page selectors. Use ::part() and a part name exposed by your component version.

Start with the styling tutorial and check the CSS Parts reference.

Why do survey events not fire?

1. Check event support: UserChoice and FeaturePriority emit sfError only.
2. Attach listeners to the mounted survey element before the event occurs.
3. Match casing exactly, such as sfReady or sfSubmit.
4. Keep enableEvents enabled in FastPoll and OpenFeedback.

See the events reference for supported events and listener cleanup.

How do I fix API or CORS errors?

A 403 response with Access denied based on origin means the embed origin was rejected.

1. Compare the page origin, such as https://example.com, with the Website URL and survey Embed URL in SenseFolks.
2. Set both URLs to the origin where the survey runs, including the protocol and correct hostname.
3. Check whether a browser extension blocks the request.
4. If it still fails, send the request ID and error to support.

See dashboard setup for website configuration.