{
  "id": 13464853,
  "title": "Meta Pixel Counting Purchases Twice: Causes and How to Fix Duplicates",
  "url": "https://urgent.news/2026/10/10/meta-pixel-counting-purchases-twice-causes-and-how-to-fix-duplicates",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-10T16:52:36.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/oscarvillegas/meta-pixel-counting-purchases-twice-causes-and-how-to-fix-duplicates-4o95"
  },
  "original_language": "en",
  "account": "Meta's Meta Pixel can mistakenly count purchases twice under certain circumstances. This typically occurs when the same sale reaches Meta from multiple sources without a shared event_id. For instance, this can happen when both the Meta Pixel and the Conversions API send the Purchase event, or when two apps or plugins send Purchase events. It can also occur when customers return to the thank-you page from an external payment gateway, causing the Meta Pixel to fire again.\n\nThe primary cause of these duplicate purchases is usually due to the Meta Pixel and the Conversions API both sending Purchase events without the same event_id. This prevents Meta from recognizing these as the same sale. Additionally, a single platform or app may send the event, such as a platform app combined with a plugin, or an app alone with Google Tag Manager.\n\nThank-you pages may also load multiple times, leading to duplicate Purchase events. These pages load once after an external payment, once upon a refresh, and once from the payment provider. The Purchase event is typically set on a page that is also loaded for other actions, further contributing to the duplication issue.\n\nTo identify this problem, compare one week of actual sales against the purchases logged in Meta's Events Manager. In Events Manager, examine the Purchase event to see how many events originate from the browser versus the server, and check the deduplication status. Utilize the Test Events tool to simulate a single purchase and count the number of resulting Purchase events.\n\nTo resolve this issue, ensure that only one tool sends each event to Meta. Send the same event_id, often the order ID, with both the browser event and the server event. Moreover, fire the Purchase event only once per order, for example, by checking the order ID before sending it.",
  "summary": "Meta counts a purchase twice when the same sale reaches it from two places without a shared event_id, for example the pixel and the Conversions API, or two apps or plugins that both send Purchase. It also happens when customers return to the thank-you page from an external payment page and the pixel fires again. The fix is one source per event and the same event_id on the browser and the server…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}