Dashboard

What goes in a survey performance dashboard?

A survey performance dashboard measures the machinery of research itself: whether surveys reach people, whether people finish them, and where questionnaires leak respondents. It keeps response-rate denominators explicit — responses over sends, opens, and views are three different metrics.

For: Research, product ops, and anyone running recurring surveys. Refresh: daily while surveys are in field. Source: modeled feedback, survey, and product-usage tables in a Metabase-connected database.

Which cards belong on this dashboard?

  • Responses per survey per week
  • Response rate by survey with labeled denominator
  • Completion rate by survey
  • Drop-off by question position
  • Median time to complete
  • Response rate by channel and device
  • Open-text answer rate
  • Responses by audience segment

What data does this dashboard need?

  • Response-grain data with started and submitted timestamps
  • Invitation, open, or view counts per survey and channel
  • Answer-grain data with question position and type
  • Survey metadata: question count, channel, audience
  • Respondent segment fields (plan, region, tenure)

How do you build it?

  1. Sync the source tools into a database and retain raw IDs, timestamps, statuses, and segment fields.
  2. Build modeled tables at the grain this dashboard requires.
  3. Create one saved question per card and certify the shared models and definitions.
  4. Add dashboard filters for Date range, survey, channel, segment, device.
  5. Show refresh time, and exclude internal and test activity from every headline card.

Example card SQL

Completion rate by surveyPostgreSQL
SELECT
  s.name AS survey,
  COUNT(r.id) AS started,
  COUNT(r.id) FILTER (WHERE r.completed) AS completed,
  ROUND(
    100.0 * COUNT(r.id) FILTER (WHERE r.completed)
    / NULLIF(COUNT(r.id), 0), 1
  ) AS completion_rate
FROM surveys s
JOIN survey_responses r ON r.survey_id = s.id
WHERE r.started_at >= CURRENT_DATE - INTERVAL '90 days'
GROUP BY s.name
ORDER BY completion_rate ASC;

Dashboards

Integrations

Metrics

Analytics

FAQ

Response rate or completion rate — which matters more?
They diagnose different problems. Low response rate means the invitation, channel, or audience is wrong; low completion rate means the survey itself is too long or loses people at a specific question. The drop-off card tells you which question.
Can I compare response rates across survey tools?
Only after normalizing the denominator. One tool's rate-over-opens will always beat another's rate-over-sends. Land invitation and view counts in the warehouse and compute rates yourself with one definition.