KATLA FOR KAJABI
Kajabi cookie consent, from one header page script.
Add Katla to Kajabi as a header page script, which Kajabi places in the head of every page, or from a Google Tag Manager container. The scan finds what your Kajabi site and its embeds set, and writes the cookie policy from that.
Header page scriptsOr Google Tag ManagerNo Kajabi app to install
Settings → Site details → Page scripts → Header page scriptsHead, all pages
1. In Katla, add your Kajabi site's domain and let the first scan run. 2. Install → Widget, and copy the snippet. 3. In Kajabi: Settings → Site details → Page scripts → Header page scripts. 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.
Header page scripts do not load on Offer checkout and upsell pagesWidget guide →
WHY KAJABI SITES STRUGGLE WITH CONSENT
A Kajabi site collects cookies from everything added to it.
THE PROBLEMVideo players, forms and embeds on a Kajabi 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 PROBLEMPixels added for course launches run 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. Tracking code of your own can wait for consent with data-katla-category.
THE PROBLEMA heavy banner slows the sales pages that a launch depends on.
WITH KATLAKatla's banner is 18 KB in one request, served from a CDN and cached at the edge.
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 Settings → Site details → Page scripts → Header page scripts, in the head, for all pages, above any analytics code.
- Tag Manager: nothing to pasteIf your Kajabi site already loads a Google Tag Manager container, connect Google in Katla and it writes its own tag there, on the Consent Initialization trigger.
- Publish and checkOpen the published site in a private window and make a choice. It shows up in your Katla dashboard within a minute.
- 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 Kajabi; it then checks the live page for cookies set before consent.
BUILT FOR KAJABI
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 Kajabi 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 Kajabi teams ask
- Is there a Katla app for Kajabi?
- No, and none is needed. Katla runs on Kajabi as one snippet in the site-wide head code or from a Google Tag Manager container.
- Does Katla block the cookies Kajabi sets itself?
- The scan lists them. Cookies Kajabi 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 Kajabi'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 Kajabi, and checks the live page once you have published.
- Does the banner show on checkout pages?
- No. Kajabi does not add header page scripts to Offer checkout and upsell pages, so the banner does not load there. Kajabi has a separate checkout tracking code setting for those pages.
- Where in Kajabi does the snippet go?
- Settings → Site details, then the Header page scripts field under Page scripts. Kajabi includes it in the head of every page except checkout and upsell pages.
Scan your Kajabi site, then paste one snippet.
The free plan scans your Kajabi site and generates a cookie policy, without a card.