Survey Response
Segmentation
Link every survey response to a user. Segment feedback by plan, role, behavior, or any custom attribute - so you act on specifics, not averages.
The problem with anonymous feedback
Most survey tools collect responses without knowing who submitted them. You get an aggregate score and have no way to act on it. Mapster is different - every response can be linked to a specific user, so you can segment and filter feedback by the attributes that matter to your business.
Without segmentation
What most tools show you
"Looks fine. No action needed."
With segmentation
Same data, broken down by user segment
Happy - love the product
At risk - one bad month from churn
80% of all negative feedback
Three segments. Three different problems. Three different fixes.
How segmentation works
Mapster lets you pass user attributes alongside survey responses. These attributes are attached to every response, so you can filter and segment your feedback in real time. There are three ways to do this.
If you know the user - pass their attributes via URL parameters or widget (Methods 1 & 2). If you don't - ask them directly in the survey (Method 3).
Method 1: URL parameters
Append user attributes as query parameters to your survey link. When a user submits a response, Mapster captures these attributes and links them to that response.
https://mapster.io/s/your-survey-id?user_id=789&plan=pro&role=adminBest for: Email campaigns, in-app links, or any flow where you already know who the user is. Build the link server-side and each user gets a personalized survey URL.
Method 2: Widget attributes
If you embed Mapster surveys in your app using the widget, pass user attributes when you open the survey. The widget attaches them to every response automatically.
widget.open(widgetId, {
user_id: '789',
plan: 'pro',
role: 'admin',
lifetime_value: 480
})Best for: In-product feedback surveys where you want to capture rich context - plan tier, usage data, feature flags - without the user having to type anything.
Method 3: Ask in the survey
Add questions to your survey that collect segmentation data directly from the respondent. For example: "What is your role?" or "How long have you been using our product?"
Best for: Public surveys where you don't have existing user data, or when you want respondents to self-identify their segment.
What you can segment by
Any key-value pair you pass becomes a filterable attribute. Common examples:
| Attribute | Example value |
|---|---|
| user_id | usr_789 |
| plan | pro |
| role | admin |
| signup_date | 2024-03-08 |
| lifetime_value | 480 |
| feature_used | analytics |
| company_size | 50-200 |
| taken_from | pricing_page |
Why segmentation changes everything
Find hidden churn risk
Your overall NPS is 42 - looks healthy. But enterprise users (80% of revenue) score 12. Without segmentation, you'd miss that your most valuable segment is unhappy.
Stop building for the wrong users
Free tier users flood your feedback with feature requests. Segmentation shows that paying users want something completely different. Build for the segment that pays.
Measure product-market fit by segment
Overall PMF at 32% looks like failure. But segmented: small agencies at 67%, freelancers at 38%, enterprise at 18%. You have strong fit in one segment - double down there.
Follow up with the right users
A user left critical feedback about your onboarding. Because their response is linked to their user ID, your CS team can reach out directly and close the loop.
Track satisfaction over time by cohort
Compare feedback from users who signed up in January vs March. Did that product change actually improve things? Segmentation gives you the before-and-after by cohort.
Security & privacy
User attributes are powerful, so handle them responsibly:
- -
Use internal IDs, not emails or names. This keeps responses semi-anonymous while still letting you segment and follow up via your own database.
- -
Never pass sensitive data. Passwords, tokens, payment info, or SSNs should never appear in URL parameters or widget attributes.
- -
URL-encode values. Special characters in attribute values should be URL-encoded to prevent data loss.
- -
Limits enforced. Maximum 10 attributes per response, 100 characters per key, 200 characters per value. UTM and ad-tracking parameters are automatically filtered out.
Have questions? Contact us.