# **🔍 Overview**

When the OTTO Pixel script is installed on a GoHighLevel (GHL) website, some customers notice that the mobile navigation bar disappears or stops working on the homepage. This happens because GoHighLevel's script loader can execute the OTTO Pixel asynchronously in a way that interferes with the page's navigation rendering.

The fix is straightforward: adding the **data-cfasync** attribute to the OTTO Pixel script tag tells the page to handle the script correctly and prevents it from blocking or disrupting mobile navigation elements.

# **⚙️ Why This Happens**

GoHighLevel uses Cloudflare Rocket Loader to optimise page performance. Rocket Loader defers JavaScript execution to speed up load times. However, when it processes the OTTO Pixel script without proper instructions, it can interfere with scripts that control navigation menus — particularly on mobile viewports.

Adding **data-cfasync="false"** to the OTTO Pixel script tag tells Cloudflare's Rocket Loader to skip deferring that specific script. This ensures the pixel fires correctly without disrupting other page elements like the navigation bar.

# **🚀 How to Fix the Issue**

1. Log in to your **GoHighLevel** account and open the website or funnel where the OTTO Pixel is installed.
2. Navigate to the page settings or the custom code/header script section where your OTTO Pixel script tag is currently placed.
3. Locate the existing OTTO Pixel **<script>** tag. It will look similar to this:  
   ​

**Before (original script tag):**

<script src="https://your-otto-pixel-url.js"></script>

**After (corrected script tag):**

<script data-cfasync="false" src="https://your-otto-pixel-url.js"></script>

1. Add **data-cfasync="false"** as an attribute directly inside the opening **<script>** tag, before the **src** attribute.
2. Save your changes and publish the page.
3. Open the page on a mobile device or use your browser's mobile preview mode to confirm the navigation bar is displaying and functioning correctly.

# **✅ Where Exactly to Place the Attribute**

The **data-cfasync="false"** attribute must be placed **inside the opening script tag** of the OTTO Pixel — not in a separate tag, not above or below it. See the correct placement below:

<script **data-cfasync="false"** src="https://your-otto-pixel-url.js"></script>

If your OTTO Pixel script is an inline script (with the JavaScript code written directly between the tags rather than loaded from a URL), place the attribute the same way in the opening tag:

<script **data-cfasync="false"**> /\* your OTTO Pixel inline code here \*/ </script>

# **📊 Verify Your OTTO Pixel Is Still Active**

After making this change, confirm that the OTTO Pixel is still tracking correctly:

- Go to **Search Atlas** and navigate to **OTTO SEO** in the left sidebar, then open **SEO Automation** inside it (or visit **/seo-automation-v3**).
- Open the OTTO SEO dashboard for your connected website.
- Check that the pixel status shows as **Active** or **Connected**.
- If the status does not update within a few minutes, hard-refresh the page and check again.

# **💡 Tips to Avoid This Issue**

- Always add **data-cfasync="false"** to the OTTO Pixel tag at the time of installation on any GoHighLevel site.
- If you manage multiple GHL sites with OTTO Pixel installed, audit each one to confirm the attribute is present.
- Test your pages on mobile after any script changes to catch navigation issues early.
- Rocket Loader is enabled by default on most Cloudflare-connected sites — this fix applies any time you see navigation disruption after adding a new script.

# **🆘 Still Seeing Issues?**

If your mobile navigation is still broken after adding the **data-cfasync="false"** attribute, or if the OTTO Pixel status is not showing as active, 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.