SurveyMonkey
SurveyMonkey is an online survey development tool to create and run surveys.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | SURVEY_HISTORY table using SurveyMonkey webhooks. | |
| History mode | SURVEY_HISTORY, SURVEY_PAGE_HISTORY, QUESTION_HISTORY, QUESTION_HEADING_HISTORY, SUB_QUESTION_HISTORY, QUESTION_OPTION_HISTORY, and RESPONSE_HISTORY tables. | |
| Custom data | ||
| Data blocking | ||
| Column hashing | ||
| Re-sync | ||
| Row filtering | ||
| API configurable | API configuration | |
| Priority-first sync | ||
| Fivetran data models | ||
| Private networking | ||
| Authorization via API |
Supported deployment models
We support the SaaS Deployment model for the connector.
Setup guide
Follow our step-by-step SurveyMonkey setup guide to connect SurveyMonkey with your destination using Fivetran connectors.
Schema information
This schema applies to all SurveyMonkey connections.
Syncing empty tables and columns
The SurveyMonkey connector doesn't support the creation of empty tables and columns in your destination.
We create a table in the destination only if we can retrieve the table data from the source. If SurveyMonkey doesn’t return data for the source table, we don’t create the table in your destination.
Limitations
The SurveyMonkey connector relies on the survey-level updated_at value returned by the SurveyMonkey API to determine which surveys to process during incremental syncs. This behavior is defined by the source side limitation, where the updated_at value is only updated when the survey itself is structurally modified (such as adding new responses, changes to questions or title), and not when existing responses are edited. On the Fivetran side, the sync operates in two stages: first, only surveys whose updated_at is greater than the survey cursor are selected for processing; second, responses are synced only for those selected surveys. Because of this limitation, while new responses are captured, updates to existing responses may not be synced if the survey’s updated_at does not change. These updates will only be captured after a subsequent survey modification or a full re-sync.