Read Quest Responses and Analytics

Both pages open from a quest’s row on the Quests page, or from the Responses and Analytics buttons in the quest editor. Anyone on the project can read them.

An archived quest keeps both pages. Open Archived at the bottom of the Quests page and use the links on its row. The pages say Archived at the top, and no new responses arrive.

Read responses

The banner reads Responses with a count. Each card is one visitor’s run through the quest, newest first.

1. Scan the cards

   A card shows Submitted or In progress, the visitor ID (or “anonymous”), how long ago it came in, and the page it was answered on.

2. Open one

   Click a card to see each question’s label and the answer given. Choices show their labels, not their saved values. A card with nothing filled in says “No answers recorded.”

3. Load older ones

   The page shows 50 at a time. Load more at the bottom adds the next 50.

The visitor ID is a random ID kept in that visitor’s browser, so two cards with the same ID came from the same browser. Question labels come from the quest’s current draft. An answer to a question you have since deleted shows its question ID instead.

A response launched from a thumbs button is linked to that feedback, but these pages do not show the link. The Platform API does, below.

Filter finished from in progress

The list opens on All. Click Submitted for visitors who reached the end and sent it, or In progress for those who started and stopped. The count in the banner follows the tab. A visitor who closes the quest halfway stays In progress for good, with the answers they gave. See what gets saved, and when.

Read the analytics

The Aggregate row counts every response under Started, the finished ones under Submitted, and their ratio as Completion.

Below it is one card per question, in the order of the current draft. Only submitted responses feed these cards.

Question type	Card shows
Choice	A bar per option, with its count and share
Range, Currency	Mean, Median, Min and Max, over a histogram of about ten bars
Date	A bar for each day that was picked
Text	The 20 most recent answers, newest first

Analytics covers every response the quest has had, across all its versions. There is no date or version filter.

Get the raw data out

The Platform API reads them. Make a key under project Settings → Platform API with the responses:read scope, then:

curl https://qaid.dev/api/v1/quests/YOUR_QUEST_ID/responses?completed=true \
  -H "Authorization: Bearer YOUR_PLATFORM_KEY"

Route	Returns
GET /api/v1/quests/{id}/responses	One page of responses, newest first. Each has completed, visitorId, pageUrl, feedbackId, questVersionNumber and answerCount. Filters: completed=true or false, since, until. Page with limit, and pass meta.pagination.nextCursor back as cursor
GET /api/v1/responses/{id}	One response with its answers
GET /api/v1/quests/{id}/analytics	The Analytics page’s figures, as JSON

Answers are not in the list; fetch each response for them. An archived quest’s responses and analytics are still served, with meta.questArchived (or data.questArchived on a single response) set to true. The quest list and GET /api/v1/quests/{id} leave archived quests out, so keep the quest’s id.