Install on Framer
The head slot lives behind "Show Advanced" in Site settings and many brands miss it. Publish is explicit. Free plan cannot ship custom code.
Framer's custom-code install hides the head slot behind a "Show Advanced" disclosure that's easy to miss on first install. Once you find it, the install itself is a single paste. 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 (Mini plan or higher required).
Open the head slot
In the Framer editor: gear icon (top-right of the editor) > Site settings.
On the General tab, scroll to Custom Code. Click Show Advanced.
A new field labeled "Start of <head> tag" now appears. Without clicking Show Advanced, you only see "Body end" (wrong slot for click capture — Rekomi needs <head>).
Paste the head script
In the "Start of <head> tag" field:
<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>Your program ID is in the Rekomi dashboard at Settings > Tracking.
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.
Framer's billing model
Framer's native paid sites feature is a Merchant of Record (Framer collects payment, remits to you). If you sell directly via Framer's paid sites, there is no merchant Stripe account to attribute conversions through, so the standard Stripe-webhook attribution rail does not apply.
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.
If you DO sell directly via Framer paid sites, you'll need to fire convert from your own backend listening to Framer's purchase webhook (if/when they expose one).
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
"Show Advanced" disclosure hides the head slot. This is the single most common install miss. If you don't see "Start of <head> tag" in Custom Code, you didn't click Show Advanced.
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 Free does not ship any custom code blocks to production, regardless of how many times you Publish. Upgrade to Mini or higher.
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 native CMS data tokens for convert. If you start selling via Framer's native paid sites and need to fire convert from a Framer template, you have no Liquid-style tokens for order data. You'd have to either parse from the DOM or relay from a server-side webhook.
Troubleshooting
Published the site but Rekomi script does not appear in View Source. Three things: confirm "Show Advanced" was clicked and the script is in "Start of <head> tag" (not Body end); confirm you clicked Publish after Save; confirm your plan is Mini or higher.
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 main framer.app preview does not. Framer's preview at your-site.framer.app may not include all Site settings until you publish. Test on the custom domain after Publish for the most accurate read.
Related
- JavaScript pixel reference
- Install on Stripe — for Stripe Payment Links + MutationObserver pattern when selling via Framer-hosted marketing pages
Install on Webflow
Site settings Head code for the global install. Then either Webflow Ecommerce Order Confirmation snippet, or Stripe Payment Links MutationObserver for external checkouts.
Install on Squarespace
Code Injection greater-than Header on the Business plan or higher. Squarespace Commerce runs on your own Stripe so attribution works automatically once the head script is in place.