Install on Framer
Site Settings Custom Code tab, "Start of head tag" field. Publish is explicit. Custom code needs a paid site plan, and the sale itself always completes off-Framer via Stripe.
Framer's install is a single paste in the Custom Code tab of Site Settings. Two operational notes worth knowing up front: Saving does not publish (Framer's Publish is an explicit action), and the free plan cannot ship custom code (any paid site plan includes it).
Open the head slot
In the Framer editor: gear icon (top-right of the editor) > Site Settings > the Custom Code tab.
Use the field labeled "Start of <head> tag". The tab also offers end-of-head and body slots; those are the wrong place for click capture, Rekomi needs the start of <head>.
Paste the head script
In the "Start of <head> tag" field:
<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 Framer).
Publish
Click Publish (top-right of the editor). Without an explicit Publish action, your saved-but-unpublished site does not pick up the change. Framer treats Save and Publish as separate.
Where the sale happens
Framer has no native checkout and is not a merchant of record, so the sale always completes off-Framer: Stripe Checkout or a Stripe Payment Link in the common case, or an embedded third-party checkout.
The common SaaS pattern: use Framer for marketing pages only, link out to Stripe Checkout or Stripe Payment Links for the actual sale. The head script captures clicks; the Stripe webhook closes the loop on the conversion. No Framer-specific conversion-fire step needed. For Payment Links specifically, attribution runs on per-affiliate coupon codes; see Install on Stripe.
If checkout happens in an embedded third-party provider instead, track conversions with per-affiliate coupon codes (Campaign > Coupons), or relay the sale from that provider's webhook into Rekomi's S2S tracking endpoint from your own backend.
Per-page custom code (skip it)
Framer also exposes per-page custom code via the Page Settings panel. Keep the Rekomi install in the site-wide Site settings slot, not per-page. Duplicating the script across pages risks double-firing clicks and confusing the cookie state.
Quirks worth knowing
Publish is explicit, not automatic. Framer's Save updates your draft; Publish ships to production. Forget Publish and your changes never reach visitors.
Free plan strips custom code. Framer's free plan does not ship any custom code blocks to production, regardless of how many times you Publish. Any paid site plan includes custom code.
Framer Components don't expose custom-code slots. Custom code lives at the Site or Page level, not the Component level. If you're using a third-party component (e.g., a pricing table from Framer's marketplace), the Rekomi script in Site settings still runs on the page that renders the component, no per-component install needed.
No order data on the page. The sale completes off-Framer, so there is no reliable way to record a sale from the Framer page itself. Record conversions where the money moves: through your Stripe connection, with per-affiliate coupon codes, or via an S2S relay from your checkout provider's webhook.
Troubleshooting
Published the site but Rekomi script does not appear in View Source. Three things: confirm the script is in the "Start of <head> tag" field on the Custom Code tab (not a body slot); confirm you clicked Publish after Save; confirm your site is on a paid plan (free sites strip custom code).
Click cookie sets on the homepage but not on /pricing or other pages. The script lives in Site settings (global), so it loads on every Framer-rendered page. If a specific page is missing the script in View Source, the page might be a Framer-hosted redirect or a custom-domain misroute. Verify Framer is actually serving that page.
Custom domain shows the script but the Framer preview does not. Framer's preview at your-site.framer.website may not include all Site Settings until you publish. Test on the custom domain after Publish for the most accurate read.
Related
- No-code and non-Stripe checkout tracking
- Install on Stripe, for the Payment Links coupon walkthrough when selling via Framer-hosted marketing pages
Install on Webflow
Site settings Head code for the global install. Webflow Ecommerce orders relay to Rekomi's S2S API via the ecomm_new_order webhook; external Stripe Payment Links attribute via per-affiliate coupon codes.
Install on Squarespace
Code Injection Header field on the Core plan or higher. Squarespace Commerce runs on your own Stripe so attribution works automatically once the head script is in place.