🧩 Understanding the Four Stages of OTTO Pixel Detection

Seeing the OTTO Pixel snippet in your page source is only the first step. The Search Atlas dashboard confirms detection only after completing four distinct stages. Each stage can fail independently, which is why confirming one stage does not guarantee the next will succeed.

1. Installation — The pixel code is present in your website HTML.
2. Firing — The code executes when a browser loads the page.
3. Data Transmission — The fired pixel sends a request to Search Atlas servers.
4. Dashboard Detection — The Search Atlas UI reflects the received data and marks the pixel as active.

IP whitelisting and code visibility in page source only address Stage 1. If your dashboard still shows the pixel as undetected after more than 30 minutes, the issue almost certainly lies in Stage 2, 3, or 4.

⏱️ Expected Detection Timeline

Once the pixel fires and data reaches Search Atlas servers, the dashboard should update within 5 to 30 minutes. If more than 30 minutes have passed since a real browser visited your page with the snippet present, use the verification steps below to diagnose where the process is stalling.

🔎 How to Verify Each Stage

✅ Stage 1 — Confirm Installation

Open your browser, navigate to your website, right-click anywhere on the page, and select View Page Source. Search for OTTO or the snippet ID provided in your Search Atlas account. If the code appears, Stage 1 is complete.

⚡ Stage 2 — Confirm the Pixel Is Firing

A pixel present in HTML does not automatically mean it executes. Rendering issues, JavaScript errors, or tag manager conflicts can block execution. To verify firing:

1. Open your website in a browser.
2. Press F12 (or right-click and select Inspect) to open DevTools.
3. Click the Console tab and look for any JavaScript errors. Errors appearing before the pixel code loads may prevent execution.
4. Reload the page while DevTools is open to capture all activity from the start.

If you see JavaScript errors unrelated to OTTO, resolve those first, as they can interrupt all scripts that load after them.

📡 Stage 3 — Confirm Data Transmission to Search Atlas

This is the most common hidden failure point. Even if the pixel fires, a browser extension, firewall, Content Security Policy (CSP) header, or ad blocker can silently block the outbound request before it reaches Search Atlas servers.

1. Open your website in a browser with no extensions enabled (use an Incognito window and disable all extensions, or use a fresh browser profile).
2. Open DevTools and click the Network tab.
3. In the filter bar, type searchatlas to filter relevant requests.
4. Reload the page.
5. Look for an outbound request to a Search Atlas endpoint (the URL will contain searchatlas.com). A status code of 200 confirms the request succeeded.

If no request appears, the pixel is either not firing (return to Stage 2) or an external factor is blocking the outbound call. Common blockers include:

• Ad blockers or privacy extensions — test in a clean browser profile.
• Content Security Policy (CSP) headers — ask your developer to check whether your site's CSP restricts outbound requests to external domains.
• Firewall or proxy rules — ensure your hosting environment permits outbound requests to Search Atlas servers.
• Caching plugins or CDN rules — some configurations serve cached HTML without executing scripts. Purge your cache and retest.

If a request appears but returns a 4xx or 5xx status code, note the exact code and contact support using the instructions at the bottom of this article.

📊 Stage 4 — Confirm Dashboard Detection

Once Stage 3 is verified, allow up to 30 minutes for the Search Atlas dashboard to update. To check detection status:

1. Log in to Search Atlas and go to OTTO SEO → All Sites (SEO Automation) from the left sidebar (URL: /seo-automation-v3).
2. Locate your OTTO project and open its settings.
3. Review the pixel status indicator. If Stage 3 confirmed a successful request but the dashboard still shows undetected after 30 minutes, proceed to the next section.

🛠️ Additional Checks if All Stages Appear Correct

• Correct snippet placed on the correct domain — verify the snippet in your Search Atlas account matches the domain you are testing. Snippets are domain-specific.
• Pixel placed inside the correct HTML tag — the OTTO Pixel snippet should be placed inside the tag of your page, not inside a conditional comment or a template section that only loads for logged-in users.
• Testing with a real browser visit — search engine crawlers and synthetic monitoring tools do not trigger pixel firing. Use an actual browser session.
• Cookie consent or consent management platform (CMP) — if your site uses a cookie consent banner, the pixel may be configured to fire only after a user accepts tracking. Test by accepting all cookies and reloading.

📋 Quick Checklist Before Contacting Support

• Pixel code is visible in page source on the correct domain.
• No JavaScript errors appear in the DevTools Console on page load.
• A Network request to a searchatlas.com endpoint returns a 200 status code in a clean browser profile with no extensions.
• Cache has been purged and the page retested.
• More than 30 minutes have passed since confirming a successful Network request.

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.