Search Atlas Help Center

🛠️ Fix OTTO Pixel Detection and Google Analytics Issues

Open in
View as Markdown Open in ChatGPT Open in Claude
Camilo Aponte

Camilo Aponte

Last updated on Sep 30, 2026

🔍 Overview

Two of the most common setup issues in Search Atlas involve the OTTO Pixel not being detected on your site and Google Analytics properties failing to appear or connect. This article walks you through the most likely causes and how to fix them.

⚙️ Why the OTTO Pixel May Not Be Detected

The OTTO Pixel can fire correctly and even appear in your page source without being successfully detected by Search Atlas. This is usually caused by one of the following reasons:

  • Pixel placed inside an iFrame or shadow DOM: Search Atlas scans the top-level document. If your pixel is injected inside an iFrame or a shadow DOM component, the detection crawler cannot read it.
  • Pixel loading after a JavaScript delay: If the pixel fires only after a user interaction or a delayed script execution, the detection tool may scan the page before the pixel renders.
  • Cookie consent blocking the pixel: A cookie consent or consent management platform (CMP) may be preventing the pixel from loading for users who have not accepted tracking, including automated crawlers.
  • Caching layer serving a stale page: Your CDN or server cache may be serving an older version of the page that does not yet include the pixel code.
  • Incorrect placement in the HTML: The pixel must be placed inside the tag of every page you want tracked, not in the footer or conditionally loaded only on certain pages.

✅ How to Fix OTTO Pixel Detection

  1. Open your site's source code and confirm the pixel snippet is placed inside the tag, directly in the HTML and not inside a script loader or tag manager container that delays execution.
  2. If you are using a tag manager such as Google Tag Manager, make sure the trigger is set to All Pages and the firing priority is high enough to load before other scripts.
  3. Check your cookie consent platform settings. Add the OTTO Pixel to the necessary or always active category so it loads without requiring user consent.
  4. Purge your CDN and server cache after making any changes, then wait a few minutes before triggering a new detection scan.
  5. In Search Atlas, go to Left sidebar → OTTO SEO → All Sites (SEO Automation) and locate your site. Click Re-detect Pixel to run a fresh scan after you have made the corrections above.

📊 Why Google Analytics Properties Are Not Showing Up

If your Google Analytics properties are missing from the Search Atlas connection screen or fail to load after authorisation, consider these common causes:

  • Wrong Google account connected: The Google account you authorised may not be the one that has access to the relevant GA4 or Universal Analytics property.
  • Insufficient permissions on the GA property: Your Google account needs at least Viewer level access to a property for it to appear in Search Atlas. Editor or Administrator access is required to write data.
  • GA4 property not yet published: A newly created GA4 property can take up to 24–48 hours to become visible through the Google API. Wait and try reconnecting later.
  • Token expired or revoked: If you recently changed your Google account password or revoked third-party app access, the existing token will be invalid and must be re-authorised.
  • Multiple Google accounts causing a conflict: Browser sessions with multiple Google accounts logged in simultaneously can cause the wrong account to be used during OAuth authorisation.

✅ How to Fix Google Analytics Connection Issues

  1. Sign out of all Google accounts in your browser, then sign back in using only the account that owns or has access to the GA property you want to connect.
  2. In Search Atlas, go to Left sidebar → OTTO SEO → All Sites (SEO Automation), open your site settings, and disconnect the existing Google Analytics integration.
  3. Navigate to Site Metrics → Site Explorer (GSC Accounts page) and click Connect GA Account to complete the OAuth flow again, making sure you select the correct Google account and grant all requested permissions.
  4. Once reconnected, confirm that the correct GA4 property appears in the dropdown. If it does not, verify that your Google account has at least Viewer access to that property inside Google Analytics under Admin → Property Access Management.
  5. If the property was created recently, wait 24–48 hours and attempt the reconnection again.

💡 Quick Checklist Before Contacting Support

  • OTTO Pixel is in the tag on all target pages
  • No cookie consent or CMP is blocking the pixel from loading
  • CDN and server cache have been cleared after pixel changes
  • Re-detect Pixel scan has been run from Left sidebar → OTTO SEO → All Sites (SEO Automation)
  • Only one Google account is active in the browser during OAuth
  • The connected Google account has sufficient permissions on the GA property
  • Newly created GA4 properties have been given 24–48 hours to propagate

🆘 Still Need Help?

If you have followed all of the steps above and are still experiencing issues, we are here to help. 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.