Strategy
Survey Segmentation: Targeting by Order Value, Product, and Customer Tag
7 min read
A first-time buyer who spent $38 on a single tee and a returning wholesale account that just placed a $4,200 order have almost nothing in common. Yet most stores show them the same survey. The same questions, the same answer options, the same "How did you hear about us?" Then they wonder why the data feels flat.
That is the core problem survey segmentation solves. When you ask everyone the same thing, you get answers that average out to nothing useful. When you ask the right question to the right buyer, you get specifics you can act on.
Why one-size surveys produce generic answers
A generic survey has to be written for the lowest common denominator. It can't assume anything about the order, so the questions stay vague enough to apply to everyone. Vague questions get vague answers.
Think about what you lose:
- A buyer who just spent $300 could tell you whether the price felt fair. A buyer who spent $25 can't answer that the same way, so you never ask.
- Someone who bought running shoes has a real opinion on sizing and fit. Someone who bought a gift card does not. A blended survey skips the sizing question entirely.
- A wholesale customer cares about lead times and reorder flow. A retail customer cares about delivery speed. One question can't serve both.
The fix is not writing one cleverer survey. It is writing several focused ones and showing each to the segment it was built for.
How OrderSurvey targeting rules work
OrderSurvey lets you attach targeting rules to each survey so it only shows when the order matches. These rules read attributes that are already on the order, so there is no extra setup on the customer's side and no broad data access scope requested from your store.
The rules you can target on:
| Rule | Example use |
|---|---|
| Order total | Ask about perceived value only on orders over $150 |
| Item quantity | Show a bulk-buyer survey when the cart has 5+ units |
| Products / variants | Trigger a fit-and-sizing survey on apparel SKUs |
| Customer tags | Send VIPs a different NPS follow-up than first-timers |
| Shipping country | Localize questions or skip regions you don't ship from |
| Currency | Separate domestic responses from international ones |
One thing to keep in mind for in-store feedback: POS surveys target by location only, not by order rules. Shopify's POS surface exposes the order id but not the full order detail at survey time, so product and order-total rules don't apply there. If you run retail, target POS surveys by store location and keep your order-rule segments on the thank-you and order status pages.
Example segments worth building
You don't need twenty surveys. Three or four well-chosen segments cover most of the value. Here are the ones that earn their keep.
New customer vs VIP
This is the highest-leverage split for most stores. A new buyer's most valuable answer is attribution: where they actually came from. A repeat buyer already knows you, so attribution is noise. What you want from them is loyalty signal and reasons to come back.
- New customers (no orders tag, or a "first-order" tag): lead with "How did you hear about us?" See the attribution playbook for answer options that map cleanly to channels.
- VIPs (a "VIP" or repeat-buyer tag): run NPS and a short "what almost stopped you from reordering?" follow-up. Skip attribution.
Tag-based targeting reads your existing customer tags, so if you already segment customers in Shopify or via your email tool, the groundwork is done.
Apparel vs everything else
If you sell a mix of categories, the questions that matter change by product. Apparel buyers can tell you about fit and sizing, which is the single biggest driver of returns in soft goods. Accessories or home goods buyers can't, so asking them about fit wastes a question.
Target a fit-focused survey to your apparel products and variants. Use the answers to spot SKUs that run small or large before the returns pile up. There is a full breakdown of this approach in reduce returns with surveys.
Wholesale and high-value orders
Use order total and item quantity to catch your wholesale and bulk orders. A $4,000 order with 60 units is a different relationship than a $40 retail order, and the buyer's concerns reflect that:
- Lead time and restock reliability
- Reorder and account-management friction
- Whether the order arrived complete and undamaged
You can stack rules here. Target order total over $1,000 and a "wholesale" customer tag to be precise about who sees the B2B survey.
Running multiple surveys at once without collisions
Segmentation only works if you can run several surveys at the same time and trust the right one fires. OrderSurvey supports multiple concurrent surveys with a priority order plus a default-survey fallback.
Here is the logic to plan around:
- Priority decides ties. When an order matches more than one survey's rules, the higher-priority survey wins. Order your surveys from most specific to least specific.
- Specific beats general. Put your wholesale and VIP surveys above your catch-all. A $2,000 wholesale order would match a generic "spent over $100" survey too, but you want it to see the B2B questions.
- The default is your safety net. Set a general survey as the fallback so any order that matches no segment still gets asked something. No buyer falls through.
A workable priority stack might look like this:
| Priority | Survey | Rules |
|---|---|---|
| 1 (highest) | Wholesale | Order total > $1,000, tag: wholesale |
| 2 | VIP loyalty | Tag: VIP |
| 3 | Apparel fit | Products in apparel collection |
| 4 | New customer attribution | Tag: first-order |
| 5 (default) | General NPS | No rules (fallback) |
You can also schedule surveys with optional start and end dates, which is handy for seasonal segments. Run a holiday-gifting survey only in Q4, then let it expire without touching the rest of your stack.
Measuring the lift from relevance
Segmentation is a means to an end. The end is better data and higher completion, so measure both.
Response and completion rate per survey. A well-targeted survey almost always completes at a higher rate than a generic one, because the questions feel relevant and there are fewer of them. Watch each segment's completion rate separately. If your apparel-fit survey completes at 40% while your general survey sits at 18%, that gap is the relevance payoff. There are typical numbers to compare against in the response rate benchmarks.
Answer specificity. This one is qualitative but obvious when you see it. Open-text answers from a targeted survey name actual products, sizes, and reasons. Answers from a generic survey say "good" and "fast shipping." Export everything to CSV and skim a sample from each segment.
Action rate. The real test is whether the data changes anything. Segmented NPS lets you route detractor alerts smartly: a VIP scoring a 4 deserves a faster response than an anonymous first-time buyer. OrderSurvey can fire a low-score alert to a Slack webhook when NPS lands at or below your threshold, so a VIP detractor can hit a different channel than the rest.
A simple before-and-after: run one generic survey for two weeks, then split it into two or three segments and run those for two weeks. Compare completion rate, the share of open-text answers that are specific, and how many responses you actually acted on. The segmented version usually wins on all three.
Start with one split
You don't have to build the whole stack on day one. Pick the split that matters most for your store, usually new vs returning, and run two surveys against it. Once you see the completion gap and the difference in answer quality, the next segment is easy to justify.
If you're still setting up your first survey, start with the complete guide to post-purchase surveys, which walks through surfaces, question types, and targeting from scratch. OrderSurvey's free plan covers up to 100 responses every 30 days, which is plenty to test a couple of segments before you commit.
Run your first post-purchase survey free
OrderSurvey adds NPS, attribution, and CSAT surveys to your Shopify thank-you page, order status page, and POS. No code, and no extra data scopes.
Install OrderSurvey