Install on Outseta

Outseta is an all-in-one authentication, billing, and CRM layer that sits on top of a host site you control (Webflow, Carrd, WordPress, or custom HTML). Rekomi installs in the host's head, alongside the Outseta embed code. Connecting your own Stripe account is part of every Outseta account, so conversion reporting flows through the same Stripe rail Rekomi's Stripe-native customers use. No thank-you-page snippet is needed; the head script records a lead at signup and the Stripe sale matches it by email.

Install the head script on the host

The Outseta embed and the Rekomi script both live in the host's <head>. Order does not matter, but both must run on every page where affiliate clicks could land.

Webflow: Site settings > Custom code > Head code.

Carrd: Site Settings > Code > Head.

Custom HTML / WordPress: Paste inside the <head> of the shared template (or via a header-injection plugin like WPCode for WordPress).

<script async src="https://api.rekomi.com/api/v1/r/loader.js" data-program-id="YOUR_PROGRAM_ID" data-rkmi-email-capture="auto"></script>
<noscript>
  <img src="https://api.rekomi.com/api/v1/r/c.gif" width="1" height="1" alt="" referrerpolicy="no-referrer-when-downgrade" />
</noscript>

Your program ID is pre-filled into the snippet in Rekomi under Setup > Install (choose Outseta). The Outseta embed code (from Outseta admin > Auth > Embeds) sits next to this; both load independently and don't conflict.

How attribution works

Outseta routes payments through the Stripe account you connected when you set up Outseta. Connect that same Stripe account to Rekomi under Setup > Connect payment gateway and every sale, refund, and cancellation records automatically.

Recording is automatic; crediting the affiliate is not. A Stripe sale attributes by a redeemed Rekomi coupon, by rekomi_affiliate_slug or rekomi_affiliate_id subscription metadata, or by matching the checkout email against a lead recorded in the last 90 days. The click cookie the head script sets is never read server-side, so a click alone cannot credit a sale. Outseta's signup widget does not let you stamp Stripe metadata, which leaves the lead path as the one that works here.

Record the lead at signup. Any of these paths works:

• From the page. When a visitor submits Outseta's signup form, call window.Rekomi.convert({ email: "the-signup-email" }) from your host page. The head script is already loaded, so this is one line in your form handler. You own the host page, so this stays the most precise developer path.
• No code. The data-rkmi-email-capture="auto" attribute on the head script above records the lead the moment a visitor finishes typing their email anywhere the script runs. That covers Outseta's login step and any Outseta embed whose signup never fires a form submit, so no form handler is needed. It records nothing without a referral, and plus-addressed variants such as you+test@gmail.com and you@gmail.com count as the same inbox. If you added a separate lead-capture snippet from an earlier version of this page, delete it.
• From a webhook. Relay Outseta's signup webhook (Outseta admin > Auth > Webhooks) from your backend to Rekomi's lead endpoint at POST /api/tracking/lead.

When Stripe reports the subscription, Rekomi matches the checkout email to the lead and credits the affiliate. See Track leads and signups for the full contract.

Prefer not to connect Stripe?

If you would rather not connect your Stripe account to Rekomi, you can relay paid signups from your own backend to Rekomi's server-to-server endpoint instead. The two rails are mutually exclusive: the S2S endpoint returns 409 while a Stripe connection is active, so pick one. For most Outseta accounts the Stripe connection is less work and handles refund clawbacks automatically.

Quirks worth knowing

Outseta is an overlay, not a host. The script always installs in the host's head. There is no Outseta admin slot for arbitrary head HTML; trying to install via Outseta will not work.

SPA-style member areas. Outseta's authenticated widgets render in place without navigating to new URLs. The captured referral is still valid because it was set on first visit to the host domain. If your signup flow lives on a separate subdomain, install the Rekomi script there too so the click is captured wherever visitors land.

Email match needs the lead first. Rekomi attributes the Stripe sale by matching the checkout email against a lead recorded in the last 90 days. If no lead was recorded, or the buyer pays with a different email than they signed up with, there is nothing to match and the purchase does not appear as a sale. Recording the lead at signup, before checkout, is what makes the match reliable.

Troubleshooting

Signup completes but no conversion lands in Rekomi. Confirm Stripe is connected under Setup > Connect payment gateway in Rekomi, then check the Conversions page, where each conversion shows its source. Stripe events reach Rekomi through Rekomi's own platform-level webhook, so they will not appear in your Stripe account's webhook deliveries list.

Stripe is connected but the purchase does not appear as a sale. A purchase that reaches Rekomi with no matching lead is skipped and does not appear on the Conversions page. Either no lead was recorded before checkout, the lead was older than 90 days, or the buyer used a different email at checkout. Check two things: the head script tag carries data-rkmi-email-capture="auto", and the buyer typed their email on a page where that script runs. If you rely on the developer path instead, verify your form handler calls window.Rekomi.convert({ email }) (or your webhook relay posts to /api/tracking/lead) with the same email the buyer pays with.

Referral is missing on the signup page. The visitor likely reached the signup page through a path that bypassed your Rekomi-bearing pages (a direct deep link). The referral has to be captured on at least one host-domain page before the visitor reaches signup. Audit your top-of-funnel pages and confirm the head script is everywhere. You can check in the browser console with window.Rekomi.getReferral().

Related

• Track leads and signups
• S2S tracking API reference
• Tracking and attribution overview