Subscription Management
Paywall Surveys
Ask users why they declined or what made them buy — right at the paywall, from the dashboard, with no app release.
Every paywall close is a question you never get to ask. The user hit your pricing screen, decided not to buy, and left — and all you're left with is a number that ticked down. Was it the price? The plan mix? Did they just want to keep looking around? You can guess, or you can ask them in the moment they decide. Superwall surveys let you attach a short question to the exact instant a user declines or completes a purchase, collect the answers in your dashboard, and change the questions whenever you want — all without shipping a new app build.
See how surveys workCatch the why at the exact moment of decision
Surveys fire on the two moments that tell you the most about your funnel. A close survey appears when a user declines to transact or closes the paywall — the classic "wait, why did you leave?" — and a post-purchase survey appears right after a successful transaction, while the reason they bought is still fresh. You're not emailing a survey days later and hoping for a reply; you're asking at the point of highest intent, inside the experience they were already in.
Build the question, not a release
Each survey is composed in the dashboard from a few simple parts, so a growth or marketing person can author one without touching code:
Title and message. The contextual prompt at the top of the survey — set the framing in plain language.
Response options. Add or remove individual tappable choices ("Too expensive," "Not sure it's for me," "Just browsing"). To fight ordering bias, options are shuffled for each user, so no answer wins just because it sat at the top.
An "Other" path. Turn on a free-text option, always shown last, to capture the reasons your preset choices didn't anticipate.
An optional "Close" button. Let users dismiss without answering when you don't want to force a response.
You also control a presentation percentage from 0 to 100, so you decide what share of users see the survey at all — handy when you only need a representative sample rather than every single person. Each user sees a given survey only once per paywall, so you're gathering clean signal, not nagging the same person on every visit.
Read the answers, then act on them
Responses roll up into a stats view in the dashboard: you can see which options users picked and, when free text is enabled, read the individual "Other" responses verbatim. Because every survey is tied to a real paywall and a real outcome (declined vs. purchased), you're not collecting opinions in a vacuum — you're connecting the reason to the behavior that triggered it.
View the stats dashboardThe most useful part is what you do next. A common pattern is to react to a survey answer in real time: when a user says the price is the problem, you can route them to a discounted paywall instead of letting them walk. Survey responses can drive conditional paywall behavior through standard placements and event triggering, so "why did you leave?" becomes "here's an offer that fixes that" — without an engineer in the loop.
Why teams use it
Subscription teams hit a ceiling where the paywall converts about as well as it's going to, and the next gains come from understanding the users who didn't convert — and the abandoned-transaction revenue leaking out with them. Surveys turn that blind spot into a feed of reasons, in the users' own words, gathered at the decision point. Treat your paywall as a full-funnel surface: combine surveys with onboarding questions and multiple-choice elements to learn who your users are and what they want, then keep optimizing on what they tell you.
Get started
If the SDK is already in your app, surveys are a dashboard setting away. Read the surveys guide to add a close or post-purchase survey, then create a free Superwall account to start collecting answers from real users.
Read the surveys guide