π Overview
Some customers see a Not Installed status for OTTO even though the OTTO script (dynamic_optimization.js) loads correctly in their browser after a visitor accepts analytics cookies. This article explains why the status and your real-world results can differ, how to confirm that OTTO is working, and what to send us if you still need help.
π§© Why This Happens
The installation check works like a new visitor who has not given consent. If your cookie banner or tag manager holds back the OTTO script until a visitor accepts analytics cookies, the script is not present when the check runs. The check then reports Not Installed, even though the script loads for people who accept consent.
Common causes include:
- The OTTO script is placed in a consent category (such as Analytics or Marketing) that stays blocked until a visitor accepts.
- A tag manager trigger fires only after a consent event.
- The script is added to the page by JavaScript after consent, so it is not in the original page source.
- A cache or CDN is serving an older version of the page without the script.
- The domain being checked differs from the domain where the script is installed (for example, www versus non-www).
β How to Verify OTTO Is Working
Use these steps to confirm the script runs correctly in both the before-consent and after-consent states.
- Open your website in a private or incognito browser window so no previous consent is saved.
- Open your browser developer tools and go to the Network tab. Reload the page.
- Search for dynamic_optimization.js. Before you accept cookies, it is normal for the file not to appear if your consent setup blocks it.
- Accept analytics cookies in your banner. Reload the page if your setup requires it.
- Check the Network tab again. The file should now appear with a 200 status.
- Open the Console tab and look for red errors related to the script or your consent tool. Errors here can stop OTTO from running.
- Open the Elements view or view the page after loading and confirm that the OTTO script tag is present in the page.
If the file loads with a 200 status after consent and there are no related errors, the installation is working for consenting visitors. The Not Installed label in this case reflects what the automated check can see, not a failure of the script.
π οΈ Options to Resolve the Status
Choose the option that fits your privacy policy and legal requirements.
- Keep the script consent-gated: If your policy requires consent first, no change is needed. OTTO still works for visitors who accept. Use the verification steps above as your confirmation, and expect the status label to stay as Not Installed.
- Move the script to a category that loads without consent: If your legal team confirms OTTO can be treated as a necessary or functional script on your site, change its category in your consent tool or tag manager. The script then loads for the automated check and the status can update.
- Check the basics: Confirm the script is on the exact domain connected in your Search Atlas project, that the snippet was copied in full, and that you have cleared your site cache and CDN after any change.
Speak with your legal or privacy advisor before changing how a script is categorized. We cannot advise on consent compliance for your region.
π After Making Changes
- Save your changes in your consent tool or tag manager and publish them.
- Clear your website cache and CDN cache.
- Repeat the verification steps in a fresh incognito window.
- Return to OTTO in the platform and re-run the installation check. Allow some time for the status to refresh.
π About Data and Results
When OTTO is consent-gated, it only runs for visitors who accept. This means activity and data tied to the script reflects consenting visitors rather than all traffic. This is expected behavior and does not mean the optimizations are broken. To confirm that changes are live, open a page after accepting consent and check that the expected updates, such as titles or meta descriptions, appear.
π¬ What to Include When You Contact Support
If the status does not match what you see in your browser, send us the details below so we can review the check results and data received for your account.
- Your website domain and the exact page URL you tested.
- The name of your consent tool and whether you use a tag manager.
- The consent category the OTTO script is assigned to.
- A screenshot of the Network tab showing dynamic_optimization.js and its status after consent.
- Any red errors shown in the Console tab.
- The date and time of your test, including your time zone.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.