Google Ads Common Issues

Most issues with Google Ads data in Fibbler come down to the Leadfeeder tracking script not being installed correctly. Below are the most common problems and how to fix them.

Leadfeeder Tracking Script

The Leadfeeder tracking script is a small JavaScript snippet that you add to your website. It loads asynchronously, meaning it does not block or slow down your page load speed. The script is served via AWS CloudFront with global edge locations for fast loading.

I'm not seeing any Google Ads data

If you're not seeing any company data from Google Ads, check the following:

Is the tracking script installed? Go to your website and check the page source (right-click > View Page Source) to verify the Leadfeeder script is present. You can find your unique script on the Visitor Tracking Script card on Data sources.
Is it on the right pages? The script needs to be on the pages where Google Ads traffic lands. If you use a tag manager, make sure the trigger fires on all relevant pages, not just the homepage.
Is your CRM connected? Google Ads features require a CRM (HubSpot, Salesforce, Attio, or Pipedrive) to be connected for attribution data.
Give it time. After installing the script, data typically starts appearing within 24 hours. Full functionality may require up to 48 hours.

The script won't verify, or I see no data after 24 hours

Verification is manual. On the Visitor Tracking Script card on Data sources, click Continue setup, then I've added the script and Verify installation. When it works, the card's badge changes from Setup required to Active (or the days left on your trial). If verification keeps saying the script isn't detected, or you have confirmed the script is on your site (see above) but see no data after 24 hours, contact support@fibbler.co and we will investigate.

The tracking card says "Script not reporting"

This means the script was installed and verified before, but it has stopped sending visits. Until it's back, your Google Ads reports stay empty. It usually happens when the script was removed in a website change, or when a cookie banner stops it from running. Check that it's still on the pages your ads point to. You can open the card and click View tracking script to copy it again. If the script is there and the badge doesn't go away, email support@fibbler.co.

Tracking script blocked by Content Security Policy (CSP)

Some websites run a Content Security Policy that blocks unknown scripts. If your CSP is blocking the Leadfeeder tracker, you'll need to allowlist the tracker domain in your CSP configuration. Check your browser's developer console (F12 > Console) for CSP-related errors.

Look for errors like "Refused to load the script because it violates the Content Security Policy" in your browser console. This is a clear sign you need to update your CSP.

Installing via Google Tag Manager

If you're using Google Tag Manager (GTM) to install the script, make sure:

The tag is set to fire on All Pages (or at least all pages where Google Ads traffic can land).
The tag has been published, not just saved. Changes in GTM don't go live until you submit and publish the container.
Use GTM's Preview mode to verify the tag fires correctly on your landing pages.

The Leadfeeder tracker is designed to work in consent-aware mode with cookie management platforms (CMPs). It does not use third-party cookies and relies on first-party data collection methods. Even without explicit consent, the tracker can still identify companies while maintaining GDPR compliance, since the core output is company-level data which is not considered personal data.

Data & Identification Issues

Low number of identified companies

Not all website visitors can be identified as companies. The identification rate depends on factors like:

Traffic type: B2B traffic from corporate networks has higher identification rates than traffic from remote workers on residential ISPs.
Script placement: Make sure the tracking script loads on the actual landing page, not just after a redirect.

Data is delayed

Once the tracking script is live, Leadfeeder starts recording visits within minutes. However, company identification and enrichment can take up to 24 hours. If you've just installed the script, give it a full day before troubleshooting further.

An ad account says it was switched off because Fibbler lost access

If Google starts refusing Fibbler access to one of your ad accounts, the nightly sync switches that account off rather than failing the whole run. On Data Sources, under Google Ads, the account stays in the list with a note saying Switched off on <date> because Fibbler lost access to this ad account. That date is the day the data stopped, which is usually what you need to know when a chart has a flat tail.

This normally happens when the Google user Fibbler is connected as loses access to that ad account in Google Ads, for example when someone leaves or permissions are tidied up. To fix it:

Give the connected Google user access to the ad account again in Google Ads, or reconnect Google Ads from Data Sources signed in as a user who has it.
Tick the ad account on Data Sources and save. The note disappears and syncing starts again from the next nightly run.

Nothing is deleted while an account is switched off, so the history you already had is still there. The period Fibbler had no access for stays empty until it is filled in again, which is not part of the normal nightly run. Email support@fibbler.co with the dates if you need that gap closed.

Subscription & Access

I can't access Google Ads features

Google Ads is an add-on to your existing Fibbler subscription. To access it, you need:

An active Fibbler subscription (Growth, Unlimited, or Agency plan). Google Ads is not available during your LinkedIn Ads free trial.
LinkedIn Ads connected to Fibbler.
A CRM connected to Fibbler (HubSpot, Salesforce, Attio, or Pipedrive).
Either a trial that is still running or the Google Ads add-on. Your 14-day trial starts once Google Ads is connected and the tracking script is verified, and you buy the add-on on the Upgrade page.

See Pricing & Trial for more details.

Still need help?

If you're still experiencing issues, reach out to us at support@fibbler.coand we'll help you get it sorted.