Install on Kit (ConvertKit)
Connect Kit under Integrations and Kit Commerce sales credit the affiliate whose link brought the subscriber, from Kit's own signup record. Kit Commerce bills through a Kit-managed Stripe account that cannot be connected, so Rekomi takes Kit's purchase feed instead. A per-landing-page script is optional and adds click stats.
Kit (formerly ConvertKit) has two constraints that used to make this install the most work of any platform: there is no site-wide head slot for a script, and Kit Commerce bills through a Stripe Express account that Kit manages, which cannot be connected to Rekomi. Neither matters any more. Kit itself records how every subscriber arrived through a Kit form or landing page, every affiliate link Rekomi hands out carries a tag Kit stores at that signup, and once Kit is connected in Rekomi with Credit sales through Kit on, Rekomi takes Kit's purchase feed directly. The install is one connection in Rekomi. A per-landing-page script is optional and adds click counts.
Note on the CRM vs Commerce sides of Kit
There is one Kit connection in Rekomi and it does both jobs. Sync affiliates into Kit adds approved affiliates to a Kit form as tagged subscribers. Credit sales through Kit credits sales, Kit Commerce included, to the affiliate whose link brought the subscriber. The Kit CRM page covers both switches, the status line, the signup alerts and the limits; this page is the install order for a brand that sells through Kit.
Step 1: Connect Kit under Integrations
- In Kit, open Settings → Developer and click Generate API Key to create a v4 API key (legacy v3 secrets do not work).
- In Rekomi, open Integrations, click the Kit card, paste the key and click Connect. Rekomi verifies the key, checks that it can look subscribers up, and registers Kit's purchase feed with your account.
- Leave Credit sales through Kit on. It is on from the moment you connect. Pick a default form for Sync affiliates into Kit if you want your affiliates in Kit, or turn that switch off.
That is the install for Kit Commerce. If you sell through your own Stripe instead of Kit Commerce, also connect that Stripe account under Setup > Connect payment gateway; the Kit connection then names the affiliate on sales Stripe reports.
Test it
- Sign in as one of your affiliates (or use a test affiliate) and copy their link. It looks like
https://newsletter.example.com?via=jane&utm_source=rekomi&utm_campaign=jane: the last two parameters are the tag Kit stores. - Open the link in a private window and sign up through your Kit form or landing page with a fresh email address.
- On the Kit integration page in Rekomi, enter that address under Check a subscriber's email. It should say the subscriber exists, the tag names your affiliate, and a sale from that email would be credited.
- Buy a Kit Commerce product with that address. The purchase appears in the campaign's Activity view as a credited sale, with Kit as the source.
How attribution works
- Every affiliate link Rekomi generates for your campaign carries
utm_source=rekomiandutm_campaignset to the affiliate's link slug, on top of the usual?via=parameter. - When a reader lands from that link and signs up through a Kit form or landing page (the JS embed of a Kit form on your own site counts), Kit stores those values on the subscriber. Kit writes them once, on that first signup.
- When the subscriber buys a Kit Commerce product, Kit's purchase feed tells Rekomi. Rekomi confirms the buyer by reading the subscriber back from Kit, records the sale once per Kit purchase id, and credits the affiliate the stored tag names. Sales on your own connected Stripe follow the same path through Stripe's events.
- Nothing runs in the buyer's browser for any of this.
Two cases this cannot cover, stated plainly: a buyer who goes straight to a Kit Commerce checkout without ever signing up through a Kit form or landing page (Kit records no arrival on a checkout-first subscriber), and a subscriber who was already on your list before they clicked the affiliate link (Kit keeps the first record). The optional script below records a lead when such a reader types their email on a page where it runs, and that lead credits the sale by email match within 90 days.
Optional: click stats with a per-landing-page script
You do not need this for sales to credit. Add it if you want click counts in the dashboard, or to cover the two cases above on the pages affiliates send traffic to.
Kit does not have a site-wide head HTML slot, so the script goes on each landing page individually.
Step 1. In Kit, navigate to Grow > Landing Pages & Forms > select a landing page.
Step 2. In the landing page editor, click the + icon in the toolbar > Script.
Step 3. Paste the Rekomi head script:
<script async src="https://api.rekomi.com/api/v1/r/loader.js" data-program-id="YOUR_PROGRAM_ID" data-rkmi-email-capture="auto"></script>Rekomi records an email a referred visitor types into any email or text field on the pages where the tag runs (signup, login, checkout and other forms) so the sale can be credited even when the checkout passes no referral. Nothing is recorded without a referral. Remove the data-rkmi-email-capture attribute to turn this off; explicit Rekomi.convert() calls still work.
Step 4. Publish the landing page, and repeat for every landing page that affiliates send traffic to.
Kit's public API has no endpoint for updating landing-page content, so the paste is manual per page. Copy the snippet with your program ID already filled in from Setup > Install in Rekomi.
Why coupon codes are not a fallback here
Rekomi coupon codes are real discount codes minted on a connected payment gateway (Stripe, Shopify, or Wix), and attribution happens when that gateway reports the redemption. Kit Commerce runs its own checkout with its own discount codes, so a code typed there never reaches Rekomi. For Kit-hosted products, the Kit connection above is the attribution path; coupon-based attribution only applies if you sell through a connected gateway instead of Kit Commerce.
Quirks worth knowing
Kit Commerce runs on a Kit-managed Stripe account. It is a Stripe Express account under Kit's platform, not yours, so it cannot be connected to Rekomi and its payments never arrive as Stripe events. That is why Rekomi takes Kit's purchase feed instead; the connection registers it for you and removes it when you disconnect.
Kit has no refund event. A refunded Kit Commerce purchase does not reverse the commission on its own, because Kit does not tell Rekomi. When you refund a Kit order, invalidate the matching sale from the Conversions page and the commission reverses.
Only form and landing-page signups carry the tag. Subscribers created by import, by the API, through the Creator Network, or by a Kit Commerce order with no earlier signup carry no arrival record.
Kit's rate limit is shared. Kit allows 120 requests per minute per key. Rekomi makes a read or two per sale, keeps a short per-email cache so the same buyer is not read twice in a burst, and tries a read again after two minutes if Kit answers 429. The affiliate sync honors Retry-After, so a busy launch day slows the sync a little rather than dropping sales.
Kit landing pages and Kit forms each have their own script slot. If you add the optional script, installing it on a form does not cover the landing pages, and the other way round.
Troubleshooting
A Kit Commerce purchase shows as a purchase but not as a credited sale. Enter the buyer's address under Check a subscriber's email on the Kit integration page. No subscriber means the buyer went straight to checkout without a form signup. A subscriber with no tag means they joined before the click, or through an import, the API or the Creator Network. A subscriber with the tag and still no credit means the sale arrived before Kit had finished creating the subscriber. Rekomi keeps checking Kit for that email for about two hours (after 2 minutes, 15 minutes and 2 hours) and credits the sale when the subscriber appears with the tag, so wait a few minutes and look again.
Purchases never appear at all. Credit sales through Kit is off, or the connection was made before the purchase feed existed. Turn the switch off and on again on the integration page; Rekomi re-registers the feed.
Wrong amount on a commission. Kit reports money in decimal currency units; Rekomi converts them. If an amount looks 100x off, contact support with the Kit purchase id.
Multiple landing pages, inconsistent click counts. You installed the optional script on some landing pages but not others. Only the ones with the script count clicks; sales credit either way.
Related
- Kit CRM connection: the two switches, the status line, signup alerts and limits
- No-code and non-Stripe checkout tracking
- S2S tracking API reference, for sales that happen on your own backend
Install on beehiiv
Connect the Stripe account beehiiv bills through and connect beehiiv under Integrations. Premium Subscription sales then credit the affiliate whose link brought the reader, from beehiiv's own signup record, with nothing in the reader's browser. A Google Tag Manager tag is optional and adds click stats.
Install on WordPress
The Rekomi plugin is the one-click path, with or without WooCommerce. WPCode stays documented as the no-plugin alternative.