In-product surveys overview
In-product surveys show FromUsers questionnaires inside your website or web app through a lightweight JavaScript SDK. Visitors respond in context instead of leaving for a separate link (though a respond link still exists for testing).


When to use in-product surveys
Section titled “When to use in-product surveys”- Post-purchase or post-activation feedback on real pages.
- Feature satisfaction after a user completes a key action.
- Exit-intent or scroll-based intercepts on marketing pages.
- Continuous discovery with frequency caps so you do not over-survey.
Use a standalone survey when you recruit by email or Prolific. Use a usability test when you need prototype tasks and recordings.
How it fits together
Section titled “How it fits together”| Piece | Role |
|---|---|
| Website | Org-level install target with an ID |
| SDK script | fromusers-sdk.js with API key and website ID |
| In-product survey | Content, display mode, targeting, triggers, frequency |
| JavaScript API | FromUsers.init, showSurvey, trackEvent, submitResponse |
| Results | Impressions and responses in Results Studio |
Shared with other study types: pages, sections, logic, variables, branding, translations (21 languages), endings, screeners, and legal pages.
Display and targeting at a glance
Section titled “Display and targeting at a glance”- Display modes: modal, banner, embedded, toast. See Display modes and layout.
- Page targeting: URL contains, equals, starts with, regex, params, plus devices and traffic percentage. See Page targeting.
- Triggers: time on page, element click, hover, input, scroll depth, exit intent, custom JS event. See Triggers.
- Frequency: once ever, once per session, custom interval. See Frequency and quarantine.
- Audience rules: user attribute conditions and dynamic values. See Audience and dynamic values.
End-to-end path
Section titled “End-to-end path”- Create a website.
- Install the SDK.
- Create an in-product survey.
- Configure display, targeting, triggers, and frequency.
- Preview, set Live, and monitor impressions and results.
- Use troubleshooting when surveys do not appear.
Status labels
Section titled “Status labels”| Label | Meaning |
|---|---|
| Draft | Building |
| Live | Eligible to show when rules match |
| Paused / Inactive | Not showing |
| Closed | Finished |
Related
Section titled “Related”Common questions
Do I need an npm package?
No. Install the fromusers-sdk.js script with your API key and website ID. There is no npm package for the in-product SDK.
How is this different from a regular survey?
In-product surveys appear inside your site based on targeting and triggers. Standalone surveys rely on respond links, email, or Prolific.
What statuses will I see?
Studies still use Draft, Live, Paused, and Closed. In-product lists often emphasize Live versus Inactive when a survey is not collecting.
Who owns websites?
Websites are organization-level install targets. Multiple in-product surveys can target the same website.