Post purchase survey questions

Most post-purchase surveys open with some version of "how satisfied are you?" It's a reasonable instinct and a weak question. Satisfaction scores tell you how the experience compared to what the shopper expected, which is not the same as telling you whether they'll buy again. Two customers can have identical experiences and give you opposite scores.

The questions worth asking are the ones tied to a decision you're about to make: what to fix in checkout, which channel to fund, which product to reorder. Below are 38 of them, grouped by that decision rather than by topic, with the response type for each.

Pick four to six. A post-purchase survey that runs longer than that trades response rate for detail you won't use.

Use these to sharpen positioning and product page copy.

Attribution reporting shows the last click. These reach the shopper's memory, which is where brand and word of mouth actually live.

Expectation gaps drive returns, and returns are more expensive than the survey that predicts them.

Keep these last and keep them optional. They're the most likely to trigger a drop-off.

The pattern to notice: no category is worth asking about unless someone owns the resulting action. If nobody will change checkout, the checkout questions are wasted fields.

Open a survey with a single-click question and hold open text until the shopper is invested. Demographics go last because they feel like a cost with no benefit to the respondent.

Jumping between checkout, product, and attribution questions forces the respondent to keep switching mental context, and the switching is what makes a short survey feel long.

Shorter surveys are easier to complete and produce cleaner data, which is why our poll question guidance recommends a maximum of one to five questions for quick-decision formats. A post-purchase survey on a confirmation page sits in the same territory, so four to six questions is a sensible working recommendation. An email sent after delivery can carry a few more, because the reader has more patience and a clearer reason to respond.

Checkout and attribution questions belong immediately after purchase, on the confirmation page, while the experience is fresh. Product and expectation questions need the product in hand, so they belong in an email a few days after delivery. Asking about product quality on the thank-you page gets you a guess.

If you use Likert scales, keep the same point system across every question, so a 1 always means the same thing from the first question to the last. Mixing a 1 to 5 scale with a 0 to 10 scale in the same survey makes results harder to compare and harder for respondents to answer consistently. Label the endpoints in words rather than leaving bare numbers.

"Was checkout fast and easy?" produces an unusable answer when it was fast but confusing.

For deeper guidance on constructing the questions themselves, see survey best practices and the guidance on follow-up questions for probing an initial answer. If you want broader satisfaction wording beyond the purchase moment, the customer satisfaction survey questions library covers it. If you plan to ask on the confirmation page rather than by email, the website feedback use case covers triggering a survey on visitor behavior. Once responses are in, analyze features let you filter and cross-tab by segment, which is where the useful differences show up.

Choose the six questions that map to a decision someone on your team is actually about to make, then build from a starting point that already has the structure in place.

Ryanair takes this approach to customer listening. Market research manager Rawaa Shami described SurveyMonkey as a platform that lets the airline engage customers to understand where it can improve and hear firsthand about the customer experience. The Ryanair customer story has the detail.

The post purchase survey template gives you an expert-built version you can edit in a few clicks. To ask on the confirmation page at the moment of purchase rather than by email, GetFeedback by SurveyMonkey triggers a form on visitor behavior.