Search Atlas Help Center

🍞 Fix OTTO Pixel Detection Issues on Toast Websites

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

Camilo Aponte

Last updated on Sep 30, 2026

🔍 Why This Happens on Toast Websites

Toast is a closed restaurant-focused website platform with its own internal caching layer and strict script-loading rules. Standard troubleshooting steps — such as clearing your browser cache or repositioning a script tag — do not apply here. When OTTO Pixel stops being detected on a Toast website, the root cause is almost always one of the following:

  • Residual OTTO Pixel code left over from a previous install
  • Toast's internal cache serving an outdated version of your site
  • A Google Tag Manager (GTM) container conflicting with the direct pixel install

Follow the steps below in order. Skipping steps or repeating the install without completing the full removal process is the most common reason reinstallation fails.

🗑️ Step 1 — Completely Remove Existing OTTO Pixel Code from Toast

Before adding any new code, you must ensure no previous version of the OTTO Pixel remains on your Toast site.

  1. Log in to your Toast account and navigate to your website settings.
  2. Open the section where custom scripts or tracking codes are managed (sometimes labeled Header Scripts, Custom Code, or Advanced Settings).
  3. Locate every instance of OTTO Pixel code. This includes any snippet containing your OTTO tracking ID or references to the OTTO script URL.
  4. Delete all instances completely. Do not leave any partial snippets behind.
  5. Save your changes.

Important: If you installed OTTO Pixel more than once during previous troubleshooting attempts, there may be duplicate entries. Check the custom code area thoroughly before proceeding.

🏷️ Step 2 — Remove Google Tag Manager if Present

If you previously installed OTTO Pixel through a Google Tag Manager (GTM) container, or if GTM is active on your Toast site alongside a direct OTTO Pixel install, this conflict will prevent detection.

  1. Check your Toast custom code area for any GTM snippet (it will reference googletagmanager.com).
  2. If GTM is present and was used to fire the OTTO Pixel, remove the GTM container snippet from Toast entirely, or pause the OTTO Pixel tag inside GTM so it is not firing.
  3. Choose one installation method only: either a direct OTTO Pixel snippet in Toast, or via GTM — never both at the same time.
  4. Save all changes.

If you intend to use GTM as your installation method, ensure the GTM container is published with the OTTO Pixel tag active before moving to the cache-clearing step.

🧹 Step 3 — Clear Toast's Internal Cache

Toast caches your website at the platform level. Clearing your browser cache alone will not update what Toast serves to visitors or to OTTO's detection system.

  1. Inside your Toast dashboard, locate the Publish or Save & Publish option for your website.
  2. Trigger a full republish of your site. On some Toast plans this is labeled Force Refresh or Clear Cache.
  3. If you do not see a dedicated cache-clearing option, saving any minor change to your site (such as editing a word in a paragraph, then reverting it) and republishing will force Toast to regenerate your pages.
  4. Confirm the publish completed successfully before continuing.

➕ Step 4 — Reinstall the OTTO Pixel

  1. In Search Atlas, go to OTTO SEO in the left sidebar (URL: /seo-automation-v3).
  2. Locate your OTTO Pixel snippet for the relevant project.
  3. Copy the snippet in full.
  4. Return to your Toast custom code area and paste the snippet once into the correct field (typically the Header section).
  5. Save and republish your Toast site.

⏳ Step 5 — Wait 20+ Minutes Before Testing Detection

After republishing, Toast requires time to propagate changes across its network. Attempting to verify OTTO Pixel detection immediately after reinstallation is one of the most common sources of confusion — the pixel will appear undetected even when the install is correct.

  • Wait a minimum of 20 minutes after your final publish before running a detection check.
  • When you are ready to test, open your live Toast website URL in a private or incognito browser window to avoid cached responses from your own browser.
  • Return to Search Atlas and trigger the OTTO Pixel verification check from the OTTO SEO section.

✅ Quick Checklist Before Contacting Support

  • All previous OTTO Pixel code removed from Toast custom code fields
  • GTM conflict resolved — one installation method only
  • Toast internal cache cleared via a full republish
  • Fresh OTTO Pixel snippet pasted once into the Header section
  • Site republished and at least 20 minutes have passed
  • Detection tested from a private browser window on the live site URL

💬 Still Not Detected?

If you have completed every step above and OTTO Pixel is still not being detected, there may be a Toast account-level restriction or a platform update affecting script loading. 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.