Solved: Google Ads “AI Advisor Chat” tool making the UI unbearably slow – any way to turn it off?

#devops #programming #tutorial #cloud

🚀 Executive Summary

TL;DR: The Google Ads “AI Advisor Chat” tool is causing significant UI slowdowns and high resource consumption. Users can mitigate this by implementing browser-level content blocking with tools like uBlock Origin, utilizing dedicated browser profiles for isolation, or employing network-level blocking via DNS filters or corporate firewalls to prevent the chat’s scripts from loading.

🎯 Key Takeaways

Browser-level content blockers like uBlock Origin can be configured with custom CSS selectors (e.g., ads.google.com##.ai-advisor-chat-widget) and network filter rules (e.g., ||ai-advisor.google.com^$script) to prevent the Google Ads AI Advisor Chat widget and its scripts from loading.
Creating dedicated browser profiles (e.g., in Chrome) or using container extensions (e.g., Firefox Multi-Account Containers) provides an isolated, minimal environment for Google Ads, reducing general browser overhead and conflicts with other extensions.
Network-level blocking, using tools like Pi-hole for DNS filtering or corporate firewalls, can centrally prevent connections to the AI Advisor Chat’s backend services by blacklisting specific domains (e.g., ai-advisor-service.google.com), requiring precise domain identification to avoid over-blocking.

The new Google Ads “AI Advisor Chat” tool is causing significant UI slowdowns, impacting productivity for many advertisers. This post details how to mitigate or potentially disable the resource-intensive AI chat feature to restore optimal Google Ads interface performance.

Addressing Google Ads UI Slowness Caused by the AI Advisor Chat

Google Ads is a critical platform for digital advertisers, but recent additions, particularly the “AI Advisor Chat” tool, have been reported to drastically degrade user interface performance. This article outlines several practical, problem-solving approaches for IT professionals and power users to alleviate the slowness and regain control over their Google Ads experience.

The Problem: Google Ads AI Advisor Chat and UI Performance

Many users are experiencing a noticeable decline in Google Ads UI responsiveness since the introduction of the AI Advisor Chat. This tool, while intended to assist with campaign management, appears to consume substantial browser resources, leading to a sluggish, unresponsive, and often frustrating user experience. For agencies managing multiple accounts or individuals performing complex optimizations, this performance hit translates directly into lost productivity and increased operational costs.

Symptoms of a Slow Google Ads UI

Extended Page Load Times: Navigating between sections or loading campaign data takes significantly longer than usual.
Laggy Interactions: Delayed response to clicks, typing, and hovering over elements.
High Resource Consumption: The browser tab for Google Ads shows elevated CPU and RAM usage, often peaking when the AI chat component is active or attempting to load.
Browser Unresponsiveness/Freezes: The entire browser or specific Google Ads tabs may freeze or become unresponsive for short periods.
Overall System Sluggishness: In extreme cases, the browser’s resource drain can impact the performance of the entire workstation.

Solution 1: Browser-Level Content Blocking (Ad Blockers/Content Filters)

This approach involves using browser extensions designed to block unwanted content, scripts, or network requests. The goal is to prevent the AI Advisor Chat widget and its associated scripts from loading or executing, thereby freeing up browser resources.

How to Implement (Example: uBlock Origin)

uBlock Origin is a powerful and efficient content blocker. Here’s how you might configure it:

Install uBlock Origin: Add the extension to your preferred browser (Chrome, Firefox, Edge, etc.).
Inspect the Google Ads Page:
- Open Google Ads and navigate to a page where the AI Advisor Chat is visible.
- Right-click on the chat widget or near it and select “Inspect” (or “Inspect Element”).
- Look for unique CSS classes or IDs associated with the chat widget in the HTML structure. Common patterns might include .ai-advisor-chat, #advisor-widget, or similar.
- Switch to the “Network” tab in the developer tools. Reload the page and look for requests that contain terms like “advisor,” “chat,” or “ai” originating from Google domains. Note down any suspicious URLs or domains.
Add Custom Filters in uBlock Origin:
- Click on the uBlock Origin icon in your browser toolbar.
- Click on the “Open the dashboard” icon (usually three gears).
- Go to the “My filters” tab.
- Add your custom filter rules based on your inspection.

Example Filter Rules (Hypothetical, requires user verification):

# Block the chat widget element directly (CSS rule)
ads.google.com##.ai-advisor-chat-widget
ads.google.com##div[aria-label*="AI Advisor"]
ads.google.com##[data-test-id="advisor-chat-container"]

# Block specific scripts or network requests associated with the chat
||ai-advisor.google.com^$script,domain=ads.google.com
||chat-advisor-service.google.com^$xhr,domain=ads.google.com

Explanation:
- ads.google.com##.ai-advisor-chat-widget: This rule attempts to hide or remove HTML elements with the class ai-advisor-chat-widget on ads.google.com. You’ll need to find the exact class name.
- ads.google.com##div[aria-label*="AI Advisor"]: A more generic rule to hide a div containing “AI Advisor” in its aria-label attribute.
- ||ai-advisor.google.com^$script,domain=ads.google.com: This rule blocks any script requests to the hypothetical domain ai-advisor.google.com when browsing ads.google.com.
Test and Refine: After adding rules, clear your browser cache and refresh Google Ads. If the chat widget disappears and performance improves, you’ve succeeded. If not, refine your rules by re-inspecting. Be cautious not to block essential Google Ads functionality.

Comparison: Browser-Level Content Blocking


Pros	Cons
* Individual user control, no admin rights needed. * Highly granular, can target specific elements/requests. * Effective for blocking client-side resource hogs. * Quick to implement and test.	* Requires identifying correct blocking rules (trial and error). * May break other Google Ads functionality if rules are too broad. * Solution is per-browser/per-user; no centralized management. * Google may change selectors/domains, requiring rule updates.

Solution 2: Browser Profile Management and Clean Slate

Sometimes, the issue isn’t just the AI chat, but a combination of it with other browser extensions, cached data, or a cluttered profile. Creating a dedicated, minimal browser profile for Google Ads can provide an isolated, optimized environment.

How to Implement (Example: Google Chrome Profiles)

Create a New Chrome Profile:
- Click on your profile icon (top right, next to the address bar).
- Click “Add” or “Manage profiles” and then “Add profile”.
- Give it a descriptive name like “Google Ads Work” and choose an avatar.
Log In to Google Ads: Open the new profile, navigate to Google Ads, and log in.
Install Only Essential Extensions (Optional): If you require extensions like a password manager, install only those critical ones. Avoid unnecessary add-ons that could interfere. You might even consider installing uBlock Origin here with specific rules from Solution 1 if the problem persists.
Maintain Separation: Use this profile exclusively for Google Ads or related work, keeping it clean from general browsing history and other extensions.

How to Implement (Example: Firefox Multi-Account Containers)

Firefox’s Multi-Account Containers extension offers a similar isolation mechanism without needing separate full browser profiles.

Install Firefox Multi-Account Containers: Add the extension to Firefox.
Create a New Container:
- Click the Containers icon in the toolbar.
- Click “Manage Containers” and then “New Container.”
- Name it “Google Ads” and choose a color/icon.
Open Google Ads in the Container:
- Right-click on any link to Google Ads or click the Containers icon.
- Select “Open Google Ads in ‘Google Ads’ container.”
- You can also configure “Always Open in…” settings for ads.google.com.
Benefit: This isolates cookies, local storage, and potentially some script interactions, giving Google Ads a cleaner environment without the overhead of a full separate browser profile.

Comparison: Browser Profile/Container Management


Pros	Cons
* Creates a clean, isolated environment. * Reduces conflicts with other extensions/tabs. * Easy to set up and manage. * Improved overall browser stability for dedicated tasks.	* Doesn’t directly disable the AI chat, only mitigates general browser overhead. * Requires switching profiles/containers, which can be a minor inconvenience. * Still reliant on Google not forcing the chat to load regardless.

Solution 3: Network-Level Blocking (DNS Filtering/Firewall)

For IT professionals managing networks or dedicated workstations, blocking the AI Advisor Chat at the network level offers a more robust and centralized solution. This prevents the browser from ever connecting to the chat’s backend services.

How to Implement (Example: Pi-hole for DNS Filtering)

Pi-hole is a network-wide ad blocker that works by acting as your network’s DNS server, blocking unwanted domains.

Identify Target Domains: This is the most critical step. You need to identify the specific domains that the AI Advisor Chat uses to load its content or communicate. Use your browser’s developer tools (“Network” tab) while on Google Ads and look for suspicious domains related to “advisor,” “chat,” or “AI” that are not core Google Ads functions.

(Caution: Blocking a generic domain like chat.google.com will likely break Google Chat entirely. Aim for highly specific domains if they exist, e.g., ai-advisor-service.google.com or a subdomain of ads.google.com specifically for the chat.)

Access Pi-hole Admin Interface: Log in to your Pi-hole web interface (e.g., http://pi.hole/admin).
Add Domains to Blacklist:
- Navigate to “Blacklist” under the “Tools” section.
- Enter the identified domains (e.g., ai-advisor-service.google.com, advisor.ads.google.com) into the “Add domain” field.
- Click “Add to Blacklist.”
Verify: Clear your browser’s DNS cache and browser cache. Reload Google Ads. The chat should fail to load or disappear entirely.

How to Implement (Example: Corporate Firewall Rules)

For organizations, a corporate firewall can block these domains for all users on the network.

Identify Target Domains/IPs: As with Pi-hole, precise identification of domains or even specific IP addresses for the AI chat service is crucial. Network traffic analysis tools (e.g., Wireshark, firewall logs) might be needed.
Access Firewall Management: Log in to your organization’s firewall (e.g., pfSense, Palo Alto, Cisco ASA, FortiGate).
Create a Blocking Rule:
- Navigate to the “Security Policies,” “Firewall Rules,” or “Application Control” section.
- Create a new outbound rule.
- Source: Internal network (e.g., ANY or specific user groups).
- Destination: FQDNs (e.g., ai-advisor-service.google.com) or IP addresses identified. Some firewalls support URL filtering to block specific paths (e.g., ads.google.com/ai-advisor/chat/*).
- Action: Deny or Block.
- Log: Enable logging to monitor if the rule is triggered.
Deploy and Test: Apply the rule. Test from a client machine to confirm the chat is blocked and Google Ads functionality remains intact.

# Hypothetical Pi-hole command to add to blacklist
pihole -b ai-advisor-service.google.com
pihole -b advisor.ads.google.com

# Example Firewall Rule (Conceptual, specific syntax varies by vendor)
# This would block DNS resolution or direct access to the specified FQDN
# For FortiGate:
config firewall policy
    edit 0
        set name "Block_Google_Ads_AI_Advisor"
        set srcintf "internal"
        set dstintf "wan"
        set srcaddr "all"
        set dstaddr "all"
        set service "DNS" "HTTPS" "HTTP"
        set action deny
        set dscaddr-type fqdn
        set dst-fqdn "ai-advisor-service.google.com" "advisor.ads.google.com"
    next
end

Comparison: Network-Level Blocking


Pros	Cons
* Centralized control for multiple users/devices. * Highly effective; blocks connections before they reach the browser. * Enforces policy across the network segment. * Less susceptible to client-side bypasses or changes.	* Requires network administration privileges. * Risk of over-blocking legitimate services if domains are misidentified. * More complex to implement and maintain. * Requires precise identification of chat-related domains/IPs.

Comparison Table: Solution Approaches


Feature	Browser-Level Content Blocking	Browser Profile/Container Management	Network-Level Blocking
Ease of Implementation	Moderate (requires research for specific rules)	Easy	High (requires network admin skills & domain research)
Impact Scope	Single browser instance	Single browser instance/isolated environment	Network-wide (all users/devices)
Technical Proficiency	Intermediate (CSS selectors, network inspection)	Low	High (DNS, firewall rules, traffic analysis)
Risk of Side Effects	Moderate (can break features if rules are too broad)	Low (minimal impact on other browser functions)	High (can disrupt legitimate services if domains are misidentified)

Recommendations and Best Practices

Start Simple: Begin with Solution 2 (Browser Profile/Container Management) to rule out general browser clutter. If the problem persists, move to Solution 1.
Investigate Thoroughly: Before implementing any blocking rules (especially network-level), spend time in your browser’s developer tools (Network tab) to accurately identify the domains and scripts associated with the AI Advisor Chat. This is crucial for avoiding unintended side effects.
Test Incrementally: Apply rules one by one and test Google Ads thoroughly to ensure core functionality remains intact.
Monitor Performance: Use your browser’s task manager (Shift+Esc in Chrome) or performance monitor to observe CPU and RAM usage for the Google Ads tab before and after applying solutions.
Report to Google: Provide feedback to Google Ads support about the performance issues. The more data they receive, the higher the chance of an official fix or an option to disable the feature.
Keep Software Updated: Ensure your browser, content blockers, and network appliances are running the latest versions for optimal performance and security.
Regular Cache Clearing: Periodically clear your browser cache and cookies for the Google Ads domain to prevent stale data from contributing to performance issues.

By systematically applying these solutions, IT professionals and advanced users can effectively mitigate the performance degradation caused by the Google Ads AI Advisor Chat, restoring a productive and efficient environment for managing advertising campaigns.