Skip to main content
NS
Ecommerce21 Nov 2026·By Nazmun Sakib·5 min read

Meta Conversions API for WooCommerce: how to send events and avoid duplicates

Sending events from your server to Meta improves measurement, but only if browser and server events are deduplicated. Here is how it works and what to check.

Browser tracking has become less reliable. Ad blockers, privacy settings and short-lived cookies mean the Meta Pixel misses some purchases, and that makes ad optimisation and reporting worse. The Meta Conversions API lets your server send events straight to Meta, so conversions are reported even when the browser cannot. The catch is that when you use both, every event has to be deduplicated, or purchases are counted twice.

How the pieces fit together

  • The Meta Pixel runs in the visitor's browser and reports what it sees.
  • The Conversions API runs on your server and reports events you choose to send, such as a purchase when an order is paid.
  • Meta receives both and removes duplicates, using the event name and a shared event ID.

Used together, they give you browser signals and server reliability.

Why event_id is the whole game

When a purchase happens, the Pixel can send a Purchase event and your server can send a Purchase event for the same order. If both carry the same event_id, Meta recognises them as one. If the IDs differ or one is missing, Meta counts two purchases, and your cost per result and return on ad spend are wrong.

  • Create one event ID per event, such as one per order.
  • Send that exact ID from the browser as the event ID and from the server as the event_id.
  • A stable choice for purchases is something derived from the order ID, so a reload cannot generate a new one.

What to send for a purchase

A good server event includes:

  • The event name, Purchase, and the event time.
  • The event_id shared with the Pixel.
  • The event source URL and the action source, which is website for online store events.
  • Value and currency, matching the order.
  • Content details: product IDs, quantities and the content type.
  • Customer information parameters to help Meta match the event to a person.

Customer data: hash it, and respect consent

Meta matches events to people using identifiers. Email, phone, name and address details are normalised, for example lower-cased and trimmed, and hashed with SHA-256 before sending. The browser identifiers stored in the fbp and fbc cookies can be passed along as well. Only send what you are allowed to send. If a visitor has not consented to marketing or analytics where the law or your policy requires it, do not send their data, and make sure your consent setup controls the server events too. Server-side sending does not bypass consent.

When to fire the server event

Fire it from the server when WooCommerce confirms the order is paid or in a status you treat as a completed purchase, not when someone merely lands on a page. That way off-site payment gateways, page reloads and closed tabs do not change the outcome. Also make sure the same order cannot be sent twice, for example by saving a flag on the order once the event has been sent successfully.

Test before you trust it

  • Use the Test Events tool in Meta Events Manager with a test event code to watch events arrive in real time.
  • Place a test order and confirm that browser and server events appear and are marked as deduplicated.
  • Check the event match quality shown in Events Manager and improve the customer parameters you can legitimately send.
  • Compare Meta's purchase count with WooCommerce orders over a few days.

Common mistakes

  • Different event IDs in the browser and on the server.
  • Sending the server event but leaving two Pixel installs running, so the browser sends it twice.
  • Sending unhashed personal data.
  • Sending the event before payment is confirmed, which counts failed orders.
  • Storing the access token in a place that is exposed on the page.

Keep the access token secret

The Conversions API uses an access token that allows sending data on behalf of your account. Keep it on the server, in configuration and not in front-end code or a public repository, and rotate it if it is ever exposed.

Need help setting it up?

I set up GA4, Google Tag Manager, server-side tracking and the Meta Conversions API for WooCommerce stores, including deduplication and validation against real orders. If your Meta numbers do not match your store, describe what you see and I can look at where the gap comes from.

Frequently asked questions

What is the Meta Conversions API?

It lets your server send conversion events, such as purchases, directly to Meta, as a complement to the browser Pixel. It is less affected by browser restrictions, ad blockers and lost cookies.

Do I still need the Meta Pixel if I use the Conversions API?

Meta recommends using both. The Pixel captures browser signals and the Conversions API adds reliability. They must share an event_id so Meta can remove duplicate events.

How does Meta deduplicate events?

When the same event name and event_id arrive from both the Pixel and the Conversions API, Meta keeps one. If the event_id is missing or different, the purchase is counted twice.

Do I need to hash customer data for the Conversions API?

Customer identifiers such as email and phone should be normalised and hashed with SHA-256 before sending, and only sent where you have the right to do so, including consent where required.

ShareX / TwitterLinkedIn