# In-game feedback surveys: join survey answers to player data

> Send each in-game survey answer as an event with the player ID, then split answers by build, playtime and progress. Includes response rates from real playtests.

By Yos Riady. Updated 2026-11-18. Published 2026-11-18. Canonical URL: https://manalens.dev/blog/in-game-feedback-survey-player-data

Send each survey answer as an event with the same player ID as your gameplay events, so you can split answers by build, playtime and progress. Response rates vary: Brickadia got about 5.5% of its Next Fest demo players to answer (March 2025), and a Steam playtest of Effulgence RPG got 875 forms from 4,882 players.

## Key points

- Send each survey answer as an event with the survey ID, question ID and answer, and the SDK adds the player ID, session and build.
- Published in-game survey response rates range from about 5.5% for the Brickadia Next Fest demo to about 25% for a small web game.
- Keep an in-game survey short and optional, and aim for 5 to 10 minutes with short, concrete questions.

## Why join survey answers to play data?

Because an answer means more when you know what the player did. A low score from a player who quit in the tutorial is a different problem from a low score after ten hours. Without a player ID, you cannot tell them apart.

Andres Garcia Garcia, who ran an online survey for his incremental game, calls surveys a middle ground between playtesting and analytics. He advises you to look for meaning in the correlations between answers, not only in single answers. Play data adds more things to correlate.

The Desert Pirates team ran a Steam Playtest with a 10-question survey at the end of the demo. They wrote that they forgot to track how many players who asked for access actually played, and how far they got. Event data answers both.

Sources: Game Developer (Andres Garcia Garcia, 10 February 2017); Game Developer (Hernan Smicht, 3 November 2021).

## What response rate can I expect?

Anywhere from a few percent to about a quarter of players, depending on where you ask and who plays. The table lists rates that developers published. Each is a single game, not an average.

Our arithmetic: 875 forms from 4,882 unique players is about 17.9%, and 53 answers from 223 access requests is about 23.8%. The Effulgence RPG developer put a prompt for the form in several places in the game and made forms in 12 languages. The Desert Pirates team got only 3 questions on the Steam forum, against 53 in-game survey answers.

*Published survey response rates from individual games*

| Game and context | Answers | Base | Rate |
| --- | --- | --- | --- |
| Brickadia, Steam Next Fest demo, 2025 | Nearly 2,000 | Demo players | About 5.5% |
| Effulgence RPG, 5-day Steam Playtest, 2025 | 875 forms | 4,882 unique players | About 17.9% (our arithmetic) |
| Desert Pirates, Steam Playtest, 2021 | 53 answers | 223 access requests | About 23.8% (our arithmetic) |
| Incremental web game, Reddit post, 2017 | Not given | Visitors to the game | About 25% |

Sources: Brickadia (24 March 2025); Andrey Fomin (15 July 2025); Game Developer (Hernan Smicht, 3 November 2021); Game Developer (Andres Garcia Garcia, 10 February 2017).

## How do I send survey answers as events?

Send one event per answer with flat properties: the survey ID, the question ID, and the answer as a number or a short string. The SDK adds the anonymous player ID, the session, and the build and app version, so you do not need to send them. After identify(), it also adds your user ID.

Also send survey_shown when the survey opens. Then the response rate is survey_answer players divided by survey_shown players, and you can compare it by build.

Keep free text short. The server events API caps a string property at 1,024 characters, so long text is a poor fit for event properties in any case. If you collect long answers in another tool, store only a score and the question ID as an event.

``` GDScript
# Godot: one event per answer, with the same player ID as gameplay events
Manalens.track("survey_shown", {"survey_id": "demo_end_v2"})
Manalens.track("survey_answer", {
    "survey_id": "demo_end_v2",
    "question_id": "fun",
    "score": 4,
    "level": current_level,
})
Manalens.track("survey_answer", {
    "survey_id": "demo_end_v2",
    "question_id": "would_buy",
    "answer": "maybe",
})
```

Sources: Manalens Godot and Unity SDK documentation; Manalens server events documentation.

## What if my survey is a web form?

Host it on your own website and open it from the game with link_url(). The Godot and Unity SDKs add a short-lived ID to the URL, and the web SDK on your site joins that visit to the same player, without identify(). The link works for 10 minutes. Then send each answer from the page with a normal track call.

If a form tool on another domain collects the answers, send them from your backend as server events with the secret key, with a user_id that your game also sends through identify(). The secret key must stay on the backend and never ship in a build.

A form with no ID at all still has value, but you cannot join it to play data later.

Sources: Manalens Godot and Unity SDK documentation; Manalens server events documentation.

## How do I segment survey answers?

Use the answer as a filter, or use play data to split the answers. Any report can filter on an event property, such as question_id is would_buy and answer is no. On the Users page, a Behavior filter selects people who did an event a number of times, with one event property condition. You can export that list as CSV.

For questions that need a join, use SQL in the Explorer. The query below shows the average fun score by how long each player has played in total. Note that it counts all playtime up to now, not only the time before the answer.

``` SQL (Explorer)
-- Average "fun" score by total minutes played (session_end events)
SELECT
  multiIf(minutes < 30, 'a: under 30 min', minutes < 120, 'b: 30 to 120 min', 'c: 120 min or more') AS played,
  count() AS answers,
  round(avg(score), 2) AS avg_score
FROM (
  SELECT a.anonymous_id, a.score, p.minutes
  FROM (
    SELECT anonymous_id, JSONExtractFloat(properties, 'score') AS score
    FROM raw_events
    WHERE event = 'survey_answer'
      AND JSONExtractString(properties, 'question_id') = 'fun'
      AND toDate(original_timestamp) BETWEEN {{date_from}} AND {{date_to}}
  ) AS a
  LEFT JOIN (
    SELECT anonymous_id, sum(JSONExtractFloat(properties, 'duration_s')) / 60 AS minutes
    FROM raw_events
    WHERE event = 'session_end'
    GROUP BY anonymous_id
  ) AS p USING (anonymous_id)
)
GROUP BY played
ORDER BY played
```

Sources: Manalens filters and segments documentation; Manalens Explorer documentation.

## How do I ask without hurting the game?

Make it short, optional and easy to reach. Charles Cordingley built an in-game feedback screen modeled on the system that the Subnautica team presented at GDC. Andres Garcia Garcia's survey had about 40 questions and still got answers, but he advises a length of 5 to 10 minutes. About a third of his players filled in the free text box.

- Collect feedback inside the game, with a hot key that opens the form from anywhere.
- Ask for little. Cordingley used two text boxes and a submit button.
- Use emotion buttons as the submit buttons, as Subnautica did, so every answer has a mood.
- Attach context in the background, such as the level and recent events.
- Do not send anything that identifies the player.
- Ask short, concrete questions, and put one free text box at the end.
- Do not change a survey while it is live, and close it after a set time.

- [Playtest survey questions: what to ask your playtesters](https://manalens.dev/blog/playtest-survey-questions)
- [Playtest survey builder](https://manalens.dev/tools/playtest-survey-builder)
- [Best playtest and feedback tools for indie games](https://manalens.dev/blog/best-playtest-tools-indie-games)

Sources: Game Developer (Charles Cordingley, 26 March 2015); Game Developer (Andres Garcia Garcia, 10 February 2017).

## How do I keep survey data private?

Do not ask for names or emails in free text, and respect consent. With consent mode on, the Godot and Unity SDKs record no events and write no ID before the player agrees. A survey that a player fills in before consent is not sent.

If you need an email for a follow-up, ask for it in a separate, clear field, and send it as an identify() trait only with the player's consent. Our privacy guide covers consent and data rules for games in more detail.

- [Privacy friendly game analytics and GDPR](https://manalens.dev/blog/privacy-friendly-game-analytics-gdpr)

Sources: Manalens Godot and Unity SDK documentation; Manalens consent guide.

## Where do I see survey answers next to each player?

Manalens is the analytics and growth engine built for games. Each answer event shows in the player profile activity with the rest of their play, and event property filters split funnels, retention and other reports by answer.

- [User profiles](https://manalens.dev/features/user-profiles)

Sources: Manalens product documentation.

## Frequently asked questions

### Should I use Steam forums for playtest feedback?

Use them, but do not rely on them. The Desert Pirates team got only 3 questions on the Steam forum during its playtest, against 53 answers to its in-game survey. Players answer where they already are. Put the survey inside the game, and link to the forum for longer talks.

### How many questions should an in-game survey have?

Keep it short. Andres Garcia Garcia advises a survey that takes 5 to 10 minutes, ideally at the lower end, and short, concrete questions. Charles Cordingley used only two text boxes and a submit button. Ask one or two scored questions in the game, and keep a longer form optional.

### Can I join answers from Google Forms to players?

Only if the answer carries a player ID that your game also sends. The simplest way is a form on your own website, opened from the game with link_url(), which joins the visit to the same player. Otherwise, send answers from a backend as server events with a user_id.

### What response rate is good for an in-game survey?

Published single-game rates range from about 5.5% for the Brickadia Next Fest demo to about 25% for a small web game. A Steam Playtest of Effulgence RPG reached about 17.9% in our arithmetic. Measure your own rate with a survey_shown event, and compare builds rather than other games.

## Sources

- [Brickadia: Next Fest Wrap-Up: Survey Results, Plans for EA (24 March 2025)](https://brickadia.com/blog/next-fest-follow-up/)
- [Andrey Fomin: First Steam playtest of Effulgence RPG, results (LinkedIn post, 15 July 2025)](https://www.linkedin.com/posts/fomiand_just-finished-my-first-ever-steam-playtest-activity-7351037544173596673-eJHs)
- [Game Developer: Using the Steam Playtest feature (Hernan Smicht, 3 November 2021)](https://www.gamedeveloper.com/game-platforms/using-the-steam-playtest-feature-freaking-awesome-)
- [Game Developer: In-game Feedback Forms (Charles Cordingley, 26 March 2015)](https://www.gamedeveloper.com/programming/in-game-feedback-forms)
- [Game Developer: Online playtest surveys, are they any good? (Andres Garcia Garcia, 10 February 2017)](https://www.gamedeveloper.com/design/online-playtest-surveys-are-they-any-good-personal-experience-tips-and-conclusions)

## Steam data

- [RPG games on Steam: benchmarks](https://manalens.dev/steam/genres/rpg)

## Related guides

- [Game marketing measurement guide](https://manalens.dev/blog/game-marketing-measurement-guide)
- [Playtest analytics: what to measure](https://manalens.dev/blog/playtest-analytics)
- [Player segmentation for small studios](https://manalens.dev/blog/player-segmentation-small-studios)
- [Privacy friendly game analytics and GDPR](https://manalens.dev/blog/privacy-friendly-game-analytics-gdpr)
- [Game tracking plan generator](https://manalens.dev/tools/game-tracking-plan-generator)
- [A/B test significance calculator](https://manalens.dev/tools/ab-test-significance-calculator)
- [Player analytics guides](https://manalens.dev/blog/topic/player-analytics)
- [Playtest survey questions: what to ask your playtesters](https://manalens.dev/blog/playtest-survey-questions)
- [Detect game exploits and economy bugs with event data](https://manalens.dev/blog/detect-game-exploits-analytics)
- [How to move from Unity Analytics to Manalens](https://manalens.dev/blog/migrate-from-unity-analytics)
- [A/B testing in games: when is a result real?](https://manalens.dev/blog/ab-testing-games-statistical-significance)
