Skip to content
Lunor Medya

20 Oct 2026 · 5 min read · Lunor Medya · Updated 21 Nov 2026

Troubleshooting the Meta Pixel and Conversions API: Data Quality, Consent and Privacy

Conversions missing or double-counted? Low match quality? Common Meta pixel and Conversions API problems, plus what cookie consent and KVKK mean for tracking.

Tracking review screen showing Events Manager warnings and a cookie consent banner

Setup is done and events are arriving, yet Meta's sales figure does not match your order panel, or warnings keep piling up in Events Manager. This article starts right there. It works through the most common data quality problems with the Meta pixel and Conversions API by symptom, then covers how to handle tracking under cookie consent and Turkey's KVKK. If you have not set things up yet, start with the setup checklist.

Troubleshooting by symptom

Conversions appear doubled

  • event_id may be missing or mismatched between browser and server events. Check in event details that both sides send the same name and ID.
  • The pixel may be loaded twice, for example by a plugin and a tag manager. Count how often the base code appears in the page source.
  • Purchase may fire every time the thank-you page loads. Tie the event to order confirmation and block repeats for the same order.

Conversions appear missing

  • Pixel-only setups lose events to ad blockers and browser restrictions. Server-side events narrow that gap.
  • If payment completes on an external payment page and the user never returns, Purchase may never fire. Send the event from the server when payment confirmation arrives.
  • If the pixel does not run after cookies are declined, that is expected; see the consent section below.
  • Meta reports within an attribution window. Sales it cannot connect to an ad will not appear there; that is a difference in method, not a bug.

Values are wrong or zero

  • The value field may be hard-coded or currency may be missing.
  • Decimal formatting: send a number (1250.00), not locale-formatted text such as "1.250,00".
  • Decide whether VAT and shipping are included and apply it consistently.

Low match quality

Events Manager shows a match quality score for server events. A low score means events are not being matched to people well enough. What helps:

  • Where you have a legal basis, send email and phone hashed and normalised per Meta's rules. Details matter, such as including the country code in phone numbers.
  • Add IP address and user agent to events.
  • Pass the browser's fbp and fbc cookie values to the server and include them.
  • Send an external_id for logged-in users.

Events are erratic or suddenly stop

  • A site update, theme change or plugin update may have removed the code. Run test events as a quick check after every release.
  • The Conversions API access token may have expired or lost permissions. Watch server logs for error responses from Meta.
  • Domain verification may have been lost, for instance after a DNS migration.

A weekly check routine

  1. Read warnings and diagnostics in Events Manager.
  2. Compare Meta's purchase and lead counts with your own system and note the direction and size of any gap.
  3. Look for a clear drop in match quality.
  4. Re-run test events after recent site changes.

Cookie consent and tracking

The pixel sets cookies and passes behaviour to Meta for advertising. That is not a strictly necessary cookie, so the general approach is to run marketing cookies only after the user consents. In practice:

  • The cookie notice should make "reject" as easy as "accept", with nothing pre-ticked.
  • The pixel should not load before consent; a tag manager can fire it based on consent status.
  • Apply the same consent logic to server-side events. Tracking someone through the server after they declined in the browser is risky both legally and for your reputation.
  • Keep a persistent cookie settings link so people can change their choice later.

The general KVKK picture

This is not legal advice; it is a general roadmap based on Law No. 6698 and the Turkish Data Protection Authority's guidance on cookies.

  • Notice: your privacy and cookie policy should clearly describe the Meta pixel and server-side data sharing: what data, for what purpose, shared with whom, and what rights people have.
  • Explicit consent: get consent for advertising and targeting; do not make it a condition of using the service.
  • Cross-border transfer: data goes to Meta's servers abroad, so you need a basis that fits current transfer rules. Settle this with your legal adviser.
  • Data minimisation: keep sensitive or unnecessary data such as health information or ID numbers out of event parameters. In healthcare, think carefully about which page views are sent as events at all; Meta's own policies also restrict this area.
  • Documentation: record which events are sent with which data; it makes responding to a request or audit much easier.

What your privacy policy should cover

  • That the site uses the Meta pixel and server-side measurement.
  • The types of data collected: pages visited, actions taken, hashed contact details.
  • The purpose: ad measurement, audience building, ad optimisation.
  • Who receives the data and that it is transferred abroad.
  • How to withdraw consent and how to contact you.

Getting help

Some tracking problems are fixed in the ad account, others in the site's code. To review your site's technical setup, see our maintenance and support service; for campaigns and measurement, see Meta Ads management.