Integration: Fairing (EnquireLabs)

This article 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

Key Topics

Click on the links below to take you to the section where you can learn more about this Integration

• Integration Overview
• Integration Availability
• S3 Feed
• Entity Relationship Diagram
• Fairing Schema
• Related Resources

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.

The key piece of data we pull out of the integration for the aforementioned order channel comparison is the response value for the question “How did you hear about us?” Fairing allows for free-text responses, so we use the following logic to derive the order channel from the response itself, which gets fed into the model in its raw form as as the order vendor. The logic we use to derive channel from the survey response is:

• If response contains the string “youtube,” channel is set to “Paid Search”
• If response contains the string “google,” channel is set to “Paid Search”
• If response contains the string “facebook,” channel is set to “Paid Social”
• If response contains the string “pinterest,” channel is set to “Paid Social”
• If response contains the string “instagram,” channel is set to “Paid Social”
• If response contains the string “snapchat,” channel is set to “Paid Social”
• If response contains the string “criteo,” channel is set to “Display”
• If response contains the string “pepperjam,” channel is set to “Affiliates”

Any response that doesn’t contain one of those strings is assigned a catch-all “Other” channel. That constructed “Enquire Channel” can then be compared with GA last click or other attribution models using this out-of-the-box Sankey visualization:

Integration Availability

This integration is available for:

• Growth
• Pro (V1 and V2)

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)

The embedded diagram houses the ERD for the Daasity Fairing integration illustrating the different tables and keys to join across tables. Hover over the embedded diagram to reveal controls to zoom and scroll.

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

Surveys

• Endpoint: AWS S3
• Update Method: UPSERT
• Table Name: enquire_labs.surveys

Related Resources