Skip to content

Meta Pixel and Conversions API: what to check when conversions don’t come through

TroubleshootingUpdated 14 Nov 20266 min read

Cover: two signal lines from a browser and a server merging at one point into a single event box
In this article
  1. Check the pixel on the page with Meta Ads Data Advisor
  2. See whether events reach Meta
  3. Running both Pixel and Conversions API: deduplicate events
  4. Raise Event Match Quality
  5. Send events close to when they happen
  6. Checklist
  7. Where AdPilot fits
  8. Sources

The Meta Pixel is a snippet of JavaScript code that lets you track visitor activity on your website (source). The Conversions API connects your marketing data — from your server, website platform, mobile app or CRM — to Meta’s systems (source).

If conversions aren’t coming through, this article walks through five steps: check the pixel on the page, see whether events reach Meta, deduplicate when you send through both, raise match quality, and send events close to when they happen.

1. Check the pixel on the page with Meta Ads Data Advisor

Meta Ads Data Advisor (formerly Meta Pixel Helper) is a free browser extension for Google Chrome and Microsoft Edge (source). According to Meta, you use it to (source):

  • Verify Pixel and Conversions API installation and whether events fire.
  • Flag errors such as broken events and missing parameters (for example content_ids, value and currency).

To check: open a page with the pixel, click the Data Advisor icon in your browser toolbar, and confirm that the expected event appears and shows as successful (source). Two statuses to know (source):

  • Active: the event is being sent correctly.
  • Error: the event has a critical configuration issue that needs action, such as blocked parameters, duplicate events or a compliance violation.

2. See whether events reach Meta

Pixel events. Go to Events Manager, find your pixel and click its details. A new PageView event means the pixel is installed. If you don’t see it, wait a few minutes and refresh the page (source).

Server events (Conversions API). Meta says you should be able to verify them within 20 minutes of sending (source).

  1. On the Data Sources page, click the pixel that matches the pixel ID you sent to.
  2. Click Overview. It shows how many events Meta received before they were deduplicated, discarded under consent controls and other policies, or processed (source).

To check your Conversions API connection before going live, Meta suggests the Test Events tool (source).

3. Running both Pixel and Conversions API: deduplicate events

For optimal ad performance, Meta recommends implementing the Conversions API alongside the Meta Pixel and sending the same events through both; Meta calls this a “redundant setup” (source).

If you send an event through both, Meta needs to know it’s one event (source):

  • The pixel’s eventID must match the Conversions API’s event_id.
  • The pixel’s event must match the Conversions API’s event_name.

On the pixel, eventID is the fourth argument of the fbq track call (source):

fbq('track', 'Purchase', {value: 12, currency: 'USD'}, {eventID: 'EVENT_ID'});

Meta only deduplicates events received within 48 hours of when Meta receives the first event with a given event_id (source). The rate of deduplicated events is on the Event Deduplication tab of the event details (source).

If you don’t send the same event through both, you don’t need to set up deduplication for that event (source).

4. Raise Event Match Quality

Event Match Quality shows how effective the customer information in your server event may be at matching it to a Facebook or Meta account (source). It’s scored from 1 to 10; where possible, Meta typically recommends aiming for 6.0 or higher (source). The score is currently available only for web events (source).

Sending more customer information parameters may help raise the score — for example email (em), phone number (ph), name (fn, ln) and IP address (client_ip_address) (source). When you send them (source):

  • Contact information has to be hashed: Meta’s systems are designed not to accept unhashed contact information, except where noted.
  • Email: hashing required; trim leading and trailing spaces and convert to lowercase before hashing.
  • Phone numbers must include a country code to be used for matching.
  • Don’t hash client_ip_address, client_user_agent, fbc or fbp.

5. Send events close to when they happen

Meta recommends keeping the time between when an event occurs (the event_time parameter) and when it’s shared with Meta as close to real time as possible (source). The Conversions API lets you send events in real time or in batches close to real time (source). Delay shows on the Event Freshness tab, on a scale from “Real Time” to “Weekly” (source).

Checklist

  • Data Advisor shows the expected event as Active on the page
  • Events Manager shows the pixel event (wait a few minutes, then refresh)
  • Server events show in Overview within 20 minutes of sending
  • Sending through both: event_id / eventID and event_name / event match
  • Match quality: aiming for 6.0+; contact details hashed, IP and user agent not hashed
  • Events sent close to real time; Event Freshness tab checked

Where AdPilot fits

AdPilot for Meta Ads gives an overview across many accounts in one pass, including which pixels have gone quiet (source). For an agency managing many accounts, that tells you which account to check first. Checking and fixing the pixel and Conversions API still happens in Meta, as above.

See AdPilot for Meta Ads · Running Google Ads too? Read Google Ads conversions not recording.

💬 Need help? Join the ALFA Software support group on Telegram (ask in your own language) — or message our support bot privately about your account or invoices.

Checked against Meta’s documentation on 8 Nov 2026. Meta’s interface and documentation can change; where they differ from this article, follow Meta’s documentation.

Sources

  1. Meta for Developers — Meta Pixel: https://developers.facebook.com/docs/meta-pixel
  2. Meta for Developers — Get started with the Meta Pixel: https://developers.facebook.com/docs/meta-pixel/get-started
  3. Meta for Developers — Meta Ads Data Advisor: https://developers.facebook.com/docs/meta-pixel/support/pixel-helper
  4. Meta for Developers — Conversions API: https://developers.facebook.com/docs/marketing-api/conversions-api
  5. Meta for Developers — Handling Duplicate Pixel and Conversions API Events: https://developers.facebook.com/docs/marketing-api/conversions-api/deduplicate-pixel-and-server-events
  6. Meta for Developers — Verifying Your Setup: https://developers.facebook.com/docs/marketing-api/conversions-api/verifying-setup
  7. Meta for Developers — Best Practices — Conversions API: https://developers.facebook.com/docs/marketing-api/conversions-api/best-practices
  8. Meta for Developers — Customer Information Parameters: https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/customer-information-parameters
  9. ALFA Software — AdPilot for Meta Ads: https://alfasoftwares.com/en/adpilot-meta