---
title: "Connect Fairing to Rig | Rig guide"
description: "Copy your Fairing secret token and sync post-purchase survey responses with the order ID, customer ID and email attached, ready to join to your orders."
canonical: "https://rig.so/guides/connect-fairing"
format: markdown
---

Search guides, references, playbooks…⌘K

Browse guides

# Connect Fairing to Rig

Fairing, formerly Enquire Labs, asks customers how they heard about you after checkout. Syncing it puts those self-reported answers next to the orders that generated them, so declared attribution can be measured in revenue rather than in response counts.

Requirements

Access to `Settings` → `API credentials` in Fairing

Time required

3 mins

## Get your secret token

1. Log into Fairing.
2. Go to `Settings` → `API credentials`.
3. Copy the **secret token**.

The secret token, not the publishable key
Fairing shows you both on that page. The publishable key is the one meant to be exposed in a browser, so it cannot authenticate a data sync and Rig has no use for it. The secret token is the one you want.

## Connect it in Rig

New to Rig? Watch how to find Connections

1. In Rig, open `Connections` and go to `Sources & actions`.
2. Search for **Fairing** and open the card.
3. **Secret token**: paste the value you copied.
4. Click `Test`, then `Sync`.

## What Rig pulls in

- **Survey responses**, each carrying the order ID, customer ID and email
- **The question catalog**, so you can tell which question a given answer belongs to and track the catalog changing over time

The identifiers on each response are the whole point. They are what turn a survey result into a channel economics question: average order value by declared source, repeat rate by declared source, twelve-month value by declared source.

## Troubleshooting

- **Authentication fails**: you have the publishable key. Go back to `Settings` → `API credentials` and take the secret token instead.
- **Responses sync but will not join to orders**: your order data needs to be in the same warehouse. Check the order ID on a response actually matches the order identifier your store writes, rather than assuming the join is broken.
- **Fewer responses than expected**: expected, and not a sync fault. Fairing only records answers from customers who responded, so the table is a sample of orders by design.

Was this guide helpful?

Yes No

---

- [This page as HTML](https://rig.so/guides/connect-fairing)
- [Site map for language models](https://rig.so/llms.txt)
- [API and agent documentation](https://rig.so/developers)