Create an in-product survey
Create an in-product survey after you know which website will host it and what moment in the product should trigger feedback.
Prerequisites
Section titled “Prerequisites”- Organization Admin or Member with Editable access.
- A website created (or create one during setup).
- SDK install planned or already done. See Install the SDK.
Create the study
Section titled “Create the study”- Open In-Product Surveys.
- Choose New in-product survey.
- Name it clearly (for example, “Settings satisfaction modal”).
- Select a workspace.
- Open the editor in Draft.
Attach website and basics
Section titled “Attach website and basics”- Open Configure.
- Select the website this survey belongs to.
- Confirm title and default language.
- Add legal pages if required.
One organization can have many websites. Each survey targets one install context through its website selection and targeting rules.
Build questions
Section titled “Build questions”- Open Build.
- Keep in-product surveys short. Visitors did not opt into a long questionnaire.
- Prefer one focused rating plus an optional open text field.
- Add an ending that dismisses cleanly.
- Apply Brand so the survey matches your product chrome where possible.
Avoid interactive usability tasks. Those belong in usability tests.
Display, targeting, and triggers
Section titled “Display, targeting, and triggers”Configure, in roughly this order:
- Display mode and layout (modal, banner, embedded, toast).
- Page targeting (URL rules, devices, traffic %).
- Triggers (time, click, scroll, exit intent, custom event).
- Frequency and quarantine.
- Audience and dynamic values when you pass user attributes.
Preview and go Live
Section titled “Preview and go Live”- Preview content inside the editor.
- On a staging site with the SDK, trigger the survey manually if needed via the JavaScript API.
- Set status to Live.
- Verify impressions appear. See Impressions and results.
Example
Section titled “Example”Checkout thank-you feedback:
- Website: production marketing and app site.
- Display: modal.
- Targeting: URL contains
/checkout/success. - Trigger: time on page 5 seconds.
- Frequency: once ever.
- Two questions: satisfaction rating and optional comment.
Related
Section titled “Related”Common questions
Can I create the survey before installing the SDK?
Yes. Build content in Draft first, but you need a website and the SDK installed before real visitors can see it.
Do in-product surveys support logic and translations?
Yes. Use the same logic, variables, branding, and translation tools as other study types.
Who can create in-product surveys?
Admins and Members with Editable workspace access. Viewers cannot create studies.