Meta Ads Common Issues

Most issues with Meta Ads data in Fibbler come down to one of two things: the URL parameters missing from your ads, or the Leadfeeder tracking script not being installed correctly. Below are the most common problems and how to fix them.

URL Parameters

I see companies, but no campaigns

This is the single most common Meta issue, and it has one cause: the utm_id parameter is missing from your ads. Fibbler can tell the visit came from Meta, but nothing tells it which campaign sent it, so ad spend, delivery and campaign names have nothing to attach to.

Open the URL parameters field on each ad in Meta Ads Manager and confirm it contains exactly this:

utm_source=facebook&utm_medium=paid&utm_id={{campaign.id}}&utm_campaign={{campaign.name}}&utm_content={{ad.id}}&utm_term={{adset.id}}
  • Set it on every ad, not just the campaign or ad set. The field lives at ad level.
  • Keep the double braces. Meta substitutes them when the ad is served. If you see the literal text {{campaign.id}} in your landing page URL, the ad was set up in a way that skipped substitution.
  • Data starts from when you added it. Only ads served after the change carry the campaign id. Earlier visits cannot be backfilled.

Parameters are set but still not arriving

Click one of your live ads and look at the URL in the address bar after the page loads. The UTM parameters should still be there. If they are gone, something on your side is dropping them:

  • A redirect is stripping the query string. Redirects from a marketing domain to the main site, or from HTTP to HTTPS, often drop query parameters unless configured to preserve them.
  • The landing page URL already has a query string and the parameters were appended in a way that produced two ? characters.
  • A consent banner reloads the page without the original query string.

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. It is the same script used for Google Ads, so if you already run that, you do not need a second one.

I'm not seeing any Meta Ads data

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

  1. Are the URL parameters on your ads? See above. This is the most common cause.
  2. 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 in Fibbler under Settings.
  3. Is it on the right pages? The script needs to be on the pages where Meta Ads traffic lands. If you use a tag manager, make sure the trigger fires on all relevant pages, not just the homepage.
  4. Is the right ad account selected? On the Sources page, check that the ad account running your campaigns is among the ones you saved. You can change the selection at any time.
  5. Is your CRM connected? Meta Ads features require a CRM (HubSpot, Salesforce, Attio, or Pipedrive) to be connected for attribution data.
  6. Give it time. After installing the script, data typically starts appearing within 24 hours. Full functionality may require up to 48 hours.

An ad account is marked "Inactive on Meta"

This label comes straight from Meta: the ad account is in a state where it cannot serve ads, usually a billing or policy problem. Fibbler will not receive spend or delivery data for it until you resolve that in Meta Ads Manager. Selecting it in Fibbler does no harm, it simply will not produce data yet.

The checkmark is not green, or I see no data after 24 hours

Verification shows as a green checkmark on the Sources page once Fibbler detects the script. If the checkmark is still not green, 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.

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 Meta 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.

Cookie consent / consent management platforms

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.
  • Mobile traffic: Meta delivers a large share of its impressions in the Facebook and Instagram mobile apps, and visitors on mobile networks are identified less often than visitors on a corporate network. Expect a lower identification rate here than on search traffic.
  • 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.

Subscription & Access

I can't access Meta Ads features

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

  • An active Fibbler subscription (Growth, Unlimited, or Agency plan). Meta Ads is not available during your LinkedIn Ads free trial.
  • A CRM connected to Fibbler (HubSpot, Salesforce, Attio, or Pipedrive).
  • The Meta Ads add-on activated in your Settings. It comes with a 14-day free trial.

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.