Frequently Asked Questions

Common questions about Affitor's pricing, tracking, commissions, and integration options.

General

What is Affitor?

Affitor is an affiliate growth platform for SaaS companies. It tracks partner-driven clicks, signups, and sales, and manages commissions and payout operations in one workflow.

Who is Affitor built for?

Affitor is designed for SaaS teams that want to launch or scale a partner program without taking on the full operational burden themselves.

How is Affitor different from traditional affiliate tools?

Affitor differentiates on:

performance-based pricing
first-party tracking for click → signup → sale flows
support for Stripe integration or Server-side tracking
commission and payout operations in one workflow

Pricing & Billing

How much does Affitor cost?

Affitor charges a 3.5% platform fee on partner-generated revenue.

no monthly subscription
no setup fee

What about the $10K fee-free threshold?

Affitor's pricing includes a $10K fee-free threshold on affiliate-driven revenue. Confirm your commercial terms directly with the Affitor team before a launch decision.

In the invoice billing model, Affitor bills you through its invoice workflow after tracked conversions are validated. Confirm billing timing directly with the Affitor team if it affects your launch decision.

Does Affitor collect money from my customers?

No. Affitor is not the merchant of record. You continue charging customers through your own Stripe or payment setup.

Tracking & Integration

What integration paths are supported?

Three main paths are supported:

Tracker install for click tracking
Browser signup helper or server lead API for signup attribution
Server-side tracking or Stripe integration for revenue attribution

What is the difference between `customerKey`, `customer_key`, and `affitor_customer_key`?

They represent the same business concept in different integration contexts:

customerKey — browser helper argument for signup(customerKey, email)
customer_key — field used in the tracking API payloads
affitor_customer_key — Stripe metadata field

Use the same internal user/customer ID across all three.

Can I use Affitor without changing my checkout?

Usually yes. If your backend can call POST /api/v1/track/sale, or if you already use Stripe Checkout and can attach Affitor metadata, you can integrate without replacing your existing payment stack.

Does Affitor only work with Stripe?

No. Stripe is the best-documented integration path, but Server-side tracking works with any backend/payment provider that can send revenue events after payment succeeds.

How does attribution work?

Affitor uses:

first-party tracking
last-click attribution
a documented 60-day default attribution window

For the most reliable results, install the tracker first, send a stable internal customer ID at signup, and reuse that identifier in sale tracking.

What happens if the customer later pays on Stripe?

With Stripe integration, Affitor attributes the sale from metadata and webhook events. For subscriptions, renewals also require subscription_data.metadata to be populated.

Commissions & Payouts

Who pays the partner?

Affitor handles partner commissions and payouts after attributed conversions move through the commission lifecycle.

What happens after a sale is attributed?

At a high level:

sale is recorded
commission is created
commission moves through review / hold operations
payout workflow continues in Affitor

signup used the wrong internal identifier
Stripe metadata used a different identifier than signup
Server-side tracking payload omitted customer_key / click_id
subscription metadata was only added to the initial checkout, not subscription_data.metadata

How do I get help?

After working through the integration and testing guides, contact the Affitor team with:

your program ID
the exact integration path you used
request/response samples or Stripe webhook evidence
screenshots of any relevant dashboard/test-event state