Integration Specifications
This page will help you learn about how Daasity replicates data from Fairing, limitations to the data we can extract and where the data is stored in the Fairing schema.
Integration Overview
The Daasity Fairing integration allows merchants to compare post-purchase survey responses with other order channel attribution models. This allows the customer to compare, e.g. GA last click channel with a customer’s survey response to form a more holistic view of which marketing channels drive a customer to make an order.
Integration Availability
This integration is available for:
Enterprise
Growth
S3 Feed
The Daasity Fairing integration is built based on this Fairing Data Sync Documentation. Daasity uses the S3 Server to obtain CSV files from Fairing and extracts the following information:
Survey questions, responses, and other survey-related information
Information about the survey respondent
Information about the purchase associated with the survey
Entity Relationship Diagram (ERD)
Click here to view the ERD for the Daasity Fairing integration illustrating the different tables and keys to join across tables.
Fairing Schema
The Daasity Fairing extractor creates these tables using files from S3 and replication methods listed. The data is mapped from source S3 File to the table based on the mapping logic outlined in each table.
Surveys
Endpoint: AWS S3
Update Method: UPSERT
Table Name: enquire_labs.surveys
event_at | event_at |
coupon_amount | coupon_amount |
coupon_code | coupon_code |
coupon_type | coupon_type |
customer_name | customer_name |
customer_order_count | customer_order_count |
landing_page_path | landing_page_path |
order_id | order_id |
order_number | order_number |
order_total | order_total |
other | other |
other_response | other_response |
question | question |
question_id | question_id |
question_type | question_type |
referring_question | referring_question |
referring_question_id | referring_question_id |
referring_question_response | referring_question_response |
referring_question_response_id | referring_question_response_id |
referring_site | referring_site |
response | response |
response_position | response_position |
utm_source | utm_source |
utm_campaign | utm_campaign |
utm_medium | utm_medium |
utm_term | utm_term |
utm_content | utm_content |
source | source |
Daasity: account_id | _account_id |
Daasity: sync_key | __sync_key |
Daasity: timestamp when loaded into DB | __synced_at |
Last updated