## **🔍 Overview**

Two separate but related issues can block your OTTO setup: the pixel verification tool reporting a false negative (showing the pixel as missing even though it is correctly installed), and the Google Ads account failing to connect inside Campaign Hub. This article explains why each issue occurs and walks you through the steps to resolve both.

## **⚠️ Understanding OTTO Pixel False Negatives**

A **false negative** means the OTTO pixel scanner reports that your pixel is not detected, even though you have installed it correctly. This is typically caused by one or more of the following:

- **Third-party script collision:** Another script on your site shares a similar `src` attribute path, causing the scanner to misidentify the pixel's origin domain.
- **GTM caching:** Google Tag Manager caches container snapshots. If the pixel was recently added to GTM, the cached version may not yet include it, so the scanner reads an outdated snapshot.
- **WAF or CDN blocking:** A Web Application Firewall (WAF) or content delivery network (CDN) may block the verification request before the scanner can read the pixel response.
- **Direct install mislabelled as GTM:** The diagnostic tool may incorrectly classify a direct (hard-coded) pixel installation as a GTM-managed install, which can trigger a domain-mismatch warning.

## **🛠️ Steps to Resolve Pixel False Negatives**

1. Navigate to **Left sidebar → OTTO SEO → SEO Automation** (URL: `/seo-automation-v3`) and open the site showing a pixel error.
2. Confirm the pixel snippet is placed in the `<head>` section of every page, either hard-coded directly in your theme or published through GTM.
3. If you are using **GTM**, publish a new container version to force a cache refresh, then wait 5–10 minutes before re-running verification.
4. Temporarily **disable your WAF or CDN caching rules** for your domain (or whitelist the Search Atlas verification user-agent), then re-run the pixel check.
5. If you installed the pixel directly (not through GTM), ensure no other third-party scripts on the page use a `src` URL that contains a similar path or domain fragment to the OTTO pixel URL, as this can cause a source collision.
6. After making changes, return to **Left sidebar → OTTO SEO → SEO Automation (All Sites)**, select your site, and trigger a fresh verification scan. Allow up to 15 minutes for the two-tier scanner to complete both its primary and fallback checks.

## **📊 Understanding Google Ads Account Sync Failures in Campaign Hub**

If you cannot connect your Google Ads account inside Campaign Hub, the most common reasons are:

- **Incorrect Google account permissions:** The Google account used to authorise the connection must have at least **Standard access** to the Google Ads account you want to link.
- **OAuth consent not completed:** The authorisation flow was interrupted or the required permissions were not accepted.
- **Multiple Google accounts logged in:** Browser sessions with multiple Google accounts can cause the wrong account to be authorised.
- **Terminology mismatch:** Campaign Hub uses the term **"Connect Account"** rather than "Install Pixel." If you see a banner or button referencing pixel installation in the Reports tab, this is a display label and does not affect Google Ads connectivity — proceed with the account connection flow regardless.

## **🔗 Steps to Resolve Google Ads Connection Failures**

1. Before starting, sign out of all Google accounts in your browser and sign back in using only the Google account that has **Standard or Admin access** to your Google Ads account.
2. Inside Search Atlas, go to **Campaign Hub** and select the option to connect a Google Ads account.
3. Complete the full OAuth flow — accept all requested permissions when prompted by Google. Do not close the pop-up window before it confirms success.
4. If the connection still fails, try using an **incognito or private browser window** to eliminate cached session conflicts, then repeat the OAuth flow.
5. Verify that the Google Ads account you are connecting is **active and not suspended** in the Google Ads dashboard before attempting to link it again.
6. After a successful connection, refresh Campaign Hub and confirm your account appears under connected accounts.

## **✅ Quick Checklist**

- Pixel is in the `<head>` on all pages and matches the correct domain
- GTM container published after pixel was added
- WAF/CDN not blocking the verification request
- No conflicting third-party scripts with similar `src` paths
- Single Google account with Standard access used for OAuth
- Full OAuth consent accepted without interruption
- Google Ads account is active (not suspended)

## **💬 Still Need Help?**

If you have followed all steps above and are still experiencing a false negative or a Google Ads sync failure, our team can review your specific site configuration and account logs. 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.