SurveyMonkey is an online survey tool that helps you create, send, and analyze surveys to gain insights on the business. It provides a user-friendly interface to easily create surveys, and distribute them through multiple channels such as weblink, email, and social media. SurveyMonkey, through its analytics capabilities, helps you segregate user data according to your requirements and gain insights into the user behavior and response to improve customer satisfaction, reduce churn, and increase brand loyalty.
Hevo uses the SurveyMonkey REST API v3 to ingest data from your SurveyMonkey account and load it to the desired Destination for scalable analysis.
Prerequisites
-
An active SurveyMonkey account from which data is to be ingested exists.
-
All scopes are granted in your SurveyMonkey app to allow Hevo to access and ingest data from it. Read Scopes to know about the various scopes available and how you can set them for your app.
-
You are assigned the Team Administrator, Team Collaborator, or Pipeline Administrator role in Hevo to create the Pipeline.
Configuring SurveyMonkey as a Source
Perform the following steps to configure SurveyMonkey as the Source in your Pipeline:
-
Click PIPELINES in the Navigation Bar.
-
Click + CREATE PIPELINE in the Pipelines List View.
-
On the Select Source Type page, select SurveyMonkey.
-
On the Configure your SurveyMonkey account page, do one of the following:
-
Select a previously configured account and click CONTINUE.
-
Click + ADD SURVEY MONKEY ACCOUNT and perform the following steps to configure an account:
-
Log in to your SurveyMonkey account.
-
Select the account from which you want to replicate data.
-
-
-
On the Configure your SurveyMonkey Source page, specify the following:
-
Pipeline Name: A unique name for the Pipeline, not exceeding 255 characters.
-
Historical Sync Duration: The duration for which you want to ingest the existing data from the Source. Default duration: 3 Months.
Note: If you select All Available Data, Hevo ingests all the data available in your Survey Monkey account since January 01, 2010.
-
-
Click TEST & CONTINUE.
-
Proceed to configuring the data ingestion and setting up the Destination.
Data Replication
| For Teams Created | Default Ingestion Frequency | Minimum Ingestion Frequency | Maximum Ingestion Frequency | Custom Frequency Range (in Hrs) |
|---|---|---|---|---|
| Before Release 2.21 | 1 Hr | 1 Hr | 6 Hrs | 1-6 |
| After Release 2.21 | 6 Hrs | 30 Mins | 24 Hrs | 1-24 |
Note: The custom frequency must be set in hours as an integer value. For example, 1, 2, or 3 but not 1.5 or 1.75.
-
Historical Data: The first run of the Pipeline ingests historical data for the selected objects on the basis of the historical sync duration specified at the time of creating the Pipeline and loads it to the Destination. Default duration: 3 Months.
-
Incremental Data: Once the historical load is complete, all new and updated records for the Collectors, Recipients, Responses, and Surveys objects are ingested as per the ingestion frequency. The remaining objects are ingested in Full Load mode.
Schema and Primary Keys
Hevo uses the following schema to upload the records in the Destination database:
Data Model
The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:
| Object | Mode | Description |
|---|---|---|
| Collectors | Incremental | Contains the details of methods that you can use to collect responses for your surveys. |
| Contacts | Full Load | Contains the details of users you want to send the surveys to. |
| Recipients | Incremental | Contains the details of contacts that have received the surveys. |
| Responses | Incremental | Contains the details of the responses received for the surveys. |
| Survey Folder | Full Load | Contains the list of folders that are used to organize surveys according to your requirements. |
| Surveys | Incremental | Contains the list of surveys sent out to the contacts. |
Source Considerations
None.
Limitations
- Hevo does not load an Event into the Destination table if its size exceeds 128 MB, which may lead to discrepancies between your Source and Destination data. To avoid such a scenario, ensure that each row in your Source objects contains less than 100 MB of data.
Revision History
Refer to the following table for the list of key updates made to this page:
| Date | Release | Description of Change |
|---|---|---|
| Jan-07-2025 | NA | Added a limitation about Event size. |
| Mar-05-2024 | 2.21 | Updated the ingestion frequency table in the Data Replication section. |
| Apr-04-2023 | NA | Updated section, Configuring SurveyMonkey as a Source to update the information about historical sync duration. |
| Nov-08-2022 | 2.01 | New document. |