Skip to main content

​
Quick comparison

FeatureLink SurveysWebsite & App Surveys
Best forKnown touchpointsBehavior-based intercepts
SDK requiredNoYes
DeliveryEmail, SMS, push, or webviewTriggered in-app by SDK
SegmentationYou control externallyBuilt-in via Formbricks
Survey fatigue preventionYou control externallyAutomatic
User identificationPersonal LinksSDK user attributes
Also known as invitation-based surveys. No SDK needed. You control when and who receives the survey, often through CRMs, marketing tools, or similar platforms. Link survey example

​
Delivery channels

  • Email
  • SMS
  • Push notification
  • In-app webview

​
URL features

​
Webview with Embed mode

For mobile apps, you can display Link Surveys in a webview with full control over when the survey appears. Your app decides the timing—open the webview when the moment is right. Enable Embed mode by appending ?embed=true to the survey URL: 
https://app.formbricks.com/s/<surveyId>?embed=true&userId=123
Listen for events to close the webview automatically: 
window.addEventListener("message", (event) => {
  if (event.data === "formbricksSurveyCompleted") {
    closeWebView();
  }
});
This approach gives you full control:
  • When: Your app opens the webview at the right moment (after purchase, case closed, etc.)
  • Who: Personal links allow you to have unique links for identified contacts.
  • Display: Survey renders inside your app
  • Dismissal: Close the webview on completion or user exit
Learn more in the Embed Surveys guide.

​
When to use

  • You already decide externally who should receive which survey
  • Survey timing is tied to a known event such as a click on a link or button and in each case, you want to show the survey
  • You want fastest approach to production
  • Your platform doesn’t have a supported SDK
  • You don’t need Formbricks attribute-based targeting & survey fatigue controls

​
Website & App Surveys (SDK)

Also known as intercept surveys. Requires SDK integration. Formbricks handles targeting, triggering, and survey fatigue. In-app survey example

​
In-app features

Action tracking Track in-app events and trigger surveys based on them: 
formbricks.track("action_name");
Built-in survey cooldown
  • Global waiting time (e.g., show max 1 survey every 7 days per user)
  • Per-survey overrides for high-priority surveys
Segment-based targeting Target surveys based on user attributes (plan type, language, feature flags). In-app display Surveys appear inside your app as modals or slide-ins.

​
When to use

  • You want Formbricks to handle who sees which survey
  • Surveys should trigger based on user behavior (page views, clicks, custom events)
  • You want automatic survey fatigue prevention
  • You need percentage-based sampling (e.g., show to 10% of users)

​
Decision guide

Use Link-based Surveys. Send the URL when the moment is right, even for in-app surveys.Pass context via Hidden Fields.
Use Website & App Surveys. The SDK tracks actions and triggers surveys automatically.
Use Website & App Surveys. Built-in cooldown prevents over-surveying.
Start with Link Surveys. No SDK integration needed. Add SDK later if you need behavior-based triggers.
Need help? Join us in GitHub Discussions