Skip to main content

🟒 Learn how to inspect and validate the Search Atlas OTTO pixel manually

Fix visibility, domain, or script issues on customer websites

Camilo Aponte avatar
Written by Camilo Aponte
Updated over a week ago

In this guide, you’ll learn how to manually inspect and validate the Search Atlas pixel installation, and troubleshoot common issues reported in diagnostics.

🌟 Why it matters

An incorrectly installed pixel can block pageviews, conversions, or dynamic optimization features. Validating the install ensures reliable performance and accurate reporting.

πŸ› οΈ How to do it

  1. Run a diagnostic scan in the customer dashboard. This checks for presence, visibility, and script consistency.

  2. Open the website in Incognito mode.

  3. Use Developer Tools (right-click > Inspect > Elements).

  4. Search for the Pixel UUID (use CMD+F or CTRL+F). This helps locate the script block or embedded tag.

  5. Confirm presence of both scripts:

    • One in Base64 (core logic)

    • One visible pixel with inline params

  6. Inspect attributes in the script tag:

    • id="sa-dynamic-optimization"

    • data uuid, src

    • Presence of flags like no-wp-rocket, nitro-exclude

  7. Verify correct src path in the script tag.

    • Especially for white-label clients, make sure the URL matches the assigned subdomain.

  8. Compare all data with what is displayed on the dashboard.

Look for discrepancies in attributes, structure, or values.

⚠️ Common mistakes to avoid

❌ Searching in the wrong part of the DOM (pixel may appear in <body>)

❌ Overlooking missing attributes

❌ Ignoring domain mismatches for white-label accounts

❌ Assuming diagnostic scans validate firing (they don’t)

πŸ’‘ Pro Tip

For sites using Nitro, WP Rocket, or caching plugins, double-check for suppression attributes like no-wp-rocket. These prevent script delays or removals.

βœ… Once done

The pixel should be traceable, structurally accurate, and the diagnostic alert should clear. Tracking and optimization should resume normally.

πŸ“š Useful Official Resources
​


​

Did this answer your question?