Overview
Turn your playtest build into a feedback channel
Section titled “Turn your playtest build into a feedback channel”The FirstLook SDK drops into your Unreal or Unity project and gives playtesters a way to respond through the game itself. Surveys fire on the gameplay events you choose, like end of match or a player’s third attempt at the same boss. Answers land in your FirstLook dashboard alongside the session and event data the SDK collects on its own.
What the SDK does for your playtest
Section titled “What the SDK does for your playtest”- In-game surveys triggered by gameplay events you define, so you ask the right question while the experience is fresh.
- Automatic session tracking: who played, how long, how often.
- Custom events for hero picks, match outcomes, loading times, and anything else worth measuring.
- Onboarding for players you’ve never met. New playtesters appear as Unlinked players on first boot; show them an in-game link or QR code to finish their profile.
Time to first in-game survey: under an afternoon
Section titled “Time to first in-game survey: under an afternoon”Install the plugin or package and set two URLs. From there the SDK authenticates and starts tracking sessions on its own. Studios typically fire their first in-game survey within an hour of download.
Pick the guide that matches your engine:
Unreal SDK Setup Drop in the FirstLook plugin, wire up Steam, and start collecting playtest feedback from your Unreal build.
Unity SDK Setup Install the FirstLook packages, authenticate with Steam or Google Play, and start collecting playtest feedback from your Unity build.
Engine support at a glance
Section titled “Engine support at a glance”| Capability | Unreal | Unity |
|---|---|---|
| Steam authentication | ✅ | ✅ |
| Google Play authentication | ✅ | |
| In-game surveys (native UI) | ✅ | ✅ |
| Browser-overlay surveys | ✅ | ✅ |
| Session tracking | ✅ | ✅ |
| Custom counter events | ✅ | ✅ |
| Custom duration events | ✅ | ✅ |
| Onboard Unlinked players | ✅ | ✅ |