Troubleshoot in-product surveys
When an in-product survey does not show, work top-down: status, install, targeting, trigger, then frequency.
1. Confirm study status
Section titled “1. Confirm study status”| Status | Effect |
|---|---|
| Draft | Will not collect for real visitors |
| Live | Eligible to show |
| Paused / Inactive | Hidden |
| Closed | Finished |
Open In-Product Surveys, find the study, and set it Live if you intend to collect.
2. Verify the SDK install
Section titled “2. Verify the SDK install”- Load the page.
- In network tools, confirm
fromusers-sdk.jsreturns success. - Confirm
data-api-keyanddata-website-idmatch the website selected on the survey. - Check the console for script or CSP errors.
See Install the SDK.
Content Security Policy
Section titled “Content Security Policy”If your CSP blocks the script host or inline evaluation the SDK needs, surveys will not load. Ask engineering to allowlist the FromUsers script origin used in your snippet.
Ad blockers
Section titled “Ad blockers”Some blockers strip survey scripts. Test in a clean profile. Measure impressions with that bias in mind.
3. Recheck targeting
Section titled “3. Recheck targeting”- Compare the browser address bar to your URL rules (contains, equals, starts with, regex, params).
- Confirm device rules allow your current device.
- Set traffic percentage to 100% while testing.
- Remember SPA route changes may need a refresh or custom events.
See Page targeting.
4. Recheck triggers
Section titled “4. Recheck triggers”| Symptom | Likely cause |
|---|---|
| Never shows | Timer too long, selector wrong, event name mismatch |
| Shows too early | Timer too short or trigger too broad |
| Desktop only works | Exit intent or hover on mobile |
Fire FromUsers.trackEvent manually from the console when testing custom events. See Triggers and JavaScript API.
5. Reset frequency during QA
Section titled “5. Reset frequency during QA”If you already dismissed the survey:
- Try a private window.
- Clear site data for your staging origin.
- Temporarily use a more permissive frequency on staging only.
Production should keep strict frequency and quarantine.
6. Audience attributes
Section titled “6. Audience attributes”If audience rules require plan=pro but FromUsers.init never sends plan, the survey will not show. Log the payload you pass to init and align names with the rules.
7. Manual show test
Section titled “7. Manual show test”FromUsers.showSurvey("YOUR_SURVEY_ID");Use the survey identifier FromUsers provides in the product UI (do not invent routes). If manual show works but automatic show does not, the problem is targeting, trigger, or frequency rather than install.
Still stuck?
Section titled “Still stuck?”- Reproduce on staging with one minimal Live survey (one page, one question, time trigger, 100% traffic).
- Capture console errors and network failures.
- Confirm another teammate sees the same result on a fresh browser.
- Pause conflicting Live surveys that might quarantine the visitor.
Related
Section titled “Related”Common questions
The survey never appears. What should I check first?
Confirm the study is Live, the SDK loads for the correct website ID, and your URL matches targeting. Then verify frequency did not already hide it for your browser.
It works on staging but not production.
Compare website IDs in each snippet, confirm the production survey targets the production website, and check CSP or ad blockers on production.
showSurvey does nothing.
Ensure window.FromUsers exists, the survey is Live, and frequency or quarantine are not blocking. Check the browser console for errors.