## **🔍 What You Are Verifying**

Search Atlas may use Google Tag Manager (GTM) and a dynamic optimization script to load tracking or optimization features on your website. Verification confirms that the expected code is present, loads successfully, and is connected to the correct project.

A GTM container ID, such as **GTM-TCCS243**, identifies a Google Tag Manager container. The ID alone does not prove that the container belongs to Search Atlas. Confirm its ownership and tags in the Google Tag Manager account used for your site.

## **🛠️ Check the Website Source**

1. Open the published version of your website in a private browser window.
2. Right-click the page and select **View page source**, or use your browser’s developer tools.
3. Search for the GTM container ID, such as **GTM-TCCS243**.
4. Search for terms related to Search Atlas, OTTO, optimization, or the project’s tracking script.
5. Check several important page types, including the homepage, a service page, and a contact or conversion page.

The code may be injected through a CMS, a plugin, a tag manager, or another deployment method. It may not appear in the original HTML if it is added after the page loads.

## **📊 Check Loaded Scripts**

1. Open your browser’s developer tools and select the **Network** tab.
2. Reload the page with the developer tools open.
3. Filter requests by **js**, **gtm**, **script**, or a recognizable Search Atlas or OTTO term.
4. Open matching requests and review the request URL, status code, and initiator.
5. Confirm that the request returns successfully, normally with a 200 status, and is not blocked by the browser, consent tool, firewall, or content security policy.

Do not rely on a script name alone. Review where the script loads from and whether the request is associated with the correct website and project.

## **🏷️ Verify the GTM Container**

1. Sign in to the Google Tag Manager account that manages the website.
2. Open the container matching the ID found on the site.
3. Review the container name, account ownership, workspaces, tags, triggers, and published version.
4. Use GTM Preview mode to confirm that the expected tags fire on page load and on the relevant visitor actions.
5. Check that the container is published and that no duplicate or outdated container is also installed.

If the GTM account is managed by another agency or vendor, ask the account owner to confirm whether the container and tags were installed for Search Atlas.

## **⚙️ Confirm the Dynamic Optimization Script**

Dynamic optimization code can be loaded directly or through GTM, so its location may differ between sites. Compare the script and its request behavior with the installation details for the correct Search Atlas project. Confirm that:

- The script is installed on the intended domain.
- The project and domain are correctly matched.
- The script loads after consent requirements are met, when applicable.
- The script is not duplicated by the CMS, GTM, or another optimization tool.
- It is not being removed, modified, or blocked by caching, security, or performance tools.

## **🚨 Troubleshoot Recurring Issues**

- **Code appears only sometimes:** Test in a private window, clear site and CDN caches, and check whether a consent banner changes script loading.
- **GTM is present but tags do not fire:** Use GTM Preview mode and review triggers, blocking rules, consent settings, and the published version.
- **Requests are blocked:** Check browser console errors, security headers, firewall rules, and ad or script-blocking extensions.
- **Changes are not visible:** Confirm that the correct environment is published and purge applicable browser, plugin, and CDN caches.
- **Multiple scripts are present:** Remove duplicate installations only after confirming which deployment is active and supported.
- **Site behavior changed unexpectedly:** Temporarily document the affected URL, time, browser, and console or network error before changing code.

## **✅ Record Verification Results**

For recurring investigations, record the website URL, affected page types, GTM container ID, script or request URL, timestamp, browser, consent state, and any console or network errors. This information helps identify whether the issue is caused by installation, publishing, caching, blocking, or project configuration.

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.