Event Deduplication Engine
How WP Zbridge reports each WooCommerce purchase exactly once, from the browser or from the server.
Event Deduplication Engine PRO
Section titled “Event Deduplication Engine ”WP Zbridge reports every WooCommerce purchase from the visitor’s browser and keeps a server-side fallback for purchases the browser could not deliver (ad blockers, closed tabs, failed redirects). The server only sends an order the browser did not report, and at most once.
1. Browser first, server as fallback
Section titled “1. Browser first, server as fallback”- Thank-you page: The browser sends
Order Completedto Zaraz. The event is sent once per order; reloading the page does not report it again. - Confirmation: Once Zaraz has received the event, the browser tells WordPress, which marks the order as delivered.
- Server fallback: When an order is paid, WP Zbridge schedules a server-side check (10 minutes later by default, using WooCommerce’s Action Scheduler). If the browser has not confirmed the order by then, the server sends
Order Completedto the Zaraz HTTP Events API.
The server event carries the buyer’s IP address, user agent, page URL, tracking cookies and Zaraz consent cookie captured at checkout, so tools can attribute it to the same visitor and Zaraz applies the buyer’s consent.
2. Shared identifiers
Section titled “2. Shared identifiers”Both the browser and the server send the same order_id and the same deterministic event_id:
$eventId = "order_{$orderId}_" . md5("order_{$orderId}_{$createdAt}");Meta uses event_id, and GA4 uses order_id (sent to GA4 as the transaction ID), to merge any duplicate that still arrives from both sides.
3. Server-side locking
Section titled “3. Server-side locking”Each order is sent from the server at most once. A transient lock (wp_zaraz_order_dedup_{orderId}) blocks repeated sends when WooCommerce fires several status changes for the same order.
4. HTTP Events API path
Section titled “4. HTTP Events API path”Server events are posted to a per-site path such as /zaraz/1f3a9c0b7d2e4a6c. The path is generated on first use and written into the exported container (settings.eventsApiPath), so importing or syncing the container enables it in Zaraz. Re-export or re-sync after updating the plugin.