Installing the OTTO pixel through Google Tag Manager (GTM) is a common approach, but on proprietary or custom-built CMS platforms it can fail silently — leaving the pixel showing Not Installed even when setup appears complete. This article covers every known cause and guides you through each fix.

🧐 Why GTM Installations Fail on Proprietary CMS Platforms

Several factors specific to proprietary CMS environments can prevent the OTTO pixel from being detected:

• Unpublished GTM container: Adding a tag in GTM does not make it live until you click Publish. A saved draft never fires on your live site.
• Incorrect trigger configuration: If the tag is set to fire only on certain pages or events, it may not load on the pages Search Atlas checks during detection.
• Missing GTM code snippets: GTM requires two snippets — one inside the head section and one immediately after the opening body tag. Some proprietary CMS platforms allow only one script injection point, which breaks GTM functionality entirely.
• Content Security Policy (CSP) restrictions: Many proprietary CMS platforms enforce strict CSP headers that block third-party scripts, including the OTTO pixel delivered through GTM.
• Aggressive page caching: Cached HTML pages may not reflect GTM updates until the cache is fully cleared.
• Script stripping or sanitization: Some proprietary CMS platforms automatically remove or modify script tags injected through GTM, preventing the pixel from executing.

🛠️ Troubleshooting Steps

Work through the following checks in order until the pixel is detected:

1. Publish your GTM container. Log in to GTM, open your container, and confirm the latest version is Published — not just saved as a draft. Unpublished changes never reach your live site.
2. Check the tag trigger. In GTM, open the OTTO pixel tag and review its trigger settings. Set the trigger to All Pages so the tag fires on every page visit. Custom triggers with narrow URL conditions can cause the tag to miss the pages Search Atlas scans for detection.
3. Verify both GTM snippets are in place. Your CMS template must include the GTM script snippet inside the head section and the GTM noscript snippet immediately after the opening body tag. Open your CMS template or theme editor and confirm both snippets are present and unmodified.
4. Test with GTM Preview Mode. In GTM, click Preview, enter your site URL, and use Tag Assistant to confirm the OTTO pixel tag fires on the expected pages. If it shows as Not Fired, revisit your trigger configuration.
5. Check for CSP errors. Open your browser's developer tools (press F12, then go to the Console or Network tab) and reload your site. Look for messages containing Content Security Policy or script-src. If CSP errors appear, your server is blocking the GTM or Search Atlas script domains. Ask your developer to add those domains to your CSP allowlist.
6. Clear your CMS and CDN cache. After any GTM or template change, clear your CMS's built-in cache and, if applicable, flush your CDN cache as well. This ensures all visitors receive the updated page with the pixel firing correctly.

🔄 Alternative: Install the Pixel Directly in Your CMS

If GTM continues to be blocked or restricted by your CMS, bypass GTM entirely and install the OTTO pixel script directly into your site's HTML template. This is the most reliable method for proprietary CMS platforms and removes all GTM-related variables.

1. Go to Left sidebar → OTTO SEO → Installation Guide in Search Atlas.
2. Copy the OTTO pixel code snippet displayed on that page.
3. Paste the snippet inside the head section of your CMS's global page template or theme file. Look for a setting labeled Header Scripts, Custom Code, or Theme Editor in your CMS admin panel — the exact location varies by platform.
4. Save and publish the template change, then clear your CMS cache.

✅ Confirm the Pixel Is Detected in Search Atlas

After completing any of the steps above, verify that Search Atlas has picked up the pixel:

1. Go to Left sidebar → OTTO SEO → All Sites.
2. Locate your project card and check the pixel status indicator.
3. If the status still shows Not Installed, wait up to 10 minutes and refresh the page — pixel detection runs on a short delay after the script first loads on your site.
4. For a full installation status overview, go to Left sidebar → OTTO SEO → Installation Guide, which displays real-time detection results for all your connected sites.

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.