KATLA FOR JOOMLA
Joomla cookie consent that survives template updates.
Add Katla to Joomla with an extension that adds code to the head, a custom module, or a Google Tag Manager container, so a template update cannot remove it. The scan finds what your Joomla site and its extensions set, and writes the cookie policy from that.
Head-code extensionOr Google Tag ManagerNo template edit
a head-code extension or a custom moduleHead, all pages
1. In Katla, add your Joomla site's domain and let the first scan run. 2. Install → Widget, and copy the snippet. 3. In Joomla: a head-code extension or a custom module. 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.
Any Joomla site can add head code; no hosting plan is involvedWidget guide →
WHY JOOMLA SITES STRUGGLE WITH CONSENT
A Joomla site collects cookies from everything added to it.
THE PROBLEMExtensions and templates add scripts that 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 PROBLEMAdding code to the head usually means editing the template, and the next template update loses it.
WITH KATLAKatla is one snippet, so it fits a head-code extension or a custom module and survives template updates.
THE PROBLEMScripts added by extensions 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. 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 a head-code extension or a custom module, in the head, for all pages, above any analytics code.
- Tag Manager: nothing to pasteIf your Joomla 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 Joomla. 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 Joomla; it then checks the live page for cookies set before consent.
BUILT FOR JOOMLA
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 Joomla 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 Joomla teams ask
- Is there a Katla app for Joomla?
- No, and none is needed. Katla runs on Joomla 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 Joomla sets itself?
- The scan lists them. Cookies Joomla 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 Joomla'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 Joomla, and checks the live page once you have published.
- Is there a Katla extension for Joomla?
- No. Any extension that adds code to the head of every page will do, or a custom module assigned to all pages. Keep the snippet ahead of other scripts so the guard starts first.
- Can I edit the template instead?
- You can put the snippet in the template’s head, but a template update may overwrite it. An extension or a module keeps it separate from the template.
Scan your Joomla site, then add one snippet.
The free plan scans your Joomla site and generates a cookie policy, without a card.