The App channel brings the survey inside your app, with your app's own screen. It is not a web page opened on top: your app asks WiseData NPS whether it can show the survey, receives the texts and builds the screen with its own look. Responses land in the same Feedback and reports as the other channels.
Throughout this article, the example is a personal finance app that wants to hear from people right after they close the month.
Why not use the website widget inside the app
The embed widget is made for browsers. Inside an app it loads slowly, doesn't use the device keyboard or haptics, feels foreign and doesn't work offline. On the App channel the screen belongs to your app, and the app can store an answer given without a connection and send it when the connection comes back (the integration guide shows how).
Step 1 — Create the survey on the App channel
In Surveys › New Survey, follow the wizard to the Channels step and select the App card. You can also select Website / Embed, so the same survey runs on the site and in the app. Email and WhatsApp don't share the survey: they send to lists, and the app doesn't.
The channel is not available for eNPS or Competition surveys, and it is included in every plan without using sending quota. There is no scheduling: the survey collects when people reach the right moment in the app. There is no test send either: every answer to an active survey counts in the results. To test the integration, use a separate survey, as explained in the guide Integrating the survey into your app.
Step 2 — Decide who sees it and how often
On the same step, the Display rules on the website and in the app apply to the app. The platform enforces them, not the app: changing a rule here changes the behavior the next time the app asks, without shipping a new version.
- Sampling rate — the percentage of people who will see the survey. The draw is fixed per person: whoever is left out stays out, no matter how often the app asks.
- Snooze days after dismissal — whoever closes the survey without answering won't see it again for that many days.
- Display frequency — don't show it to the same person again for N days. In the app it also decides when the person can answer again: with 90 days, the finance app hears from each person every quarter; without it, each person answers only once. Available from the Pro plan up and on the free trial.
- Post-response actions (CTAs) — a different button for promoters, passives and detractors, shown with the thank-you.
When the app sends the logged-in user, people are counted by user, not by device: someone who switches phones won't get the survey again ahead of time.
Step 3 — Hand the data to whoever builds the app
After saving, open the survey. The In-app survey card shows the Survey ID and the API address, with copy buttons. Those are the two values the app needs. The technical walkthrough, with examples in React Native, Swift, Kotlin and Flutter, is in the article Integrating the survey into your app.
The developer chooses the moment: in the finance app, right after "Close the month". Never when the app opens or in the middle of a task — at that point the person hasn't done anything worth rating, and the survey only gets in the way.
Don't ask for a store review after the score
The obvious idea is to send whoever scored 9 or 10 straight to rate the app on the App Store or Google Play. Don't. Asking for an opinion before requesting a review is the kind of filtering both stores prohibit, and the app can be rejected. If you want to ask for a review, do it at a different moment, unrelated to the survey. The promoter CTA can point to a referral program, for example.
Step 4 — Track the results
- On the In-app survey card: Shown, Dismissed, Answered and Response rate.
- On the Results by app version card: the NPS of each published version. If 1.5 dragged the score down, it shows up here before it reaches the store ratings.
- In Feedback: each response is tagged with the app version (for example, App 1.5.0).
- On the Channels page: the month's numbers across all surveys on the channel.
Answers given too fast for anyone to have read the question get a low quality score and are left out of the official NPS by default, as with the embed.
How the app connects to the rest
App responses feed the same reports (with the App channel filter), the AI analysis and the survey's alerts, such as NPS below the threshold and negative comment. A detractor who answered in the app opens a follow-up automatically, as on the other channels. AI analysis, alerts and follow-ups are not part of the Free plan: there, app responses go into reports and Feedback, and that's it.
Where to go next
- Integrations — the technical guide with the code for your app.
- Results and reports — how to read NPS by channel and period.
- Alerts — get notified when NPS drops or a negative comment comes in.
In short: create the survey on the App channel, set sampling and frequency, give the survey ID to whoever builds the app, let the app call the survey after a moment of value and track NPS by version.