rauxdata Documentation

Everything you need to collect post-purchase insights and understand where your customers really come from.

What is rauxdata?

rauxdata is a post-purchase survey and attribution platform built for DTC (Direct-to-Consumer) ecommerce brands. After a customer completes a purchase, a lightweight survey appears — asking things like "How did you hear about us?" Their answers are matched with UTM data and analytics to reveal your true acquisition channels.

Unlike ad platform dashboards that show you what they want you to believe, rauxdata gives you first-party, zero-party data straight from your customers. No cookies, no fingerprinting — just honest answers.

Who is it for?

Getting Started

From zero to your first response in under 5 minutes.

Survey Builder

Design multi-question surveys with logic branching, routing, and 20+ ready-to-use templates.

Question Types

Templates

Templates give you a pre-built survey in seconds. Click Use template in the Survey tab to open the template picker. You can customize any template after applying it.

Routing & Logic

Routing lets you send customers to different follow-up questions based on their answer. For example: customers who answered "Instagram" can be asked "Was it a Reel, a Story, or an ad?" while customers who answered "Podcast" are asked "Which podcast?".

1. In the Survey tab, open a question card and click Routing.
2. For each option, select the target question from the dropdown (or "End survey").
3. Save all changes.

Follow-up Questions

Follow-up questions are inline expansions triggered by a specific answer. They appear immediately after the answer without navigating to a new question screen — ideal for Yes/No flows.

Example: "Did you hesitate before buying?" → Yes → shows a text box "What almost stopped you?"

Survey Language

Each project can be set to English or Spanish. The widget UI (buttons, placeholders, and labels) will automatically display in the chosen language. Configure this in the Trigger tab → Widget Language.

Slider & Ranking Question Types

Collect numeric ratings and ranked preferences with two new question formats.

Slider

A Slider question presents a horizontal range input. Respondents drag a handle to pick a numeric value between a minimum and maximum you define. The answer is stored as a plain number and visualised as a 10-bucket histogram in Analytics.

Slider configuration fields

Ranking

A Ranking question lets respondents drag options into their preferred order. Answers are stored as a JSON array of option labels in ranked order.

• Ranking questions do not support the "Allow Other" or "Randomize order" toggles — these are intentionally hidden.
• Routing (conditional branching) is not available on Ranking questions.
• In Analytics, ranking answers are aggregated by option position frequency — the most-first-ranked option is highlighted.

Draft & Publish Mode

Edit your survey safely without affecting live customers — publish only when you're ready.

How it works

1. Every save in the Survey Editor writes to a private draft — live customers always see the last published version.
2. An "Unpublished changes" badge appears in the toolbar whenever your draft differs from the published version.
3. Click Publish to push your draft live. The widget cache updates automatically within seconds.
4. Click Discard to throw away the draft and revert to the currently published survey.

Why this matters

Widget Installation

Install the rauxdata widget on your store in minutes. We support Shopify, WooCommerce, Hotmart, and any website.

On any platform (script tag)

Works on any platform: Shopify (manual), WooCommerce, Hotmart, Webflow, or custom HTML.

1. Open your project and go to the Install tab.
2. Select your platform from the dropdown (Shopify, WooCommerce, Hotmart, or General).
3. Click the copy icon next to the script tag.
4. Paste it into your site's HTML before the closing </head> tag.

On Shopify (no-code)

Connect your store with OAuth — no code and no theme files to edit. rauxdata installs as a Shopify app and captures order revenue automatically. You then choose where the survey appears: on your storefront with your own design (recommended), or natively on the checkout thank-you page (advanced). By default, with no extra setup, the survey shows on your storefront as an overlay, in always-on mode, on the home page — and channel attribution is captured either way. You can change the surface, mode, and path anytime from the Trigger tab.

1. Open your project → Install tab → Connect with Shopify.
2. Enter your store domain (e.g. mystore.myshopify.com) and click Connect.
3. Approve the permissions on Shopify. rauxdata requests read_orders and read_customers — these power automatic revenue capture and customer-level deduplication.
4. Back in rauxdata the status shows "Pending embed". In Shopify → Online Store → Themes → Customize → App embeds, turn on rauxdata.
5. The status turns green when the widget loads on your store.

Advanced: survey on the checkout thank-you page

For a survey inside the checkout — native look, with each answer linked to its exact order. From your Shopify admin: Home → Manage themes → Edit theme to open the theme editor. Then open the page selector → Checkout and customer accounts, click the Apps icon (top-left), add the Rauxdata Checkout Survey block to the Thank you page, and Save.

Verifying the Installation

1. After installing, open your store in a browser.
2. Append ?raux_debug=true to the URL to force the widget to appear.
3. Back in the rauxdata dashboard, the connection status in the Install tab should update to Active (green dot) within a few seconds.

Tracking Purchases

To associate survey responses with specific orders, call the tracking API after a successful purchase:

<script>
  window.RAUX.track('purchase', {
    orderValue: 129.99,  // numeric order total
    currency: 'USD'      // ISO 4217 currency code
  });
</script>

Place this script on your order confirmation page, after the rauxdata widget script.

Design & Branding

Make the widget look like your brand. Fully customizable — no coding required.

Workspace Branding

Two workspace-level settings drive the branded emails sent from this workspace:

Configure workspace branding in Branding (sidebar icon). These values drive your branded emails; per-project widget appearance lives in the Design tab of each project.

Per-Project Widget Customization

Each project can override workspace branding with project-specific widget visuals in the Design tab:

Live Preview

The Design tab includes a real-time preview of your widget. Switch between Desktop and Mobile views. Click Test Trigger to see the widget as a full-screen overlay — exactly as your customers will see it.

Custom CSS

Inject your own CSS into the survey widget — full visual control, fully isolated.

What is Custom CSS?

Custom CSS lets you override any visual aspect of the survey widget beyond the standard color, font, and border-radius controls. Your CSS is injected into the widget's Shadow DOM — completely isolated from your store's stylesheet — so there is no risk of leaking styles into your page or vice versa.

How to use it

1. Open your project → Design & Branding tab.
2. Scroll to the Custom CSS section at the bottom.
3. Type or paste your CSS into the textarea (max 10,000 characters).
4. Click Save Visuals. The widget cache refreshes automatically.
5. Use ?raux_debug=true on your store to preview the changes instantly.

Available CSS classes

Examples

Trigger Settings

Control exactly when and where the survey appears. Everything is in the Trigger tab of your project.

Audience Targeting

Control exactly who sees your survey — not just where, but who.

What is Audience Targeting?

The Audience tab in each project lets you define rules that gate survey display. Without rules, the survey shows to every visitor who meets the trigger path conditions. With rules, only visitors who match your criteria see it — by customer type, order count, total spend, or Shopify tags.

Option A — Supply attributes via RAUX.track()

• Pass orderCount, totalSpent, and tags in your RAUX.track() call on the purchase page.
• These values are stored client-side and evaluated when the survey is about to appear on the thank-you page.
• Works on any platform — no Shopify required.
• Example: RAUX.track({ orderId: '...', orderCount: 3, totalSpent: 450, tags: ['vip'] })

Option B — Shopify automatic enrichment

• If your project has a Shopify integration, rauxdata fetches orderCount, totalSpent, and tags automatically using the orderId from RAUX.track().
• No extra code needed in your theme — the enrichment happens server-side before the widget evaluates the rules.
• Requires the Shopify integration to be active in your project.

Building rules

1. Go to your project → Audience tab.
2. Click Add rule and select an attribute (Customer type, Order count, Total spent, or Tags).
3. Choose an operator (equals, greater than, contains, etc.) and set a value.
4. Add multiple rules and choose Match ALL or Match ANY.
5. Click Save. The widget config updates immediately.
6. Remove all rules to go back to showing the survey to everyone.

Analytics & Attribution

Your dashboard shows the big picture: where customers say they came from, how it matches your UTM data, and every individual response.

Selecting a Project and Date Range

On the main Overview page, use the View results for dropdown to select a project. Use the date range picker (top right) to filter by time period.

Question Selector

When a project has multiple survey questions, the "View results for" dropdown lets you choose which question's data to visualize in the attribution chart. For example, you can switch between "How did you hear about us?" and "What motivated your purchase?" to see attribution by different dimensions. Selecting a question also reveals a Channel Distribution bar chart below the main attribution chart — showing, for that specific question, how many responses came from each acquisition channel.

KPI Cards

Attribution Chart

The main chart compares two values per channel: what customers said (zero-party data) in darker bars vs. what the UTM data shows (technical attribution) in lighter bars. When these bars diverge for a channel, last-click attribution is underreporting or overreporting that channel.

The pie chart on the left shows the distribution of self-reported answers — at a glance, which channels your customers say drove them to purchase.

PDF Report Export

Click Export PDF Report (top right of the analytics page) to download a formatted PDF report of the current view — charts, KPIs, and date range included. When a currency is active in the dashboard, the PDF dialog shows which currency the revenue figures are reported in, and the exported report reflects that currency. Useful for sharing attribution insights with clients or stakeholders who don't have dashboard access.

Audience Filter

Use the Audience toggle on the Overview page to segment all charts by customer type:

Responses Table

The responses table shows your most recent survey completions with:

• Customer answer(s) to each question
• UTM source and medium captured at the time of the visit
• Revenue (if purchase tracking is active)
• Status badge: Mismatch (user reported a different source than UTM) or No UTM (visit had no UTM parameters)
• Timestamp

Each row can be deleted individually to remove test or invalid responses.

NPS by Channel

Find out which marketing channels bring your most loyal customers — not just the most customers.

What is NPS?

Net Promoter Score (NPS) measures customer loyalty on a 0–10 scale:

Your NPS is % Promoters − % Detractors, ranging from −100 to +100. A score above 0 is good; above 50 is excellent.

How to Read NPS by Channel

The NPS by Channel chart shows your NPS score broken down by acquisition channel. Toggle between UTM Source (e.g. instagram, google) and UTM Medium (e.g. paid, organic, email).

This answers the question: "Which channel is bringing us customers who actually love us?" A channel might drive volume but bring low-NPS customers who churn. Another might have fewer conversions but send loyal buyers who recommend you.

Detractor Alerts

rauxdata automatically sends you an email alert whenever a customer submits an NPS score of 0–6 (Detractor). The alert includes:

• The exact score
• The acquisition channel (UTM source) if available
• Whether the customer is new or returning
• A direct link to your dashboard to review the response

Alerts are sent automatically to the workspace owner's email. No configuration needed — they activate as soon as your first NPS question is live.

Score Distribution Chart

The Distribution tab in the NPS panel shows a horizontal bar chart with one bar per score (0–10). Each bar represents the count of respondents who gave that exact score, colored by bucket: red for Detractors (0–6), yellow for Passives (7–8), and green for Promoters (9–10). Use it to see whether your Detractors cluster at 5–6 (nearly Passive) or at 0–2 (extremely unhappy) — a key insight for prioritizing follow-up actions.

Order Attribution

The Order Attribution tab connects your survey responses directly to purchase data — letting you see which answer options drive the most orders and revenue. It is the most direct way to measure the ROI of each acquisition channel using your customers' own words.

Access it from the Analytics dashboard: select a project and scroll to the Order Attribution section.

Filters

• Audience — Segment by All customers, New customers (first-time buyers), or Returning customers. Default: All.
• Question — Select which survey question to break down by. Only questions with at least one attributed response are shown. On first load, all questions are available; after the initial data load the list narrows to questions with actual attribution data.
• Date range — Filters by purchase date (orderPlacedAt), not by survey submission date. Leave empty to include all dates.
• Currency — Select the currency to scope the report to. Auto-selected when only one currency exists in the dataset — zero extra steps for single-currency stores. Multiple currencies appear as separate options.

KPI Cards

• Total Orders — Count of distinct orders in the selected currency scope.
• Total Revenue — Sum of revenue across all attributed orders in the selected currency.
• Orders with Response — Count of orders linked to a survey response that includes an answer for the selected question.
• Attribution Rate — Orders with Response ÷ Total Orders. Tells you what percentage of your total orders have a matching survey response.

Estimate 100% Toggle

When your attribution rate is below 100%, the Estimate 100% toggle extrapolates your partial data to a projected full picture. It scales order counts and revenue by the inverse of the attribution rate (1 ÷ attributionRate). The toggle is OFF by default and all estimated values are clearly labeled "Estimated". It is disabled automatically when there are no attributed orders to base the estimate on.

View in Base Currency Toggle (v1.1)

When a base currency is configured in your project settings, the "View in [currency]" toggle appears whenever the selected report currency differs from your base currency. Activating it converts all revenue values using ECB exchange rates (updated daily from frankfurter.app). The rate source label is shown below the table: "ECB rates · updated [date]" for live rates, "Converted using custom rates" when you have overridden rates in settings, or "(stale)" appended when the last fetch failed. You can set custom exchange rates in Settings → Currency to override the ECB defaults.

Survey vs. UTM Comparison

Below the breakdown table, Rauxdata renders a side-by-side comparison chart showing what your customers said (darker bars, survey data) versus what UTM last-click tracking recorded (lighter bars, technical attribution) — per acquisition channel. When the two bars for a channel diverge, it means your UTM tracking is underreporting or overreporting that channel.

Mismatch Rate

The mismatch rate (shown as a percentage above the chart) is the share of attributed orders where the channel reported by the customer in the survey differs from the channel recorded in the UTM source. A high mismatch rate — typically 20–40% for paid social — reveals gaps in your click-based attribution and shows how much dark traffic your UTMs miss. Channels like influencer content, podcasts, word-of-mouth, and untagged organic posts tend to show the largest divergence.

Metrics Reference

Data Quality Indicators

Three counters appear below the breakdown table to help you spot data gaps. They reset with each filter change.

• Orphan Responses

  Survey responses whose order ID has no matching purchase row. Attribution counts them but no order revenue is linked.

  Example: A customer completed the survey but the RAUX.track("purchase") call never fired on the confirmation page (e.g., checkout on a sub-domain without the widget).

• Uncovered Orders

  Tracked orders with no matching survey response for the selected question. These orders are in your revenue total but not attributed.

  Example: Customer skipped the survey, closed the tab before it appeared, or the survey question was not active when the order was placed.

• Duplicate Responses

  Order IDs with more than one attributed response for the same question. Only the first response is used for attribution; excess responses inflate Response Density.

  Example: A customer placed an order, submitted the survey, then re-submitted it (e.g., by refreshing the confirmation page). Both responses share the same order ID.

Access & Permissions

Order Attribution data is read-only. All workspace members can view attribution reports regardless of role.

Glossary

• Attribution — The process of linking a survey response to a specific purchase order, enabling you to measure revenue impact per answer option.
• UTM / Last-Click — A technical tracking method that records the last marketing link a customer clicked before buying. Misses dark channels like podcasts, word-of-mouth, and direct searches.
• Zero-Party Data — Data customers intentionally share with you — in this case, answering "How did you hear about us?" directly. More accurate than inferred data because it comes straight from the source.
• Mismatch — When the channel reported by the customer in the survey differs from the UTM last-click channel. A high mismatch rate reveals gaps in click-based attribution.
• Orphan Response — A survey response whose order ID has no matching purchase row. The response is attributed but the corresponding order was not tracked via RAUX.track("purchase").

Live Feed

Watch survey responses arrive in real time — no page refresh needed.

What is the Live Feed?

The Live Feed is a real-time panel on the Analytics page that streams incoming survey responses as they happen. Each card shows the project name, channel attribution, first answer, and a relative timestamp. The feed is scoped to your workspace — you only see responses from projects you own.

How it works

1. Open the Analytics page for your workspace. The Live Feed panel appears in the lower section.
2. The connection status dot turns green ("Live") once the SSE stream is established.
3. Each new response card slides in at the top. The panel keeps the last 20 responses.
4. If the connection drops (e.g. network interruption), the dot turns yellow ("Reconnecting...") and the browser reconnects automatically.

Signals

rauxdata automatically analyzes your response data and surfaces patterns you might have missed.

What Signals Does

Once you have collected responses, the Signals engine reads your open-text answers and structured responses to identify recurring themes, anomalies, and actionable opportunities. Examples of insights it might surface:

• "37% of customers from Instagram Stories mention influencer recommendations. Consider a dedicated landing page."
• "Detractors disproportionately mention shipping time. This is your top churn risk."
• "Podcast-acquired customers have the highest NPS — invest more in podcast sponsorships."

How It Works

Insights are generated automatically as your response count grows. They appear in the Signals card on your Overview dashboard. No configuration required.

Insights refresh periodically as new responses come in. Each insight includes a short analysis and a recommended action.

Email Survey

Send your survey as a standalone link via email, SMS, or any marketing channel — no widget required.

What is the Email Survey link?

The Email Survey feature generates a unique public URL (e.g. https://app.rauxdata.com/s/AbCdEf123) that renders your active survey as a full-page experience. You can share this link in Klaviyo, Mailchimp, SMS campaigns, or anywhere else — customers click it and answer without visiting your store.

How to generate a link

1. Go to your project and open the Install tab.
2. Scroll to the Share Link section.
3. Click Generate Link — a unique URL is created and copied to your clipboard.
4. Paste the URL into your email or SMS template.
5. Share it. Responses collected through the link appear in your Analytics dashboard alongside widget responses.

Common use cases

Rotating the link

Click Rotate Link if you need to invalidate the current URL (e.g. after it was shared publicly by mistake). The old link immediately returns a 404. A new link is generated and displayed — update your templates before re-sending.

Identifying respondents

By default, share link responses are anonymous — UTM attribution is captured but no individual customer is identified. To link a response to a specific customer, append an email or customer ID to the URL. rauxdata hashes the email client-side (SHA-256) before storing it — the raw address is never sent to the server.

• By email — append ?email={{ email | url_encode }} (Klaviyo syntax). rauxdata hashes it before submission. Example: https://app.rauxdata.com/s/AbCdEf123?email=jane%40example.com
• By customer ID — append ?customer_id={{ customer.id }} (any platform). The value is stored as-is against the response. Example: https://app.rauxdata.com/s/AbCdEf123?customer_id=cust_12345
• Both params can be combined in the same URL — rauxdata stores whichever are present.
• Identified responses appear in Analytics and exports with the same customerEmailHash / customerId fields as widget responses, and participate in deduplication (one response per customer per 90 days).

Per-Question Integrations

Automatically send Klaviyo events based on individual survey answers — with automatic email resolution.

What are Per-Question Integrations?

Per-Question Integrations let you attach Klaviyo event triggers to individual survey questions. When a respondent answers a question, rauxdata fires a Klaviyo metric event — optionally filtered by specific answer values. This enables powerful automation: welcome flows for customers who found you via Instagram, segmentation by purchase motivation, or loyalty campaigns triggered by NPS promoters.

Setting Up Klaviyo

1. Go to Settings → Integrations in the sidebar.
2. Select the project you want to connect.
3. Enter your Klaviyo Private API key (found in Klaviyo → Settings → API Keys).
4. Choose your region (US or EU) and click Connect.
5. Optionally click Test connection to verify the key is valid.

Adding a Trigger to a Question

Once Klaviyo is connected, open any question card in the Survey Builder → Integrations section. Click "Add Klaviyo trigger" to configure: the event name (sent as a Klaviyo metric), an optional answer filter (fire only for specific answers), and optional static profile properties to attach to the event.

How Email Resolution Works

Klaviyo events are most powerful when they are linked to a customer profile. rauxdata resolves the respondent's email automatically using a 3-step cascade:

Answer Filters

Answer filters let you fire an event only when the respondent chose a specific answer. For example, if your question is "How did you find us?" with options Instagram, Google, TikTok, you can create one trigger per channel — each with a different event name and filter. Leave the filter empty to fire on any answer.

Example: trigger "Discovered via Instagram" fires only when answer = "Instagram". Trigger "Discovered via Google" fires only when answer = "Google". No trigger fires if the answer is "TikTok" and no TikTok trigger is configured.

Webhooks

Send survey responses to any external system in real time — Zapier, Make, Slack, your own backend, or any URL.

Setting Up a Webhook

1. Open your project and go to the Webhooks tab.
2. Click Add webhook.
3. Paste your endpoint URL (must be publicly accessible and return a 2xx status).
4. Optionally add a secret — rauxdata will send it as a header for verification.
5. Toggle the webhook Enabled.
6. Click Save all.

Payload Format

rauxdata sends a POST request to your URL every time a new response is submitted. The body is JSON:

{
  "event": "response.created",
  "projectId": "proj_abc123",
  "response": {
    "id": "resp_xyz789",
    "answers": [
      {
        "questionId": "q1",
        "label": "How did you hear about us?",
        "answer": "Instagram"
      },
      {
        "questionId": "q2",
        "label": "Was it a paid ad or organic?",
        "answer": "Paid ad"
      }
    ],
    "utmSource": "instagram",
    "utmMedium": "paid",
    "utmCampaign": "summer_sale",
    "createdAt": "2026-05-19T14:32:00.000Z"
  }
}

Verifying Webhook Authenticity

If you provided a secret when setting up the webhook, rauxdata sends it in the X-RAUX-Secret header. Verify it on your server before processing the payload.

Common Integrations

Zapier Integration

Connect rauxdata to 5,000+ apps with native Zapier triggers — no code required.

What is the Zapier integration?

The native Zapier integration lets you send rauxdata survey responses and purchase events to thousands of tools — CRMs, email platforms, spreadsheets, Slack, and more — without writing a single line of code. Unlike manual webhooks (which require a server to receive requests), the native integration appears directly in Zapier's trigger picker so anyone on your team can build a Zap in minutes.

How to connect

1. Open your project in rauxdata and go to the Zapier tab.
2. Create an API key if you don't have one (click New API key).
3. In Zapier, create a new Zap and search for "rauxdata" in the trigger app picker.
4. Choose a trigger event (see below) and paste your API key when prompted.
5. Zapier will pull a sample response to verify the connection — then your Zap is live.

Available triggers

Zapier vs. manual webhooks

• Native Zapier: appears in Zapier's trigger picker, no server needed, Zapier manages the subscription lifecycle for you.
• Manual webhook: you provide any HTTPS endpoint — works with Make, n8n, your own server, or "Webhook by Zapier". See the Webhooks section.

Public REST API

Query your response data programmatically using a Bearer-token API key.

Get your API key

1. Open your project in the dashboard.
2. Go to the Install tab → scroll to the API Key section.
3. Click Generate API Key. The key is shown once — copy it immediately.
4. The key starts with rak_ and is scoped to the project it was created in.

Endpoint

All requests must include an Authorization header with the Bearer scheme. The base URL is your rauxdata backend domain.

GET /v1/public/responses?eventType=survey&page=1&limit=50

Authorization: Bearer rak_your_api_key_here

Query parameters

Response shape

{
  "data": [
    {
      "id": "clx...",
      "projectId": "clx...",
      "eventType": "survey",
      "answer": [
        { "questionId": "q1", "label": "How did you hear about us?", "answer": "Instagram" }
      ],
      "utmSource": "instagram",
      "utmMedium": "paid",
      "utmCampaign": "summer-2026",
      "referrer": "https://instagram.com",
      "revenue": null,
      "currency": null,
      "orderId": null,
      "customerType": "new",
      "createdAt": "2026-05-22T14:32:00.000Z"
    }
  ],
  "pagination": {
    "page": 1,
    "limit": 50,
    "total": 243,
    "totalPages": 5
  }
}

Team & Workspace

Collaborate with your marketing team or give clients access to their own workspace.

Inviting Team Members

1. Go to Settings → Team in the sidebar.
2. Click Invite member.
3. Enter their email address.
4. They'll receive an email with an invitation link to join your workspace.

Roles

Workspace Settings

Workspace-level settings (name, domain, billing, and business profile) are accessible via Settings → Workspace. Only the Workspace Owner can access billing and danger-zone actions (like deleting the workspace). The Profile card lets you update your onboarding answers at any time — industry, platform, revenue range, and attribution reporting process for agencies.

Notifications

rauxdata surfaces important events in two ways. In-app: a bell icon in the top-right header shows your unread count. Clicking it opens a panel with recent notifications — NPS detractor alerts, response milestones (100 / 500 / 1 000 responses), and usage warnings when you reach 80 % of your monthly limit. By email: under Settings → Workspace → Notifications, the Workspace Owner can enable a weekly attribution digest sent every Monday at 8 AM UTC with total responses, week-over-week change, top 3 acquisition channels, and match rate. The digest is only sent if at least one response was recorded in the last 7 days.

Multiple Workspaces (Agency)

Workspaces are your boundary for client access and isolation: each one has its own branding and team members. Create a separate workspace per client when you plan to invite that client's own team to it — that way each client only sees their own projects and data. If you're not giving clients direct access, a single workspace can hold projects from several clients at once; group them however you like — by industry, region, or any reason that fits how you work. Use the workspace switcher at the top of the sidebar to switch between workspaces, and you can move a project from one of your workspaces to another at any time from the project's settings (Owner only). Billing is not separate per workspace — it's account-level: a single plan covers all of your workspaces, and only the Owner can see or manage it.

Billing

Manage your plan, upgrade, and view your current usage.

Accessing Billing

Click Billing in the sidebar. Here you can see your current plan, response usage, and upgrade options.

Plans

Response Limits

Each plan includes a monthly response quota. You can see your current usage in the Billing page. When you approach your limit:

• The widget continues to show on your store — no interruption for customers.
• New responses are rejected once the quota is reached.
• You will receive an email alert when nearing the limit.
• You can purchase response add-ons (10,000 responses per unit) from the Billing page without upgrading your plan.

Upgrading

1. Go to Billing in the sidebar.
2. Click Upgrade plan or Manage subscription.
3. You will be redirected to a secure checkout page.
4. After payment, your workspace is upgraded instantly.

For questions about billing, contact us at [email protected].

Data Export

Your response data is yours. Export it at any time in CSV or JSON format.

Exporting Responses

1. Open your project and go to the Install tab.
2. Scroll to the Export responses section.
3. Click CSV or JSON to download all responses.

CSV Format

The CSV export includes one row per response with columns for:

• Response ID and timestamp
• All survey answers (one column per question label)
• UTM source, medium, campaign
• Referrer URL
• Revenue, currency, and order ID (when purchase tracking is active)
• Customer type (new or returning)
• Browser and device

JSON Format

The JSON export provides the full structured response object, identical to the webhook payload format. Ideal for importing into data warehouses or custom analysis tools.

Agency Onboarding

How the setup wizard works for agency workspaces.

Workspace Type Selection (Step 0)

When you create a new workspace, the setup wizard starts with a "What best describes you?" screen. Select "I manage clients as an agency" to unlock the agency-specific profile steps.

Step 1 — Agency Portfolio

• Portfolio size: How many active clients you manage (1-5, 6-15, 16-50, 50+).
• Main verticals: The industries your clients operate in (DTC, Retail, CPG, Beauty, Fashion, Food, Mixed).

Step 2 — How You Work

• Reporting process: How you currently report attribution results to your clients (manual, platform-native tools, a dedicated reporting tool, or no formal process).
• How you found us: The acquisition channel that brought you to rauxdata.

Per-Project Client Profile

When creating a new project in an agency workspace, you can optionally fill in a client profile to help tailor the experience. All fields are optional — you can skip this step without blocking project creation.

• Industry: The client's industry vertical.
• Platform: The e-commerce platform the client uses.
• Revenue range: Approximate monthly revenue in USD.

FAQ

Common questions, answered.