Question 1

What are in-app surveys?

Accepted Answer

In-app surveys show up inside your product while someone is actually using it, in your web app or your mobile app, instead of landing in their inbox later. You might also hear them called in-product surveys or pop-up surveys, all describing the same idea: ask the question in the moment it's most relevant, right where the person already is.

Question 2

What kinds of surveys can I run in-app?

Accepted Answer

Start from a template for NPS, CSAT, CES, or product-market fit, or build a fully custom survey with your own questions, logic, and branding. The same in-app survey engine powers all of them.

Question 3

What is server-side user targeting?

Accepted Answer

It's how Survicate recognizes the same person across sessions and devices, so they never see the same survey twice. We track your logged-in users by their user ID on our servers, not just in their browser. If someone opens your app on their phone after using it on desktop, they're still recognized as the same person, and your targeting, frequency, and recurrence rules apply consistently. It works for any user you can identify with a user ID, which makes it the right choice for surveys inside your product.

Question 4

Can I control how often a survey repeats, or cap how many times someone sees it?

Accepted Answer

Yes. Set a survey to repeat on a schedule (daily, weekly, monthly) or to trigger every time someone meets your targeting criteria again. You can also cap how many times one person sees it, so a monthly survey doesn't run forever for the same respondent.

Question 5

Can I run in-app surveys on both web and mobile?

Accepted Answer

Yes. In-app surveys run inside your web app and your mobile app, each through its own SDK. Setup and the exact targeting options differ a little between the two, so check the docs for your platform before you build.

Question 6

Do I need a developer to set this up?

Accepted Answer

Getting the SDK live is usually a quick install, five minutes of a developer's time. After that, most day-to-day survey building doesn't need code. The exception is advanced targeting: triggering a survey off a specific product event, or targeting logged-in users by their attributes, usually needs a developer to pass that data to Survicate, unless you already connect through Segment. Then it's just a toggle.

Question 7

Can I trigger a survey based on something a user does, not just a page they visit?

Accepted Answer

Yes. You can trigger a survey the moment someone does something specific, like completing checkout or hitting a paywall, instead of only when they land on a page. On mobile, pass the event through our SDK and pick it as a trigger. On web, event-based triggers work through Google Tag Manager or our JavaScript SDK today.

Collect user feedback in-app

Understand users in the moment

Reach the right users

Capture feedback in context

Keep surveys on-brand

Turn responses into action

Built for modern tech stacks

Target beyond basic segments

Surveys that feel native to your product

Reach users in their native language

Analyze feedback in customizable dashboards

Turn customer feedback
into what's next

Survicate

Research Hub

Survicate MCP

Make feedback part
of your stack

Frequently asked questions

Survicate has your (feed)back