KATLA FOR FRAMER
Framer cookie consent, from the head code or your own design.
Add Katla to Framer as custom code at the start of the head and use the hosted banner, or design the banner in Framer and run Katla headless behind it. A Google Tag Manager container works too, and the scan writes the cookie policy from what your site sets.
Start of head, every pageOr Google Tag ManagerOr a banner built in Framer
Site settings → Custom code → Start of <head> tagHead, all pages
1. In Katla, add your Framer site's domain and let the first scan run. 2. Install → Widget, and copy the snippet. 3. In Framer: Site settings → Custom code → Start of <head> tag. 4. Paste it into the head code for all pages, above any analytics or advertising code. 5. Publish, then open the site in a private window and check that the banner appears. For a banner you design yourself, load https://cdn.katla.app/YOUR-SITE-ID.js?headless=true instead: the guard and the API, no banner.
Check that your Framer plan includes custom codeWidget guide →
WHY FRAMER SITES STRUGGLE WITH CONSENT
A Framer site collects cookies from everything added to it.
THE PROBLEMAnalytics, embeds and integrations added to a Framer site set cookies of their own, and the cookie policy is a template somebody adapted once.
WITH KATLAKatla scans the published site as a visitor would, lists every cookie it finds with its vendor and purpose, and writes the cookie policy from that list.
THE PROBLEMA stock banner is the one element on a carefully designed Framer site that ignores the design.
WITH KATLALoad Katla headless, design the banner in Framer, and call KatlaConsent from its buttons. The consent logic, the guard and the records stay Katla’s.
THE PROBLEMTracking code at the start of the head runs as soon as the page loads, before any visitor has chosen.
WITH KATLAThe cookie guard refuses cookies outside the consented categories and deletes any set before it started. Scripts you add yourself can wait for consent with data-katla-category.
SETUP
Three ways in, and an assistant if you want one.
- Widget: paste one snippetCopy the snippet from Install → Widget in Katla and paste it into Site settings → Custom code → Start of <head> tag, in the head, for all pages, above any analytics code.
- Tag Manager: nothing to pasteIf your Framer site already loads a Google Tag Manager container, connect Google in Katla and it writes its own tag there, on the Consent Initialization trigger.
- Your own banner: headlessLoad Katla with headless mode on and design the banner in Framer. Its buttons call KatlaConsent.acceptAll(), rejectAll() or acceptCategories().
- Or ask your assistantConnect Claude or ChatGPT to Katla's MCP server and it adds the site, scans it and hands you the snippet. You paste it in Framer; it then checks the live page for cookies set before consent.
BUILT FOR FRAMER
What you get, whichever way you install.
Consent Mode v2Defaults and updates for GA4 and Google Ads come from the banner, so there is no gtag consent code to write or keep in step.
AI cookie scanningEvery cookie on the published Framer site, classified by category and vendor, with a description in each language you serve.
A policy that keeps upThe cookie policy embeds on any page with a short snippet, is generated from the scan, and updates itself after every scan.
A way back to the choiceA floating icon, or a link calling katla.open(), lets visitors change or withdraw their choice from any page.
Global Privacy ControlVisitors whose browser sends GPC are recorded as refusing, or as opting out under the CCPA, before the banner asks anything.
Hosted in the EUKatla runs in AWS's eu-central-1 region, in Frankfurt.
CORE WEB VITALS
That's how the cookie crumbles. Except your SEO shouldn't.
A consent banner is the first third party on every page, and builder sites already carry plenty of script. Katla's banner is 18 KB over the wire, served from a CDN and cached at the edge, and headless mode is 4 KB.
How headless mode works →18 kBOver the wireBanner and your cookie data, brotli
0 msAdded LCPAgainst the same page without it
0Layout shiftThe banner reserves no space in flow
2RequestOne script, cached at the edge
Our own measurements, taken - how they were taken.
Questions Framer teams ask
- Is there a Katla app for Framer?
- No, and none is needed. Katla runs on Framer as one snippet in the site-wide head code, from a Google Tag Manager container, or headless behind a banner you design.
- Does Katla block the cookies Framer sets itself?
- The scan lists them. Cookies Framer needs for sessions and security are necessary and stay. Any cookie the visitor has not allowed is removed when Katla starts and refused after that, but cookies set by Framer's servers rather than by scripts on the page are outside what any banner script can reach.
- Can my AI assistant install it?
- Everything except the paste. Connected to Katla's MCP server, Claude or ChatGPT adds the site, runs the scan, gives you the snippet and where it goes in Framer, and checks the live page once you have published.
- Where in Framer does the snippet go?
- Site settings → Custom code, in the "Start of <head> tag" field, so it runs before the other code on the page. Publish the site afterwards.
- How do I wire a banner designed in Framer?
- Load https://cdn.katla.app/YOUR-SITE-ID.js?headless=true at the start of the head, show your banner while KatlaConsent.hasConsent() is false, and have its buttons call KatlaConsent.acceptAll(), KatlaConsent.rejectAll() or KatlaConsent.acceptCategories() from a code override.
Scan your Framer site, then add one snippet.
The free plan scans your Framer site and generates a cookie policy, without a card.