SurveyMonkey (Private App)
S
SurveyMonkey (Private App)

tap-surveymonkey-privateapp (meltanolabs variant)

SurveyMonkey is an online survey platform for creating and distributing surveys and collecting and analysing responses.

The tap-surveymonkey extractor connects to the SurveyMonkey API v3 to extract your surveys, their full definitions, distribution collectors, collector recipients, individual responses, and address-book contacts. Alongside the raw nested streams it also emits normalized streams that flatten the survey definition and responses into a relational, one-row-per-element shape (survey_pages, questions, question_headings, question_options, sub_questions, response_pages, response_answers) so downstream models do not need warehouse-specific UNNEST/FLATTEN SQL.

Prerequisites

You authenticate with a SurveyMonkey API access token that you generate from a private app in your own SurveyMonkey account. SurveyMonkey does not issue a separate API key — the API authenticates with an OAuth access token.

  1. Sign in at developer.surveymonkey.com with a SurveyMonkey account that can access the surveys you want to extract (an admin account is recommended — the token can only see surveys that user can see).
  2. Under My Apps, add a new Private app. A private app is tied to your own account and needs no SurveyMonkey approval.
  3. On the app's Settings page, grant the surveys_read, collectors_read, responses_read, responses_read_detail and contacts_read scopes.
  4. Copy the Access Token shown on the same page and paste it into the Access Token setting here.

Notes:

  • responses_read_detail (full per-question answer detail on the responses/response_answers streams) and API access in general require a paid SurveyMonkey plan; on Basic plans response answer detail is limited or unavailable.
  • Token lifetime depends on your SurveyMonkey plan. On Enterprise you can deploy the private app so the token does not expire; on lower paid plans the token expires roughly every 90 days, after which you regenerate it in the app and update the Access Token setting here.
  • Set Region to match your account's data-residency region (US / EU / CA); the wrong region causes authentication or lookup failures.

This token-based connector is an interim option. Once the Matatika SurveyMonkey OAuth app is approved, a Connect-based SurveyMonkey connector will be available that manages tokens for you.

Data recovery / backfill

The responses, response_pages and response_answers streams replicate incrementally on date_modified, bookmarked against start_date. To backfill or re-sync historical data, lower the start_date, or reset the connection state so the sync restarts from start_date. All other streams are full-table and always re-sync completely.

Note on history. These streams emit the current state of each record. They are not slowly-changing-dimension (SCD type-2) history tables — if you need valid-from/valid-to versioning (e.g. to match a Fivetran history-mode schema), layer that in the warehouse (for example with dbt snapshots).

Available Streams

surveys

All surveys in the account. Parent stream for the other streams.

FieldDescription
idUnique identifier of the survey
titleSurvey title
nicknameSurvey nickname
categorySurvey category
languageSurvey language
question_countNumber of questions in the survey
page_countNumber of pages in the survey
response_countNumber of collected responses
folder_idID of the folder containing the survey
date_createdTimestamp when the survey was created
date_modifiedTimestamp when the survey was last modified
hrefAPI resource URL

survey_details

The full definition of each survey, including pages and their questions. Synced per survey.

FieldDescription
idUnique identifier of the survey
titleSurvey title
question_countNumber of questions in the survey
page_countNumber of pages in the survey
response_countNumber of collected responses
date_createdTimestamp when the survey was created
date_modifiedTimestamp when the survey was last modified
pagesArray of page objects, each containing its questions

collectors

Collectors (distribution channels such as web links and email invitations) for each survey. Synced per survey.

FieldDescription
idUnique identifier of the collector
survey_idID of the parent survey
nameCollector name
hrefAPI resource URL

recipients

Recipients of each collector (the people an email-invite collector was sent to). Synced per collector; web-link collectors have no recipients.

FieldDescription
idUnique identifier of the recipient
collector_idID of the parent collector
survey_idID of the parent survey
emailRecipient email address
phone_numberRecipient phone number, if provided
survey_response_statusHow far the recipient got (not_responded, partially_responded, completely_responded)
mail_statusInvite delivery status (sent, not_sent, processing)
custom_fieldsCustom contact fields for the recipient
extra_fieldsExtra fields included in the invite message
remove_linkUnsubscribe link
survey_linkLink to the survey in the invite
hrefAPI resource URL

responses

Individual survey responses, including per-question answers. Synced per survey and incrementally replicated by date_modified.

FieldDescription
idUnique identifier of the response
survey_idID of the parent survey
collector_idID of the collector the response came through
recipient_idID of the recipient, if applicable
total_timeTotal time spent on the response, in seconds
ip_addressIP address of the respondent
response_statusStatus of the response (completed, partial, etc.)
custom_variablesCustom variables passed to the collector
date_createdTimestamp when the response was created
date_modifiedTimestamp when the response was last modified — replication key
pagesArray of answered pages and their question answers

survey_pages

One row per survey page, flattened from survey_details.

FieldDescription
idUnique identifier of the page
survey_idID of the parent survey
titlePage title
descriptionPage description
positionPosition of the page within the survey
question_countNumber of questions on the page
hrefAPI resource URL

questions

One row per question, flattened from survey_details.

FieldDescription
idUnique identifier of the question
survey_idID of the parent survey
page_idID of the parent page
positionPosition of the question within the page
visibleWhether the question is visible
familyQuestion family (e.g. single_choice, matrix, open_ended)
subtypeQuestion subtype
forced_rankingWhether forced ranking is enabled
hrefAPI resource URL

question_headings

One row per question heading (questions can carry multiple headings for A/B random assignment). Flattened from survey_details.

FieldDescription
question_idID of the parent question
survey_idID of the parent survey
page_idID of the parent page
heading_indexOrdinal position of the heading within the question
headingHeading text
descriptionHeading description

question_options

One row per answer choice, flattened from survey_details.

FieldDescription
idUnique identifier of the answer choice
question_idID of the parent question
survey_idID of the parent survey
page_idID of the parent page
positionPosition of the choice within the question
visibleWhether the choice is visible
textAnswer choice text
weightChoice weight, if scored

sub_questions

One row per matrix subquestion (row), flattened from survey_details.

FieldDescription
idUnique identifier of the subquestion (row)
question_idID of the parent question
survey_idID of the parent survey
page_idID of the parent page
positionPosition of the row within the question
visibleWhether the row is visible
textSubquestion (row) text

response_pages

One row per answered page of a response, flattened from responses. Incrementally replicated by date_modified.

FieldDescription
idID of the page
response_idID of the parent response
survey_idID of the parent survey
date_modifiedParent response modification timestamp — replication key

response_answers

One row per individual answer, flattened from responses down to the answer level. Incrementally replicated by date_modified.

FieldDescription
idDeterministic surrogate key for the answer
response_idID of the parent response
survey_idID of the parent survey
page_idID of the parent page
question_idID of the parent question
choice_idID of the selected answer choice, if applicable
row_idID of the matrix row, if applicable
col_idID of the matrix column, if applicable
other_idID of the "other" answer option, if applicable
textFree-text answer value, if applicable
date_modifiedParent response modification timestamp — replication key

contacts

Address-book contacts. Requires the contacts_read scope.

FieldDescription
idUnique identifier of the contact
first_nameContact first name
last_nameContact last name
emailContact email address
phone_numberContact phone number
statusContact status
hrefAPI resource URL

survey_categories

Survey categories available to the account.

FieldDescription
idUnique identifier of the category
nameCategory display name

Settings

Access Token

A SurveyMonkey API access token, used directly as a bearer token. Generate one from a private app in your own SurveyMonkey account (see Prerequisites). The token must have the surveys_read, collectors_read, responses_read, responses_read_detail and contacts_read scopes.

Start Date

The earliest response date to sync, in ISO-8601 format (e.g. 2026-01-01T00:00:00Z). Used as the incremental bookmark for the responses stream.

Region

The SurveyMonkey data-residency region your account belongs to, set when the account was created. Selecting the wrong region will cause authentication or lookup failures. If unsure, check with your SurveyMonkey account administrator.

Meltano Cloud Connector

SurveyMonkey (Private App) connector is available on Meltano. It is built, maintained, supported, and tested by Meltano.

Why Meltano Cloud?
Expert supportDirect access to the team that built and maintains Meltano Cloud. Same-day responses during UK business hours. When something breaks, we fix it fast because we know exactly how it works.
Rigorously testedEvery connector goes through comprehensive testing and quality checks before production. Daily monitoring catches issues before they hit your pipelines. We don't just wrap open-source taps and hope for the best. We validate, we test, we maintain.
No maintenance overheadAPI changes. Connector updates. Schema drift. Breaking changes from upstream sources. We handle it all. Your team focuses on using data. Our team focuses on making sure it's there when you need it.
Ingest & transform data with AIConnect Claude or any MCP-compatible assistant to Meltano Cloud. Add connectors, run pipelines, build dbt models and diagnose failed runs in plain English, against the same Git-backed project your team works in.
Access to Meltano Slack communityJoin 5,500+ data engineers and analytics practitioners. The community is active, helpful, and always on. Good for quick questions, sharing patterns, and learning what others are building.