Rekomi Docs
For brandsInstall tracking
Brands

Install tracking

Pick the platform you bill on. Each install doc covers the exact UI navigation, the specific quirks, and the conversion-fire pattern for that platform.

Rekomi attributes affiliate conversions through one of three paths depending on where your customer's checkout lives. The right install is the one that matches your billing or hosting platform.

In the dashboard, the Install tracking script step at /dashboard/setup/install leads with your universal tracking snippet (a dropdown switches the paste form between HTML, Next.js, React, Vue/Nuxt, and Google Tag Manager), followed by a searchable platform picker grouped into site builders, frameworks and code, and payment gateway guides. Picking a platform there opens the same step-by-step recipes listed below.

The Install tracking script step: the universal tracking snippet with the searchable platform picker

Payment gateways

Native integrations for the gateway you bill on: the gateway itself reports every sale, renewal, and refund, so commissions mint and adjust automatically with no backend code. Stripe is the deepest (and the Rekomi Marketplace app lets you run the whole program from inside the Stripe Dashboard); most of the rest are a one-paste connect, and WooCommerce, Wix, and Gumroad are one-click. The Payment gateways overview shows all of them side by side with what each connect involves.

Membership, course, and newsletter platforms

Hosted platforms that run their own checkout. Most bill through a Stripe account you connect, so the head script captures the click and your Stripe webhook records the sale. Where the platform itself is the merchant of record, conversions record through per-affiliate coupon codes or a webhook relay to Rekomi's S2S endpoint instead.

Site builders

Visual page builders that host your marketing surface. Most route to an external Stripe checkout for the actual sale; the head install captures clicks before the buyer leaves your site. (Wix and WooCommerce sit under Payment gateways above: their native apps track store orders directly. The WordPress guide covers both WordPress paths.)

Frameworks

Code-first installs for custom apps. Vanilla HTML and SPA frameworks install the same click-capture script; conversions are recorded through your connected payment processor, coupon codes, or the server-to-server API. Backend-heavy frameworks (Rails, Django) can post conversions server-to-server directly.

Not on this list?

If your billing platform isn't covered above but supports either a webhook or a JS-pixel injection point, the install pattern is one of the two we use for everything else: server-to-server S2S for webhook-based platforms, or the JavaScript pixel for sites where you can inject a script tag. The platform guides above are pre-written walkthroughs of those two patterns for the most common platforms.