Install on Carrd
Hidden Embed element with Location set to Head, or Pro Plus Site Settings 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 Lite ($19/yr) or higher is required to embed scripts. Free Carrd sites strip all custom code. Once you're on a paid plan, the install is a 30-second job. Two install paths depending on your tier.
Path A: Hidden Embed element (works on Pro Lite 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
- Style:
- Paste in the Code box:
<script>
(function(){
var s=document.createElement('script');
s.src='https://js.rekomi.com/v1/rekomi.js';
s.async=true;
s.dataset.programId='YOUR_PROGRAM_ID';
document.head.appendChild(s);
})();
</script>- 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 in Rekomi at Settings > Tracking.
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 Lite, 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: add the MutationObserver auto-stamping snippet (see Install on Stripe) so Payment Links carry the affiliate referral into Stripe. Conversion fires via the Stripe webhook on completion.
Embedded Stripe Pricing Table: same as above. The Pricing Table renders Payment Link buttons; the observer stamps them.
Embedded third-party form (ConvertKit, Substack): the affiliate slug travels into the form as a hidden field, then the third-party fires its own conversion event when the email is captured. For ConvertKit, see Install on Kit.
Quirks worth knowing
Pro Lite or higher required. Free Carrd strips all custom code from published sites. You'll see the Embed element in the editor, but nothing renders in the published HTML. Upgrade.
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 Lite. 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. Upgrade to Pro Lite 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.
Click cookie missing on the external Stripe Checkout page. Carrd's domain is different from buy.stripe.com. The cookie set on your Carrd site persists in the visitor's browser; when they navigate to Stripe Checkout, the affiliate slug travels via the ?client_reference_id=<slug> URL param (added by the MutationObserver snippet). Confirm the observer is installed.
Related
- JavaScript pixel reference
- Install on Stripe — for MutationObserver pattern on Payment Links
- Install on Kit — for ConvertKit form integration patterns
Install on Bubble
Settings SEO/metatags Header field for the install. Conversion fires from an HTML element on the post-signup success page using Bubble's dynamic email expression.
Install on Vanilla JavaScript
Plain HTML, no framework, no bundler. Script tag in the head of every page for click capture, convert snippet on the thank-you page only.