In-app surveys

In-app surveys for mobile and web products

Ask users in the moment that matters, inside the app they are already using.
In-app survey asking how easy the app is to navigate
15+ years on the market, trusted by 1,000+ organisations around the world to collect feedback and bring valuable insights
  1. Red Bull
  2. Schindler
  3. Bayer
  4. Booksy
  5. KraftHeinz
  6. Danone
In-app feedback

Ask inside the product, right after the thing you want to learn about

Answers arrive with the screen attached

You know which flow, which version and which device the opinion came from, so a report is a concrete fix, not a mood.

Nobody leaves the app

One or two questions on the screen someone is already using. No mailbox, no browser, no lost session.

You know who answered

The response carries the account, the plan and the attributes you already send us, so you can go back to that user with an answer.

Moments

The moments worth asking about

  • After onboarding

    Check whether the first steps were clear while the impression is a few minutes old.

  • After a purchase or an upgrade

    Measure satisfaction with the decision and catch what almost stopped it.

  • After using a new feature

    Find out whether what you shipped solves the problem it was meant to solve.

  • After a failed action

    A payment that did not go through or an error screen is the shortest path to a real usability problem.

  • After a support conversation

    A CSAT question straight after the chat, without a separate email that arrives the next day.

  • Before cancelling

    Ask about the reason at the moment of the decision, when the answer is still specific.

Look and feel

It looks like part of your app, not like a page in a frame

The survey renders through a native SDK, so it uses your fonts, colours and rounding, and it opens with the animation your users know. A single integration covers iOS, Android and cross-platform frameworks.

  • Native SDK for iOS and Android

  • React Native and Flutter with one integration

  • Your fonts, colours and rounded corners

  • Full screen, a card or a slide-in at the bottom

  • Works on phones and tablets, in portrait and landscape

In-app survey displayed on a phone screen
Context and results

Every answer with the user attached

Send us the account identifier and the attributes that matter — plan, tenure, lifetime value — and every response arrives with them. Results land in the same dashboard as the rest of your feedback, next to NPS, CSAT and CES from other channels, and travel further through integrations with your CRM and analytics.

  • User identification and your own attributes

  • Targeting by plan, cohort or segment

  • Frequency capping across all in-app surveys

  • NPS, CSAT and CES measured inside the product

  • Reports shared with the rest of your feedback

See feedback analytics
Dashboard with in-app survey results
We automated the process of monitoring every aspect of the product experience.
BNP Paribas

Tom Groenewald

Product Experience Manager

In-app survey features

Start for free

Native iOS and Android SDK

Surveys render as part of the app, not as a web page in a frame

React Native and Flutter

One integration for teams building on cross-platform frameworks

Event triggers

Ask right after a purchase, an upgrade or a failed action

Audience targeting

Reach a plan, a cohort or a single segment of your users

Native look and feel

Fonts, colours and rounding follow your app, not our defaults

Frequency capping

Set how often one person can be asked anything at all

User identification

Tie every answer to the account you already know

User attributes

Send plan, tenure or lifetime value along with the response

NPS, CSAT and CES in the app

Standard metrics measured where the experience happens

Hide after answer

Once someone responds or dismisses, the survey stays away

Privacy by design

No tracking of screens you have not chosen, data stored in the EU

Real-time reports

Results land in the same dashboard as the rest of your feedback

In-App Surveys FAQ

What is an in-app survey?

An in-app survey is a short questionnaire shown inside your mobile or web application, on the screen the user is already on. It is triggered by something that happened in the product — finished onboarding, a purchase, an error — instead of arriving by email hours later.

How do I add surveys to my app?

Install our SDK for iOS or Android, or the shared integration for React Native and Flutter, and send the events you want to react to. From then on surveys are created, targeted and paused in the panel, without shipping a new build.

Do I need to release a new app version for every survey?

No. The SDK goes in once. Content, targeting and display rules are configured on our side, so a new study goes live the same day, without waiting for app store review.

When should the survey appear?

Right after the event you want to learn about: the end of onboarding, a completed purchase, the first use of a new feature, a failed payment or a support conversation. The closer the question is to the moment, the more specific the answer.

Will the survey annoy my users?

Frequency capping limits how often one person can be asked anything at all, and a survey disappears for good once it is answered or dismissed. You can also target only a segment or a share of your users.

Can I connect responses to user accounts?

Yes. Pass the account identifier and any attributes you care about — plan, tenure, lifetime value — and each response arrives with them, so you can follow up with the specific user.

Which metrics can I measure in the app?

The standard set works inside the product: NPS, CSAT and CES, plus your own questions. Results sit in the same reports as feedback from other channels.

Will the SDK slow down or bloat the app?

The SDK is lightweight and does nothing until one of your events fires. It does not track screens you have not chosen, and the data is stored in the EU.

What about a web app that runs in a browser?

For products used in a browser, use website surveys — the same targeting and the same reports, delivered by a JavaScript snippet instead of a mobile SDK.