"The pixel is installed but Meta shows no conversions" covers several very different faults. Work through them in order — the first three account for most cases.
1. Confirm the base pixel actually loads
Install the Meta Pixel Helper extension and load the page. If it shows nothing, the base code is missing, placed after a script that errors, or blocked by a consent banner that never releases it.
Check the consent layer specifically. Many sites load the pixel only after opt-in and then never fire it because the banner's accept callback is misconfigured.
2. Confirm the conversion event fires
The base pixel firing on every page does not mean Lead or Purchase fires. Complete a real submission and watch Events Manager's Test Events tool live. If PageView appears and Lead does not, the event code is on a page users never reach — a common result of forms that submit via AJAX without redirecting.
3. Check the event name and parameters
Meta only optimises standard events it recognises. "lead" in lowercase, "Leads", or a custom "form_submit" will record but will not be usable as a standard conversion. Use exactly Lead, CompleteRegistration, Purchase, and so on.
4. Aggregated Event Measurement and iOS
Your domain must be verified and your events prioritised in Aggregated Event Measurement. If the event you are optimising for is not in the top eight configured events, iOS traffic will not report it. Unverified domains lose a large share of conversions silently.
5. Deduplication problems with CAPI
If you run both the pixel and the Conversions API without a shared event_id, Meta counts some conversions twice. If the event_id is shared but the event_name differs, deduplication fails in the other direction and events disappear.
Both halves must send the same event name, the same event_id and matching user data. This is the part most implementations get half right — see Meta Conversions API setup.
6. The remaining causes
Wrong pixel ID for the ad account. Ad blockers, which affect 15–30% of traffic. Attribution window shorter than your sales cycle. Single-page apps where route changes never re-trigger the event.
Once the pixel is verified working, add server-side events. Browser-only tracking loses a quarter or more of conversions even when it is configured perfectly.