Troubleshooting
Use this page when surveys behave unexpectedly in production. Each section starts with a quick diagnosis checklist and then a reliable fix path.
Embed Not Loading
When To Use
The survey tag renders in HTML but no component appears on the page.
Quick Diagnosis
- Verify the package script import is present before your component tag.
-
Confirm network requests for the component bundle return
200. - Check console for custom element registration errors.
Fix
- Load the correct package (`@sensefolks/*`) for the tag you use.
- Render the tag only after script/module load in SSR frameworks.
- Confirm the `survey-key` belongs to an active survey.
Related Docs
Styles Not Applying
When To Use
Brand colors and typography work on your page but not inside survey UI.
Quick Diagnosis
-
Check if selectors target
::part(...)names, not internal DOM. - Inspect element to verify part names exist on that component version.
- Confirm CSS loads after the component stylesheet in your app bundle.
Fix
- Replace global selectors with exposed CSS Part selectors.
- Start with shared parts (`survey-container`, `heading`, `button`).
- Add component-specific part selectors only where needed.
Related Docs
Events Not Firing
When To Use
Analytics hooks or custom handlers never receive submit/ready events.
Quick Diagnosis
- Confirm listeners are bound to the custom element instance, not a wrapper.
- Verify event name casing (for example
sfReady). - Test with a minimal listener and log event details.
Fix
- Attach listeners after element mount.
- In React, use a ref and bind in an effect with cleanup.
- Verify survey completion path actually reaches submit state.
Related Docs
API or CORS Errors
When To Use
Survey requests fail with authorization, origin, or blocked preflight errors.
Quick Diagnosis
- Confirm website domain in SenseFolks exactly matches deployment domain.
- Check browser network tab for failing request and status code.
- Verify adblock/privacy extensions are not blocking request domains.
Fix
- Update website domain in dashboard and republish embed.
- Retry from a clean browser profile and confirm extension impact.
- If issue persists, capture request ID and contact support.