Your beta runs in Stomio, but that's rarely where the conversation about it ends. At some point you'll want to cross-reference results against your own data, send a spreadsheet to a colleague who doesn't have an account, or keep a copy of everything once the project closes.
Every table that matters has an export behind it. The only real trick is knowing which one gives you what, because two of them look almost the same and aren't.
In this article
- Export all responses
- Export exactly what you are looking at
- Export your tester list
- Export your applicants
- Which export do I want?
Export all responses
Export all, on the results page, gives you everything: all responses with timestamps, no matter what you've currently got filtered or expanded on screen.
Use this one for analysis. The timestamps are the interesting part, because they tell you when people answered as well as what they said, and that's how you spot the difference between a beta everyone worked through steadily and one where half your testers rushed it the night before the deadline.
The results page with the Export all action
Export exactly what you are looking at
The table view has its own export, called Export view, and it does what the name says: only the columns you can see and the rows left after filtering.
There are two ways to it. The Export view link sits above the table, or you can right-click anywhere on the table itself for a menu with the same export in it. The right-click menu also gives you an Excel version if you'd rather have a spreadsheet than a CSV.
This is your reporting export. Hide the columns nobody needs, filter down to the cohort you're talking about, then export exactly that and paste it straight into a deck without tidying it up first.
Worth remembering when a step seems to be missing from a file later: check whether you'd hidden that column. The export is doing precisely what it's meant to.
Export your tester list
The users page has Export .csv, which gives you the testers themselves rather than their answers. Each row is one tester: username, email, name, phone, address, which projects they're on, which ones they've been invited to but haven't joined, and their completion figure.
Then it widens to fit your workspace, adding a column for each tag category and each custom field you've set up. Whatever you collect about a tester comes out next to them, and there's nothing to configure per export.
This is the one you want when the question is about people rather than feedback. Reconciling your tester roster against a CRM, say, or checking whether the segments you actually recruited match the ones you meant to.
The users page with the Export .csv action
Export your applicants
If you screen testers through a public application form, the applicants pipeline has its own Export CSV covering applicants and everything they answered on your screening questions.
Don't overlook this one once the beta is done. A stack of screening answers from people who wanted into your beta is market research, and that includes the applicants you turned down. Collect and Screen Beta Applicants covers the screening side of it.
Which export do I want?
- Every answer, for analysis: Export all, on the results page.
- A clean table for a report or a deck: Export view, in the table view.
- Who your testers are: Export .csv, on the users page.
- Who applied and what they said: Export CSV, in the applicants pipeline.
It's the first two that get mixed up. Export all ignores your filters and Export view respects them, and either way you get a file that looks perfectly reasonable. You just find out in the meeting that it's missing the rows you needed, or full of rows you didn't want.