Export survey responses to your warehouse

​

Who can use it

• Your workspace needs the Enterprise plan, and a BigQuery or Snowflake connection. Redshift, Postgres and S3 aren’t supported.
• Owners and admins can turn it on, change the destination and start an export. Turning export off is allowed on any plan. A workspace that leaves Enterprise stops exporting at the next hourly sync.

​

Set up the destination

CREATE SCHEMA <db>.GAINTRACE;
GRANT USAGE ON DATABASE <db> TO ROLE <role>;
GRANT USAGE, CREATE TABLE ON SCHEMA <db>.GAINTRACE TO ROLE <role>;

​

How the export behaves

• First export. The first run copies every response and campaign. Anyone querying the tables while it runs can see a partial table until it finishes.
• Every hour. After that, export runs with the connection’s sync, every hour. It needs automatic sync to be on for the connection and billing to not be locked. Choose Export now to run it right away. The tab shows the state (Copying existing responses, Exporting, Up to date or Export failed), the last export time and how many responses and campaigns were exported.
• No duplicates. Rows are upserted by id, so every response and campaign appears once. An edit, a change to a response’s follow-up, or a partial response that the customer later completes updates its row. A row never moves backwards to older data.
• Deletions. When a response or campaign is deleted in GainTrace, its row stays with deleted_at set, and every answer and personal column is cleared. Only id, workspace_id, survey_id, measure, updated_at and deleted_at are kept.
• Privacy. Responses to anonymous surveys never carry person_id, respondent_email or respondent_name, and neither do responses whose personal details were removed (anonymized_at is set). Private notes and GainTrace’s internal keys are never exported.
• What isn’t included. Answers imported from other tools or from NPS CSV and API history aren’t exported.
• Turn it off. The tables stay in your warehouse. Turning export on again, or changing the dataset or schema, empties the tables and reloads every response. Changing the destination or turning export off while a run is in progress stops that run.
• Catching up. If an export falls about a month behind, the next run reloads everything instead of patching the gap.

​

Tables

​

survey_responses

​

surveys

​

Example: monthly NPS

SELECT
  DATE_TRUNC(r.submitted_at, MONTH) AS month,
  s.name AS survey,
  COUNT(*) AS responses,
  100 * (COUNTIF(r.score >= 9) - COUNTIF(r.score <= 6)) / COUNT(*) AS nps
FROM gaintrace.survey_responses AS r
JOIN gaintrace.surveys AS s ON s.id = r.survey_id
WHERE r.deleted_at IS NULL
  AND r.measure = 'nps'
  AND NOT r.is_partial
  AND r.score IS NOT NULL
GROUP BY month, survey
ORDER BY month;

​

Troubleshooting