TagPipes Companion for Chrome Add to Chrome →

Media Tracking

Pixel Plus Conversions API: How Restaurants Stop Counting One Order Twice

Why your ordering flow now sends purchase twice

If you run Meta ads to online ordering, there's a good chance each order now reaches Meta twice: once from the Meta Pixel in the guest's browser, and once from your server through the Conversions API.

That's on purpose, and it's the right setup. Browsers block or drop events for all sorts of reasons, and the server copy fills the gap. Meta's own developer documentation calls this a "redundant setup" and recommends it. Meta Conversions API Explained covers what the Conversions API fixes and what it doesn't.

The catch is that redundancy only helps if Meta can tell the two copies are the same order. If it can't, one order becomes two purchases, and the campaign gets credit for orders that never happened. The checks below are our practice framing, not measured findings. We aren't claiming any share of restaurants gets this wrong.

How Meta matches the two

Meta's page on handling duplicate Pixel and Conversions API events spells out the recommended method. For the browser and server copies to be treated as one event:

  • "a Meta Pixel’s eventID must match the Conversion API’s event_id"
  • "a Meta Pixel’s event must match the Conversion API’s event_name"

So both copies need the same event name, Purchase on both sides, and the same ID: eventID on the Pixel and event_id on the server. If the Pixel sends no ID, or the server invents a different one, there's nothing to match on. Meta also says it only deduplicates events received within 48 hours of the first event with a given event_id.

Where the event ID should come from

The ID has to be the same value in two places that run at different times: the guest's browser and your server. The simplest way to guarantee that is to use something both sides already know once the order exists.

The order number is usually the right choice. It's fixed the moment the order is placed, it's unique, and both the confirmation page and the server-side order record have it.

What not to use: a timestamp, or a random value generated when the page loads. The browser and the server will each make their own, they won't match, and you're back to two purchases per order.

The fire-once rule

Deduplication handles the browser and the server sending the same order. It doesn't fix the browser sending it more than once.

Restaurant guests reopen confirmation pages all the time. They reload it to check the pickup time. They tap the link in an order email or text. If the Pixel fires purchase on every load of that page, each reload sends another purchase. Don't count on deduplication to clean that up. It's built to match a browser copy with a server copy, so the safe design is to stop the repeat at the source.

The rule: fire purchase when the order is placed, once. In practice that means a check on the confirmation page that remembers an order number has already been sent and skips it the second time.

A one-day test anyone can run

You don't need a developer to see whether there's a problem. Pick one recent ordinary day.

  • Look up purchases for that day in Meta Events Manager.
  • Pull the order count for the same day from your ordering platform.
  • Compare them.

They won't match exactly. Not every guest has a browser Meta can see, and not every order relates to Meta at all. But Meta's purchase count shouldn't be higher than your real orders. If it is, or if it looks like roughly double, the usual cause is a missing or mismatched event ID, or a purchase that fires on every page load. Meta also has its own tools for checking a deduplication setup, linked from the same documentation page.

What to fix first

In order:

  1. A shared ID. Send the same eventID from the Pixel and event_id from the server, with the same event name.
  2. A stable source. Use the order number or another value fixed when the order is placed, not one generated on page load.
  3. A fire-once guard. Purchase fires on order placement, not on every load of the confirmation page.

Then run the one-day test again a week later.

What you can trust once it holds

Once those three hold, Meta's purchase count lines up with your orders closely enough to compare campaigns against each other. That's all it promises. It won't make a campaign perform better on its own; it makes the number you judge it by honest.

The same one-order, one-count rule applies on the Google side; One Order, One Conversion covers that audit. If you'd rather have someone check both, book a data and tracking audit.

Source: Meta for Developers, Handling Duplicate Pixel and Conversions API Events, read November 19, 2026.

Get new research by email

New posts and Website Privacy Index findings, sent to your inbox. No spam, unsubscribe anytime.

We only use your email for this list. See our Privacy Policy.

About Rawsoft

Rawsoft is an Atlanta-based digital data agency specializing in analytics implementation, privacy and consent management, and media tracking for enterprise brands.

Add Rawsoft as a preferred source on Google

More from the blog

Media Tracking

Meta Conversions API Explained: What CAPI Fixes

The Meta Conversions API recovers signal lost to ad blockers, ITP and consent, but only if you deduplicate and send standard events. How CAPI really works.

July 2026Read

Media Tracking

One Order, One Conversion: Cleaning Up a Restaurant's Google Ads Goals

Smart bidding learns from whatever you mark as Primary. If one online order is counted by several conversion actions, the account optimizes toward a bigger number than your real orders.

November 2026Read