Meta Pixel Not Tracking Conversions

When a Meta Pixel stops tracking conversions, campaigns lose the signal Meta uses to decide who sees each ad and reports stop showing which spend produced enquiries or sales. The cause is usually one of a short list of faults, from a Pixel that no longer loads to a cookie banner that never releases it. Each one can be confirmed with Meta’s own tools before anything is changed. Getting that diagnosis right is the first job in any programme of Facebook and Instagram advertising for UK businesses.

The checks below assume tracking was set up at some point and has since stopped working or never reported correctly. Setting tracking up from scratch is covered in our guide to Facebook conversion tracking and why it matters, so the focus here stays on finding and fixing a broken setup.

Why Your Meta Pixel Is Not Tracking Conversions

A Meta Pixel stops reporting conversions for one of six broad reasons. Each one leaves different evidence. The Pixel may not load at all, the conversion event may fire on the wrong action, the cookie banner may hold it back, browsers and ad blockers may stop it, server events may be duplicated or the numbers may simply be counted differently from your own records.

Matching the symptom to the likely cause saves time, because the same complaint of missing conversions can come from very different faults. The table below lists the common symptoms and where to look first.

Work through the checks in the order below, since the earlier ones rule out the faults that stop tracking completely. Keep a note of what each check shows and when, so any later change can be measured against it.

Check the Pixel Loads With Meta Ads Data Advisor

The quickest way to see whether the Pixel loads is Meta Ads Data Advisor, the Chrome extension that replaced Meta Pixel Helper. Meta’s documentation on Meta Ads Data Advisor explains that the extension icon shows a badge with the number of Pixel events fired on the current page. No badge means no Pixel was found.

Turn off any ad blocker for your own website first, because Meta’s testing steps include that instruction and a blocker can hide a Pixel that is working. Open the page, complete the action you want to track and read the side panel. Meta lists three Pixel statuses, with Active meaning the Pixel works, Warning meaning it is not set up correctly and Inactive meaning it is not sending events.

Individual events carry their own status as well. An event marked Error has a critical configuration problem such as blocked parameters, duplicate events or a compliance violation, while a Warning points to issues that may affect performance. Meta’s troubleshooting notes for the extension list the setup faults behind most of these messages.

• The Pixel code appears more than once on the same page.
• The base code sits outside the head section of the page, which Meta says can lead to missed tracking.
• An iframe, a tag manager or a privacy tool is stopping the Pixel from running.
• Standard events load before the base Pixel code rather than after it.
• The account used for setup does not have full access to the Pixel.

Placement matters because Meta’s guide to installing the Meta Pixel recommends adding the base code between the head tags of every page, which reduces the chances of browsers or third party code blocking it. The same guide notes that the base code holds the Pixel ID in two places, so a website that still carries an old Pixel ID after a redesign or a change of agency will send its events to an account nobody is watching.

Confirm Events Arrive in Events Manager

Events Manager confirms whether Meta received an event, which matters because a Pixel can fire in the browser without the event being usable. Meta’s guide to using the Conversions API says events should be visible in Events Manager within 20 minutes of being sent. The Overview shows raw, matched and attributed events along with the connection method used for each one.

The Test Events tool shows events as they arrive while you browse your own website. For server events, the tool generates a test code to send as the test_event_code parameter. Meta says that code must be removed from production requests because test events still flow into Events Manager and are used for targeting and measurement.

Timing faults show up here too. The same guide explains that server events can be sent up to seven days after they happen and that a request containing any event older than that is rejected in full, so a delayed export from a CRM can lose every conversion in the batch.

Invalid events cause the same kind of silent loss. The same guide says that one invalid event in a batch causes Meta to reject the whole batch. The Conversions API troubleshooting page explains that an invalid payload returns a 4xx response with only minimal error details. Logging every API response on your server is the dependable way to spot these rejections, because events Meta never accepted do not appear in Events Manager.

Fix Conversion Events That Fire on the Wrong Action

When PageView events arrive but Lead or Purchase events do not, the conversion event is missing or tied to the wrong action. Meta’s documentation on conversion tracking with the Meta Pixel describes three methods, which are standard events called in code, custom events you name yourself and custom conversions built in Events Manager from page URLs.

Custom conversions are the most fragile of the three on modern websites. They rely on a URL such as a thank you page, so a form that confirms a submission on the same page without loading a new URL never triggers them. The event needs to fire from the form’s success message instead.

Health and finance advertisers have an extra check, set out in the same documentation. Meta began restricting custom conversions that suggest specific health conditions or financial status from 2 September 2025. Flagged conversions cannot be used when creating new campaigns, so a renamed or rebuilt conversion may be needed.

WordPress websites add their own causes. The official Meta pixel for WordPress plugin installs the Pixel and supports the Conversions API, so adding it to a theme or tag manager that already loads the Pixel creates the duplicate code Data Advisor warns about. On WooCommerce stores, the Meta for WooCommerce extension sets up the Conversions API automatically and deduplicates events using a unique event ID, so a second tracking plugin sending the same events needs its own deduplication or should be removed.

Theme updates, plugin conflicts and caching changes can also break tracking code without anyone noticing on the page itself. Checking conversion events after every plugin or theme update belongs in any routine of WordPress support for business websites, because a broken event rarely shows until a campaign report looks wrong.

How Cookie Consent Affects Meta Pixel Tracking

Under UK rules the Meta Pixel needs consent before it runs, so visitors who decline advertising cookies will not be tracked and that is expected rather than a fault. The ICO’s guidance on how the storage and access rules apply to online advertising says that storage and access technologies used for online advertising require consent. It adds that measuring the effectiveness of campaigns forms part of that same consent rather than needing a separate one.

Meta provides a consent setting for this situation. Its developer page on GDPR and the Meta Pixel shows a revoke command placed before the Pixel starts, which pauses Pixel fires until a grant command is sent once the visitor agrees. The same page notes that the revoke command needs calling on every page.

The fault to look for is a banner that revokes consent but never grants it, or grants it only after a page reload the visitor never makes. Accept cookies on your own website, complete a conversion and check Data Advisor again, because an event that appears only after acceptance shows the banner is doing its job.

Meta’s guide to verifying a Conversions API setup notes that the Overview in Events Manager counts events received before they are deduplicated or discarded due to consent controls. Comparing those figures over time helps separate expected consent losses from a setup fault.

Consent banners also need to describe the Pixel accurately and record what each visitor chose. Our article on compliant cookies and GDPR for UK businesses covers the wider requirements in more detail.

Recover Lost Events With the Conversions API

The Conversions API recovers conversions the browser misses by sending the same events from your server to Meta. Meta’s recommendations for the Conversions API describe a redundant setup that shares the same events through the Pixel and the API together, because server events can carry website events the Pixel loses through network connectivity issues or page loading errors.

Browsers also limit what the Pixel can keep between visits. WebKit, the engine behind Safari, explains in its tracking prevention documentation that cookies created by JavaScript on a landing page reached through a link carrying a click ID are capped at 24 hours. The same page says other storage written by scripts is deleted after seven days without interaction. A buyer who clicks an ad and comes back to enquire two days later may no longer carry the click identifier the Pixel stored on the first visit.

Meta’s guide to ClickID and the fbp and fbc parameters recommends reading the fbclid value from the landing page URL on the server, setting the _fbc cookie in the HTTP response and sending fbc and fbp with server events whenever they are available. Any redirect or form that drops the fbclid parameter from the landing page URL removes that identifier before it can be stored.

Matching quality decides how useful server events are. Meta’s recommendations state that only matched events can be used for attribution and ad delivery optimisation. Sending customer information such as an email address, IP address, name and phone number with each server event may help raise Event Match Quality.

Wider changes to browser tracking affect every ad platform, not only Meta. Our overview of PPC tracking after third party cookies covers how they change measurement across paid search and paid social.

Stop Double Counting With Event Deduplication

Conversions counted twice usually mean the Pixel and the Conversions API are sending the same event without the details Meta needs to recognise it as one. Meta’s guide to handling duplicate Pixel and Conversions API events recommends matching on event name and event ID, with the Pixel’s eventID equal to the server’s event_id and the Pixel’s event name equal to the server’s event_name.

The deduplication window is also limited in time. Meta discards later copies when the same key arrives for the same Pixel within 48 hours of the first, so a server event sent days later will be counted again. An alternative method using the fbp cookie or an external ID generally only works when the browser event arrives first and the server event follows.

Meta’s verification guide describes the Event Deduplication tab, which shows the rate of events deduplicated from each source and displays a warning when that rate is too low. Low overlap between sources means one of them is sending keys the other does not send, or the keys it sends are not unique.

Check Domain Verification and Pixel Ownership

Domain verification proves your business owns the website domain in Meta’s Business Manager. Meta’s developer documentation on domain verification describes it as a way to claim ownership and control who can edit links to your content, completed by uploading an HTML file to the web root or adding a DNS TXT record.

Verification is about ownership rather than whether events fire, but it is worth checking after a website rebuild or hosting move, because either change can remove the file or the record. Pixel ownership deserves the same check, since a Pixel created in a former agency’s or freelancer’s account may still be collecting events your team cannot see or use in campaigns.

Confirm that the Pixel ID in the website code matches the one each ad set optimises for and that your business holds full access to it. Data Advisor lists full access to the Pixel in its setup checklist, so access problems are worth ruling out before any code is changed.

Why Ads Manager Numbers Differ From Your Own Records

Ads Manager will rarely match GA4 or a CRM exactly, because it applies Meta’s own attribution rules. Meta’s guidance on Insights API reporting explains that attributed results follow the attribution setting chosen for each ad set, which can include view windows. Conversions on your website are reported against the time of the conversion, while link clicks and other actions on Meta’s own platforms use the time of the impression.

Analytics tools and CRMs apply their own attribution rules, so the same enquiry can be credited to Meta in Ads Manager and to a different channel elsewhere. Compare trends and the size of the gap between sources over time rather than chasing an exact match. A sudden change in that gap is the signal that something in the tracking has broken.

Keep Meta Tracking Working After the Fix

Tracking breaks again whenever the website, the consent banner or the plugins change, so a short repeat check belongs in every release. Run Data Advisor and the Test Events tool after each change to forms, templates, cookie settings or tracking plugins. Compare event counts in Events Manager with the week before as part of the same check.

Meta’s documentation says Data Advisor can also monitor a setup over time and alert you when it detects issues, while the Event Freshness tab in Events Manager shows the average delay before server events arrive. A delay that drifts from real time towards daily or weekly is an early sign that a server integration needs attention.

• Data Advisor shows the Pixel as Active on every page that matters.
• Each conversion appears once in Test Events after a genuine test submission.
• Events fire only after a visitor accepts advertising cookies.
• Pixel and server events share the same event name and event ID.
• The Pixel ID in the website code matches the one each ad set uses.

An independent review catches the faults that routine checks miss, especially when the same tracking problems keep coming back. Priority Pixels builds its Meta conversion campaigns with full Conversions API integration and event deduplication. Its Meta Ads audits cover conversion tracking integrity alongside campaign structure, audience performance and creative fatigue. A structured Facebook Ads audit tests tracking against the rest of the account, which shows whether a fix has held.