Skip to content
AppDues
Log in
Contact salesSign up

How to send an NPS email to app users

A practical workflow for turning an engaged subscriber segment into a short Net Promoter Score survey, without custom server code or a third-party data pipeline.

Why a list-based approach helps

Customer Lists make it possible to answer segment questions directly in the dashboard and to export the result for offline work or another system. Useful starting questions include how many lifetime customers began with a free trial, whether customers who share an email address spend more, how revenue splits by ad-tracking settings, and which active users have not yet started a trial. For feedback collection, the key shift is from pulling data through custom integrations to defining a segment, exporting it, and acting on it in an email tool.

Build the segment before you write the email

Open the Customers area of the dashboard. A first visit shows a default Active Subscribers list. For a custom segment, use the New option in the left sidebar and apply filters. The worked example narrows to people whose first purchase was in January and who were last seen in February, so respondents are recent and actively engaged. Add a filter requiring the email attribute to be present. Without an email address, email delivery is not possible; SMS, push notification, or in-app messaging are alternatives when email is not collected. Name and save the list, for example Jan 2021 NPS Survey, then open individual rows via app user ID when a detailed customer view is needed.

Export, import, and send

Use Export in the top right, confirm the request, and download the file from the link sent by email. The CSV contains more columns than the dashboard view. Upload that CSV to a new audience in the email tool, map columns so email addresses land in the correct field, create the message for that audience, and send. The example uses one email provider, but any tool that accepts a CSV audience follows the same pattern. Keep the survey brief and place it directly in the email to avoid sending respondents to a separate hosted page.

What to do next

After the first NPS round, reuse the same method for a different question. A natural follow-up segment is active users who have not started a trial yet; asking them what is holding them back can surface onboarding or paywall friction. Keep each list tied to one decision so responses stay interpretable.

NPS email checklist
StepWhat to checkWhy it matters
Define segmentFirst purchase window plus recent last-seen activityEnsures respondents are new and engaged
Require emailEmail attribute is not nullPrevents undeliverable rows in the export
Export listConfirm export and download CSV from emailed linkCSV carries more fields than the dashboard view
Import audienceUpload CSV and map the email columnEmail tool needs a clean audience
Send surveyShort survey inside the email, audience selectedReduces extra clicks and respondent friction

Workflow checklist derived from the captured tutorial; dashboard labels and export timing should be re-confirmed in the live product before publication.

Frequently asked questions

Who should receive an NPS email to app users?

Use filters for first purchase timing and recent activity, then require a non-null email attribute so the exported list can be emailed. If email is not collected, the same audience logic can be used for SMS, push, or in-app messaging.

What are the steps after exporting a customer list?

Export the list, download the CSV sent by email, upload it to the email tool, map the email column, build the survey inside the email, select the audience, and send.

Why put the survey inside the email itself?

Building the survey inside the email avoids an extra click to a separately hosted survey, which can reduce friction, and keeping the survey short is generally better.