Install on Carrd

Hidden Embed element with Location set to Head on Pro Standard or higher, or the Pro Plus site-wide Code field. Carrd's single-page nature means the cookie persists naturally.

Carrd is the simplest install in the platform set, with one constraint: Pro Standard ($19/yr) or higher is required to embed scripts. Free sites strip all custom code, and Pro Lite ($9/yr) does not include embedding your own code either. Once you're on Pro Standard or above, the install is a 30-second job. Two install paths depending on your tier.

Path A: Hidden Embed element (works on Pro Standard and above)

In the Carrd site editor:

Add an Embed element near the top of your element stack.
In the Embed element's Settings panel:
- Style: Hidden
- Location: Head
Paste in the Code box:

<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>

Publish the site.

The Hidden style means the Embed renders no visible content on the page; the Head location means Carrd injects the contents into <head> rather than <body>. The browser sees this as a normal head script and loads Rekomi normally.

Your program ID is pre-filled into the snippet in Rekomi under Setup > Install (choose Carrd).

Path B: Site-wide head slot (Pro Plus $49/yr only)

If you're on Carrd Pro Plus, you also have access to a dedicated site-wide head code slot:

Carrd dashboard > Sites > [your site] > Settings > Code > head section.

Paste the same head script there. Either approach works on Pro Plus; the Embed-element approach is the only option on Pro Standard, so it's the more universal recommendation.

Carrd is single-page

Unlike multi-page sites, the entire Carrd experience lives on one URL. That means the Rekomi cookie persists naturally throughout the visitor's session, they never navigate away from a page where the script is loaded. The script in head loads once on initial visit and stays in memory.

This also means there's no "thank-you page" install needed on Carrd itself, because Carrd doesn't host the checkout. Carrd is a marketing/landing page; the actual sale happens elsewhere (Stripe Checkout, ConvertKit form, Substack subscribe, etc.).

Conversion strategies on Carrd

Since Carrd doesn't host checkout, your conversion-fire mechanism depends on where the sale actually completes:

External Stripe Payment Links: attribute these with per-affiliate coupon codes. Stripe hosts the checkout page, so a script on your Carrd site cannot pass the referral through it; the code the buyer redeems is what credits the affiliate. Turn on Allow promotion codes on the Payment Link, create the coupon under your campaign's Coupons tab, and each affiliate shares your link with ?prefilled_promo_code=THEIRCODE appended. Full walkthrough: Install on Stripe.

Embedded Stripe Pricing Table: same as above; buyers enter or pre-fill the affiliate's code at checkout.

Embedded third-party form (ConvertKit, Substack): capture the referral into a hidden field on the form and record the signup server-side, or use per-affiliate coupon codes at the eventual checkout. See Install on Kit for the pass-through pattern.

Quirks worth knowing

Pro Standard or higher required. Free Carrd strips all custom code from published sites, and Pro Lite ($9/yr) does not include embedding your own code. You'll see the Embed element in the editor, but your script won't render in the published HTML. Upgrade to Pro Standard ($19/yr) or higher.

Single-page means simpler attribution. Most multi-page platform docs talk about "ensuring the cookie is set on every page", that concern is moot for Carrd because there is no second page.

Hidden Embed element trick. Setting Style to Hidden + Location to Head is the "official" way to inject head code on Pro Standard. It's not a hack, Carrd's docs reference this pattern.

Carrd Pro Plus extra slot. The Pro Plus tier adds a dedicated Code section in Site Settings with a head field. If you have multiple analytics scripts to install, the dedicated slot is cleaner than stacking Embed elements.

Form actions go elsewhere. Carrd forms typically POST to a third-party endpoint (Formspree, your own backend). The Rekomi click cookie travels with the visitor's browser state, not with the form POST. If your form submits cross-domain, the cookie won't follow, you need to capture the affiliate slug on the form's success page or in the destination handler.

Troubleshooting

Script in Embed element but not in published HTML. You're on Carrd Free or Pro Lite, and neither can embed your own code. Upgrade to Pro Standard or higher.

Embed element shows a visible box on the page. You forgot to set Style to Hidden. Open the Embed element's Settings panel and set Style → Hidden.

Embed element renders in <body> instead of <head>. You forgot to set Location to Head. Same Settings panel.

Payment Link sale completed but did not attribute. Carrd's domain is different from buy.stripe.com, so the click cookie never reaches Stripe's checkout; only a redeemed promotion code names the affiliate there. Confirm Allow promotion codes is on for the Payment Link and that the buyer's code is one Rekomi created for that affiliate.

No-code and non-Stripe checkout tracking
Install on Stripe, for the Payment Links coupon walkthrough
Install on Kit, for ConvertKit form integration patterns