Install on Memberstack

Memberstack is an overlay, so Rekomi installs on the host (Webflow, custom HTML, Duda), not in Memberstack itself. Sales record through your own Stripe account via Stripe Connect, coupon codes, or a server-to-server relay.

Memberstack is an authentication and gated-content overlay, not a host. It sits on top of a host platform you control: Webflow, Duda, custom HTML, or another site builder. Rekomi installs on the host's head, not in Memberstack itself, because the head-script slot belongs to the host. Memberstack bills through your own Stripe account, so the sale is recorded through Stripe (or coupon codes), not from a page snippet.

Install the head script on the host

Open your host platform's site-wide head code and paste the Rekomi script.

Webflow: Site settings > Custom code > Head code.

Custom HTML / static site: Paste in the shared template's <head>, before any other scripts that depend on member context.

Duda: Site Overview > Site Settings > Header HTML.

<script async src="https://api.rekomi.com/api/v1/r/loader.js" data-program-id="YOUR_PROGRAM_ID"></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 Memberstack). This script captures the affiliate click on every host-domain page visit.

Record conversions

Memberstack runs subscriptions through your own Stripe account, so there is no thank-you-page snippet to add. Pick one of these paths:

Stripe Connect (recommended). Connect Stripe once in Rekomi under Setup > Connect payment gateway. When a member upgrades, Rekomi records the sale automatically and reverses commissions on refunds. Recording is automatic; crediting a first-time customer 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 the head script captured is never read server-side on the Stripe rail, so it cannot credit the sale on its own. If your flow creates the Checkout Session, stamp window.Rekomi.getReferral() into the subscription metadata as rekomi_affiliate_slug. If it does not, record a lead at signup with window.Rekomi.convert({ email }) so the sale email-matches.

Coupon codes (no code). Create per-affiliate coupon codes under Campaign > Coupons and hand them to your affiliates. Coupons work on Memberstack because its checkout is Stripe Checkout on your own Stripe account, so the code is redeemed as a real Stripe promotion code; that same Stripe account must be connected to Rekomi. A redeemed code at checkout credits the affiliate. Nothing to add on any page.

Server-to-server (most durable). Relay Memberstack's member.created (paid) webhook, or your Stripe webhook, into Rekomi's S2S tracking endpoint with HMAC from your backend. This carries the real order amount without depending on the browser. S2S and a live Stripe connection are mutually exclusive: the endpoint returns 409 while Stripe is connected, so pick one rail.

Quirks worth knowing

Memberstack runs on a host platform. The Rekomi script always goes in the host's head, never in Memberstack's own admin panel. There is no "install Rekomi in Memberstack" option; Memberstack is the authentication layer, not the page renderer.

The sale is recorded off the page. Because conversions flow through Stripe (or a server-side relay), you never hard-code plan prices into a page snippet or race Memberstack's client session to read member data. The real amount comes from Stripe.

Link-based attribution needs a stamp or a lead. The head script only captures the click in the browser; the Stripe rail never reads it server-side. For affiliate links to credit sales, either stamp window.Rekomi.getReferral() onto the subscription metadata when your flow creates the checkout, or record a lead at signup so the sale email-matches. Coupon codes attribute on their own without either.

SPA-style member areas. If your member-only pages are rendered in place (no full navigation between pages), the captured referral still applies because it was set on first visit to any host page.

Refunds and subscription changes

Memberstack handles billing through Stripe under the hood. If your Memberstack account is on Stripe Connect with Rekomi-listening webhooks, refunds clawback automatically through the Stripe webhook rail. If you record sales through the server-to-server relay instead, forward the refund event from the same backend to /api/tracking/refund.

Troubleshooting

Sale completes but no conversion lands in Rekomi. If you use Stripe Connect, confirm Stripe is connected under Setup > Connect payment gateway, then check the Sales page in Rekomi, 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. If you attribute by coupon code, confirm the member redeemed the affiliate's code at checkout.

Affiliate credited on the wrong sale. Two affiliates' codes collided. Make sure each affiliate has a unique code under Campaign > Coupons.

Click never registers. The visitor reached the signup page via a path that bypassed a head-script-bearing page, so no referral was captured. Confirm the head script is installed on every top-of-funnel host page. You can check for a captured referral in the browser console with window.Rekomi.getReferral().