--- title: "Disable container injection" date: 2026-05-04 author: "GTM Kit" --- # Disable container injection This guide explains the **Inject Container Code** toggle and the **Just the data layer** mode, and when you need them. ## When to disable container injection The default and recommended setup is: GTM Kit loads both the GTM container and the data layer. You do not need to do anything else. Disable container injection only when something else on your site is responsible for loading the GTM container. The most common cases are: - **Your CMP (consent management platform) loads GTM after consent.** Cookiebot, Cookie Information, Complianz, OneTrust, and similar tools sometimes manage the GTM script themselves so they can hold it back until consent is given. - **A cache or speed plugin manages script loading.** WP Rocket and Perfmatters can be configured to inject the snippet themselves. - **You have manually pasted the snippet into your theme** for any reason. In all of these cases, having two sources load the same container produces double-firing. Turn off injection in GTM Kit and let the other source own it. ## What stays on when you disable injection GTM Kit still pushes events to `window.dataLayer`. That is the whole point of GTM Kit. The plugin only stops emitting the `