--- title: "Fairing Integration for Rig: Query Fairing Data in Plain English" description: "Connect Fairing to Rig and query your Fairing data in plain English, or ask it in Claude, ChatGPT and Cursor. Governed, validated answers from your warehouse." canonical: "https://rig.so/integrations/fairing" format: markdown --- Browse integrations ![Fairing logo](https://img.logo.dev/fairing.co?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=112&format=png&retina=true) Analytics & product Supported # Fairing integration for Rig ## The easiest way to connect Fairing to Claude and other AI tools Fairing, formerly Enquire Labs, asks customers a short question after checkout, most often how they heard about you, to capture attribution that tracking pixels cannot see. [Try Rig](https://app.rig.so/signup)[Book a demo](https://rig.so/book-demo) ## What Rig syncs from Fairing Once connected, Rig models these objects so questions resolve to the right tables and joins: - Survey responses - Question catalog - Order ID - Customer ID - Email ## How Fairing connects to Rig Give Rig your Fairing secret token. Rig syncs every survey response along with the question catalog, and because each response carries the order ID, customer ID and email, the answers join directly to your orders and customers rather than sitting in a separate reporting silo. [Read the step-by-step Fairing setup guide](https://rig.so/guides/connect-fairing) ## Compare declared attribution against tracked attribution Post-purchase surveys capture what pixels cannot: word of mouth, podcasts, offline, and channels that block tracking. Rig puts self-reported attribution next to your platform-reported attribution in one warehouse, so the two can be compared per order instead of per dashboard. Ask Rig - Where do customers say they heard about us versus what the pixel claims? - What share of revenue comes from channels no platform takes credit for? - Which channels are over-claiming relative to what customers report? ## Value each acquisition source by what it actually returns Because responses join to orders, a declared source can be followed through to order value, repeat rate and lifetime value. That turns a survey result into a channel economics question rather than a share-of-mentions chart. Ask Rig - What is the average order value by how customers heard about us? - Which self-reported channels produce the best repeat purchase rate? - What is 12-month LTV by declared acquisition source? ## Watch how the answer mix moves The distribution of survey answers shifts as campaigns launch and awareness builds. With the history in your warehouse, you can see those shifts against the dates you actually changed something, rather than comparing two point-in-time screenshots. Ask Rig - How did the answer mix change after the podcast campaign started? - Are word-of-mouth mentions growing as a share of responses? - Which sources are declining month over month? ## Ask your Fairing data in Claude, ChatGPT or Cursor Rig serves your Fairing data to AI assistants over MCP. Once Fairing is synced into your warehouse, you can ask questions in plain English from the tool you already use, and every answer is backed by validated, governed SQL. - [Claude](https://rig.so/integrations/claude) - [Claude Code](https://rig.so/integrations/claude-code) - [Cursor](https://rig.so/integrations/cursor) - [ChatGPT](https://rig.so/integrations/chatgpt) - [Codex](https://rig.so/integrations/codex) - [Gemini](https://rig.so/integrations/gemini) ## Frequently asked questions What does Rig sync from Fairing? Survey responses and the question catalog. Each response carries the order ID, customer ID and email, which is what lets the answers join to orders and customers. Can I join survey answers to order value? Yes, and that is the point of syncing it. Once responses sit beside your Shopify or other order data, declared attribution can be measured in revenue rather than in response counts. What do I need to connect Fairing? The secret token from Settings then API credentials in Fairing, not the publishable key alongside it. How does this compare with pixel-based attribution? They answer different questions and disagree usefully. Pixels record what they can observe; surveys record what customers say. Holding both in one warehouse lets you quantify the gap rather than pick a side. ## Related integrations [![Google Analytics 4 logo](https://img.logo.dev/analytics.google.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=72&format=png&retina=true)Google Analytics 4Funnel, channel and conversion analytics from your GA4 events.](https://rig.so/integrations/google-analytics-4)[![Google Search Console logo](https://img.logo.dev/search.google.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=72&format=png&retina=true)Google Search ConsoleDaily organic search clicks, impressions, CTR and position by query and page.](https://rig.so/integrations/google-search-console)[![Google Tag Manager logo](https://img.logo.dev/tagmanager.google.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=72&format=png&retina=true)Google Tag ManagerYour whole tag, trigger and variable configuration as queryable tables.](https://rig.so/integrations/google-tag-manager)[![KnoCommerce logo](https://img.logo.dev/knocommerce.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=72&format=png&retina=true)KnoCommerceMulti-question post-purchase surveys joined to orders and customers.](https://rig.so/integrations/knocommerce)[![Langfuse logo](https://img.logo.dev/langfuse.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=72&format=png&retina=true)LangfuseToken cost, latency and quality analytics for your LLM features.](https://rig.so/integrations/langfuse)[![Microsoft Clarity logo](https://img.logo.dev/clarity.microsoft.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=72&format=png&retina=true)Microsoft ClarityDaily engagement, scroll depth and rage-click snapshots from Clarity.](https://rig.so/integrations/microsoft-clarity) ## Connect Fairing data to AI tools like Claude Rig builds a governed context layer over your data so every team, and every AI tool, asks questions and gets answers they can trust. [Try Rig](https://app.rig.so/signup)[Book a demo](https://rig.so/book-demo) --- - [This page as HTML](https://rig.so/integrations/fairing) - [Site map for language models](https://rig.so/llms.txt) - [API and agent documentation](https://rig.so/developers)