KATLA FOR GOOGLE TAG MANAGER
Google Tag Manager cookie consent, without a site deploy.
Katla installs from the container you already run. Connect Google and Katla writes one tag on the Consent Initialization trigger, or paste it yourself in five steps. Consent Mode v2 signals are sent for you.
One Custom HTML tagConsent Initialization triggerConsent Mode v2
Tag Manager → Tags → NewOr one click
1. Tags → New → Custom HTML. Name it "Katla consent". 2. Paste your Katla snippet into the HTML field. 3. Triggering: Consent Initialization - All Pages. 4. Advanced settings → Tag firing priority: 100. 5. Preview, then Publish the container. Or: Install → Google Tag Manager → Install with Google, and Katla writes the same tag for you.
Katla writes this one tag and touches nothing else in the containerConsent Mode guide →
WHY GOOGLE TAG MANAGER SITES STRUGGLE WITH CONSENT
The container fires in its own order, and consent has to come first.
THE PROBLEMA consent tag on the All Pages trigger fires alongside the Google tags it is supposed to govern, so they read consent before the banner has said anything.
WITH KATLAKatla goes on the Consent Initialization trigger, which Tag Manager fires before every other trigger in the container, at firing priority 100.
THE PROBLEMConsent Mode v2 needs four signals kept in step with the banner, and hand-written gtag calls drift from it the first time a category changes.
WITH KATLAThe banner sends the update itself when a visitor chooses: analytics maps to analytics_storage, and marketing to ad_storage, ad_user_data and ad_personalization.
THE PROBLEMChanging the site means a ticket, a developer and a deploy, for a script the marketing team owns.
WITH KATLAThe install lives entirely in the container. Publish a container version and the banner is live, with nothing deployed to the site.
SETUP
From container to consent in four steps.
- Connect GoogleIn Katla, open Install, choose Google Tag Manager and sign in with the Google account that manages the container.
- Pick the containerChoose the account, container and workspace. Katla asks for Tag Manager access only, and uses it for one tag.
- Katla writes the tagOne Custom HTML tag named "Katla consent", on the Consent Initialization - All Pages trigger. Nothing else is read or changed.
- Preview and publishPublish from Katla, or leave it unpublished and review it in Preview mode first. Publishing is your choice on the last step.
BUILT FOR GOOGLE TAG MANAGER
Everything the script tag does, from the container.
Consent Mode v2Defaults and updates for GA4 and Google Ads come from the banner, so there is no gtag consent code of your own to keep in sync.
One tag, nothing elseKatla creates a single tag in the workspace you pick. Your other tags, triggers and variables are left exactly as they were.
Clean removalDisconnecting removes the Katla tag again and records the removal as its own container version, so the history says what happened.
The same cookie guardThe tag loads the same engine as the script-tag install: cookies outside the consented categories are refused, and any already set are removed when it starts.
AI cookie scanningKatla scans the site the container runs on, classifies every cookie it finds, and writes the cookie policy from that list.
Or skip the containerIf you would rather not route consent through Tag Manager, the same banner is one script tag in the head, or a headless SDK.
CORE WEB VITALS
That's how the cookie crumbles. Except your SEO shouldn't.
A consent tag loaded through Tag Manager still adds a third party to every page, which is why it shows up in the Core Web Vitals report. Katla's banner is 18 KB over the wire, served from a CDN and cached at the edge, and reserves no space in the layout.
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 Google Tag Manager teams ask
- Does it work with GA4 and Google Ads?
- Yes. Katla sends Consent Mode v2 signals, so GA4 and Google Ads tags in the container read the visitor’s choice: analytics_storage for analytics, and ad_storage, ad_user_data and ad_personalization for marketing.
- What does Katla change in my container?
- One Custom HTML tag named "Katla consent" on the Consent Initialization - All Pages trigger, in the workspace you choose. It does not read or edit your other tags, triggers or variables.
- Does Katla publish the container for me?
- Only if you ask it to on the last step. Otherwise the tag waits in the workspace, and you preview and publish it in Tag Manager yourself.
- Do I still need a cookie banner script on the site?
- No. The tag is the install: it loads the banner and the cookie guard on every page the container runs on. Do not add the script tag as well, or the banner loads twice.
- Can I install it without Google sign-in?
- Yes. Copy the snippet from the Install page and add it as a Custom HTML tag yourself, on the Consent Initialization - All Pages trigger with firing priority 100.
Connect your container, then publish.
The free plan scans your site and generates a cookie policy, without a card.