Integration Specifications
This article will help you learn about how Daasity replicates data from Alchemer, limitations to the data we can extract and where the data is stored in the Alchemer schema.
Integration Overview
Alchemer, formerly named Survey Gizmo, is a survey software and customer feedback management platform that helps businesses understand and transform their engagement with markets, customers and employees.
This document provides context on what kind of data is being gathered through this extractor, which endpoints that data is coming from, and how the extracted tables relate to each other.
Integration Availability
This integration is available for:
Enterprise
API Endpoints
The Daasity Alchemer extractor is built based on this Alchemer API Documentation. The following endpoint is used by Daasity to replicate data from Alchemer:
Entity Relationship Diagram (ERD)
Click here to view the ERD for the Daasity Alchemer integration illustrating the different tables and keys to join across tables.
Alchemer Schema
The Daasity Alchemer extractor creates these tables using the endpoints and replication methods listed. The data is mapped from source API endpoint to the table based on the mapping logic outlined in each table.
Surveys
Endpoint: Survey
Update Method: UPSERT
Table Name: [
survey_gizmo.surveys]
survey::id
id
survey::title
title
survey::created_on
created_at
survey::modified_on
updated_at
Daasity: timestamp when loaded into DB
loaded_at
Questions
Endpoint: SurveyPage
Update Method: UPSERT
Table Name: [
survey_gizmo.questions]
MD5(survey::id + survey::question::id)
id
survey::id
survey_id
survey::question::id
origin_question_id
survey::question::title::English
title
survey::question::page_id
page_id
survey::question::position
position
Daasity: timestamp when loaded into DB
loaded_at
Question Options
Endpoint: SurveyPage
Update Method: UPSERT
Table Name: [
survey_gizmo.question_options]
MD5(survey::id + survey::question::options::id)
option+id
survey::question::options::id
origin_option_id
MD5(survey::id + survey::question::id)
question_id
survey::question::option::title::English
title
survey::question::option::properties::disabled
disabled
survey::question::option::properties::position
position
Daasity: timestamp when loaded into DB
loaded_at
Responses
Endpoint: SurveyResponse
Update Method: UPSERT
Table Name: [
survey_gizmo.responses]
MD5(response::id)
id
survey::id
survey_id
response::id
origin_response_id
response::status
status
response::date_started
started_at
response::date_submitted
completed_at
response::params::email
response::params::firstname
first_name
response::params::subscriptionid
subscription_id
response::params::orderid
order_id
response::params::customerid
customer_id
response::params::emailid
email_id
Daasity: timestamp when loaded into DB
loaded_at
Response Answers
Endpoint: SurveyResponse
Update Method: UPSERT
Table Name: [
survey_gizmo.response_answers]
MD5(response::id + response::question::id)
id
MD5(response::id)
response_id
MD5(survey::id + response::question::id)
question_id
response::answer
answer
survey::id + response::id + response::question::id + question + loaded_at
answer_options
response::question::shown
shown
Daasity: timestamp when loaded into DB
loaded_at
Response Answer Options
Endpoint: SurveyResponse
Update Method: UPSERT
Table Name: [
survey_gizmo.response_answer_options]
MD5(response::question_answer::id + response::question_answer::options::id)
id
MD5(survey::id + response::question_answer::options::id)
question_option_id
response::question_answer::id
response_answer_id
response::question_answer::options::option || response::question_answer::options::answer
answer
response::question_answer::options::rank
rank
Daasity: timestamp when loaded into DB
loaded_at
Was this helpful?