Docs

After signing up, you'll be prompted to create a workspace. A workspace is the top-level container for your business — it holds your programs, partners, and settings including your API key.

From your dashboard, create a program and choose a default percentage or flat commission. Stored rules can be one-time, recurring for a defined number of periods, or lifetime, with priority, hold periods, and partner-specific overrides.

In Settings, connect RevenueCat, choose the production or sandbox environment, and configure the displayed workspace webhook URL in RevenueCat with the same shared signing secret. Conduit normalizes purchases, renewals, trial conversions, cancellations, reactivations, expirations, product changes, billing issues, and refunds into customer, subscription, and revenue-event records.

Provider event IDs are processed idempotently, so a retried webhook does not create a second economic event.

Add a partner to a program directly, or invite them by email. Once added, a partner is automatically issued a unique referral code and a /r/{code} link.

A referral link looks like https://yourapp.com/r/abc123. When someone clicks it, Conduit logs the click and redirects them to your product, starting the attribution window for that visitor.

Some channels (podcasts, in-person, print) don't support clickable links. Partners can share their plain code instead — you can accept it manually or via the conversion API using the code field.

You can record a conversion manually from the dashboard, or send one from your backend using the conversion API:

curl -X POST https://conduitreferral.com/api/public/conversions \
  -H "Authorization: Bearer <your-api-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "event_id": "unique-idempotency-id",
    "code": "creator-code",
    "type": "purchase",
    "amount": 29.99,
    "currency": "USD",
    "customer_ref": "user_123",
    "occurred_at": "2024-01-01T00:00:00Z",
    "metadata": { "plan": "pro" }
  }'

You can identify the referring partner either by code or by visitor_id (the identifier tied to a prior click). event_id should be a unique ID you generate so retries don't create duplicate conversions. Supported type values are signup, subscription, purchase, renewal, refund, and cancellation.

Conduit uses first-touch attribution: whichever referral link or code a visitor interacted with first, within your program's attribution window, gets credit for the conversion. This gives clear attribution across the partner journey, but it has real limitations worth understanding:

• Cross-device journeys — if someone clicks a link on their phone but converts on desktop, the two aren't automatically linked.
• Private browsing — incognito/private modes can prevent the attribution identifier from persisting.
• Cookie expiry — if the attribution window has passed, a later conversion won't be attributed to that earlier click.
• Direct traffic after a referral — if a user closes the tab and later navigates directly, attribution depends on the identifier still being present and valid.

Conduit selects the applicable rule and calculates a percentage or flat commission. Rules can apply once, for a defined number of recurring periods, or for the customer lifetime. Hold periods keep new earnings from becoming payable too early. Refunds, partial refunds, chargebacks, and reversals are recorded as signed adjustments so the original commission record remains intact.

The payout workspace separates preparation, approval, initiation, and reconciliation. Only eligible, approved net commissions can be attached to a payout. With Stripe Connect configured, partners complete Stripe-hosted onboarding and an administrator explicitly confirms money movement. Stripe handles financial-account details and the transfer; Conduit stores provider references and payout state.

Analytics uses the revenue and commission ledgers to report active MRR and ARR, MRR movement, net revenue retention, logo churn, refunds, cohorts, average customer lifetime, LTV, commission cost, efficiency, and partner quality. Use the range control to compare the last 6, 12, or 24 months.

Before going live, click your own referral link in an incognito window, confirm the click appears in your dashboard, then send a test conversion via the API using a unique event_id and the code from your test click. Confirm the conversion and commission show up correctly, then approve or reject it to verify the ledger status transitions. For RevenueCat, use its sandbox environment and a test webhook signing secret before switching the integration to production.