🧩 Overview
If your OTTO pixel appears to be correctly installed on your Website Studio site but verification keeps failing, the most common cause is a UUID mismatch. This means the pixel snippet installed on your site contains a different unique identifier than the one associated with your current Search Atlas project. Even a single character difference will cause verification to fail every time.
This article explains how to identify whether a UUID mismatch is the cause, and how to fix it quickly.
🚨 Symptoms of a UUID Mismatch
- Pixel verification fails repeatedly despite following all installation steps correctly.
- The OTTO pixel script is visible in your site's code, but Search Atlas does not confirm a successful connection.
- You may have previously connected a different project or reinstalled OTTO at some point.
- Verification fails immediately after clicking the verify button, with no change in status.
🔎 What Is a UUID and Why Does It Matter?
A UUID (Universally Unique Identifier) is a unique code embedded inside your OTTO pixel snippet. Search Atlas uses this code to match the installed pixel to your specific project. If the UUID in your installed snippet belongs to a different project — or an older version of the same project — Search Atlas cannot verify ownership, and the connection will fail.
This mismatch commonly happens when a pixel snippet is copied from a previous project, reused across multiple sites, or pulled from a cached or outdated source.
🛠️ Step 1: Locate Your Correct UUID in Search Atlas
- Log in to your Search Atlas account.
- Open the specific project associated with your Website Studio site.
- Find the OTTO pixel snippet provided for that project.
- Copy the full pixel snippet — this contains your project's correct, current UUID.
Important: Always copy the snippet directly from the project you are trying to connect. Do not reuse snippets from other projects or from previous installations.
🔍 Step 2: Check the UUID Currently Installed on Your Site
- Access your website's code or the page where the OTTO pixel snippet is installed.
- Find the currently installed OTTO pixel snippet.
- Identify the UUID within the snippet — it is a long alphanumeric string, typically appearing as a parameter value (for example: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
- Compare this UUID character by character with the UUID in the snippet you copied from your Search Atlas project in Step 1.
If the two UUIDs do not match exactly, you have identified the root cause of your verification failure.
✅ Step 3: Replace the Mismatched Snippet and Re-Verify
- Remove the existing OTTO pixel snippet from your site.
- Paste the correct snippet (copied in Step 1) in its place.
- Save and publish your changes so the updated snippet is live on your site.
- Return to your Search Atlas project and click the verify button to re-check the connection.
- Confirmation should appear shortly if the UUIDs now match.
If verification still fails after confirming the UUIDs match exactly, double-check that the updated snippet is fully published and live on your site, then wait a few minutes and try verifying again.
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.