Three CAPIs, Three Endpoints, One WooCommerce Store — Run Them All Server-Side

What three Conversions APIs do WooCommerce stores need in 2026?#

Google Enhanced Conversions via Measurement Protocol, Meta CAPI via Graph API v25.0, and OpenAI CAPI at bzr.openai.com — each with distinct endpoints and authentication. If you’re running ads across all three platforms, you need 3 APIs, 3 endpoints, and 3 auth mechanisms (Seresa, 2026) working simultaneously from your WooCommerce store.

Google uses the Measurement Protocol with an API secret and measurement ID. Meta requires an access token from Events Manager. OpenAI needs a Conversions API key plus a Pixel ID from OpenAI Ads Manager. None of these tokens are interchangeable, none of these endpoints accept the same payload format, and none of them share an event schema.

The complexity isn’t theoretical. A WooCommerce purchase fires one event on your server. That single event needs to be transformed into three different payloads, authenticated against three different token systems, and delivered to three different URLs — all within the attribution window each platform expects. Miss one, and you lose conversion data for that platform’s optimisation algorithm.

WooCommerce stores now need 3 separate server-side Conversions APIs — each with distinct endpoints, authentication, and PII hashing requirements (Seresa, 2026).

How does PII hashing differ between Google, Meta, and OpenAI?#

Meta and OpenAI require SHA-256 hashed email, phone, and name before transmission. Google Enhanced Conversions accepts unhashed data and hashes server-side. Getting this wrong doesn’t throw an error — it silently fails to match conversions to ad clicks, and your optimisation data degrades without warning.

SHA-256 is required for Meta and OpenAI; Google hashes server-side (Netro Ads, 2026). The difference matters at the implementation level. For Meta, you lowercase and trim the email, then SHA-256 hash it before including it in the event payload. OpenAI follows the same pattern. Google, by contrast, wants the raw email — their server handles the hashing.

If you hash data for Google when it expects raw input, the match rate drops. If you send raw data to Meta when it expects a hash, the event is rejected or silently ignored. Two of the three platforms demand pre-hashing; one demands you don’t. A single WooCommerce checkout must branch its PII handling three ways.

Related: Six WooCommerce Server-Side Tracking Plugins That Don’t Need GTM (2026)

Can one WooCommerce plugin send to all three CAPIs?#

Netro Ads handles Meta and OpenAI CAPI from one plugin. Google Enhanced Conversions requires separate configuration. No single plugin covers all 3 CAPIs — Netro handles 2 of 3 (Netro Ads, 2026).

This means most WooCommerce stores running triple-CAPI need at least two plugins: one for Meta plus OpenAI, and a separate setup for Google Enhanced Conversions. Each plugin has its own settings page, its own event hooks, its own deduplication logic, and its own failure modes. When something breaks — and WooCommerce updates, plugin conflicts, and checkout customisations guarantee it will — you’re debugging across two independent systems.

The alternative is a managed server-side platform that intercepts the WooCommerce event once and routes it to all three endpoints from a single integration. That collapses three maintenance burdens into one, but it also means choosing a platform that keeps pace with API version changes across Google, Meta, and OpenAI simultaneously.

What is Meta’s CAPI endpoint for WooCommerce?#

Graph API v25.0 shipped February 18 2026, with events sent via access token from Events Manager to the dataset endpoint. Graph API v25.0 has been current since Feb 18 2026 (AdsUploader, 2026). If your plugin is still sending to an older API version, your events may stop processing when Meta deprecates it.

The performance case is clear. Meta CAPI delivered 17.8% lower CPA compared to pixel-only measurement (Meta, 2026). That reduction comes from matching server-side events to ad clicks with higher fidelity than the browser pixel can achieve — especially after ad blockers, ITP, and consent rejection have hollowed out client-side tracking.

For WooCommerce specifically, the integration hooks into the order completion event, collects the hashed customer data, constructs the event payload with event_id for deduplication, and POSTs it to Meta’s endpoint. Every step is an opportunity for silent failure if the access token expires, the API version changes, or the event_id doesn’t match the browser pixel’s.

What is OpenAI’s CAPI endpoint?#

Events go to bzr.openai.com/v1/events authenticated with a Conversions API key and Pixel ID from OpenAI Ads Manager. OpenAI CAPI at bzr.openai.com/v1/events requires SHA-256 hashing (Netro Ads, 2026). The endpoint is new, the documentation is sparse, and adoption is accelerating fast.

5,618 stores now run the OpenAI tracking pixel — 614% quarter-over-quarter growth (StoreLeads, 2026). That velocity means the CAPI side will matter soon for any store advertising on ChatGPT. The client-side pixel gives OpenAI basic page-view and conversion signals; the server-side CAPI adds the high-fidelity match data that survives ad blockers and browser restrictions.

The implementation pattern mirrors Meta’s: capture the WooCommerce conversion event, hash the PII with SHA-256, construct the payload, and POST to the endpoint. But the auth is different (API key plus Pixel ID rather than an access token), the deduplication uses shared event IDs between browser and server, and the event schema is OpenAI-specific. You can’t reuse your Meta CAPI code with a different URL.

5,618 stores already run the OpenAI tracking pixel with 614% quarter-over-quarter growth — the CAPI side will matter soon for any store advertising on ChatGPT (StoreLeads, 2026).

How does deduplication work across three platforms?#

Each platform has its own deduplication mechanism — Meta uses event_id, Google uses transaction_id, OpenAI uses shared event IDs between browser and server — all three managed independently. That’s 3 independent deduplication mechanisms (GlobalDev SignalBridge, 2026), each with its own failure mode.

Deduplication matters because most stores run both a client-side pixel and a server-side API for each platform. Without deduplication, every conversion is counted twice — once by the browser pixel and once by the server event. Doubled conversions feed doubled data into the platform’s bidding algorithm, which then overbids because it believes conversions are twice as cheap as they actually are.

The fix is straightforward in principle: generate a unique event ID when the conversion fires, pass it to both the browser pixel and the server-side API, and let the platform match and deduplicate. In practice, doing this across three platforms with three different ID schemes, three different pixel implementations, and three different server endpoints is where most DIY setups break down.

Related: ChatGPT Ads ROAS on WooCommerce: Why the Number in OpenAI Ads Manager Doesn’t Match Your Actual Profit

Platform	Endpoint	Auth	PII Hashing	Dedup Key
Google Enhanced Conversions	Measurement Protocol	API secret + measurement ID	Server-side (send raw)	transaction_id
Meta CAPI	Graph API v25.0	Access token	SHA-256 (pre-hash)	event_id
OpenAI CAPI	bzr.openai.com/v1/events	API key + Pixel ID	SHA-256 (pre-hash)	Shared event ID

Does running three CAPIs affect WooCommerce page speed?#

No — server-side API calls fire from the server after the page is served, adding zero latency to the shopper’s experience. The browser never waits for any of the three API responses. Zero page-speed impact from server-side calls (Netro Ads, 2026) — the work happens entirely behind the scenes.

This is the core advantage of server-side over client-side tracking at scale. A client-side pixel blocks page rendering until it loads. Three client-side pixels block it three times. Server-side events are asynchronous — the WooCommerce server processes the order, returns the thank-you page to the shopper, and then fires the three API calls independently. The shopper’s page is already loaded and visible before a single byte leaves for Google, Meta, or OpenAI.

The trade-off is server load. Three outgoing API calls per conversion add CPU and network overhead to your hosting. For most WooCommerce stores, this is negligible — a few hundred milliseconds of server time per order. For high-volume stores processing thousands of orders per hour, a managed server-side platform offloads this work to dedicated infrastructure rather than loading your WooCommerce server.

What does a managed triple-CAPI solution cost vs DIY?#

DIY means maintaining three separate API integrations, auth tokens, event mappings, and deduplication. A managed platform routes one event to all three from one integration — 1 integration vs 3 means significant maintenance reduction (Seresa, 2026).

The cost of DIY isn’t the initial setup. It’s the ongoing maintenance. Meta ships a new Graph API version and deprecates the old one on a predictable cycle. OpenAI’s CAPI is new and evolving fast. Google changes Enhanced Conversions configuration. Each change requires updating your plugin, testing the integration, and verifying that events still match. Three platforms changing independently means you’re always patching something.

A managed solution like Transmute Engine absorbs that maintenance. It hooks into WooCommerce once, captures the purchase event, and routes it to all three CAPIs — handling the PII hashing differences, the auth token management, and the deduplication for each platform. The store owner configures one integration instead of three, and API version changes are handled upstream. The cost is a monthly fee; the savings are the developer hours you’d spend chasing three different API deprecation cycles.

Key Takeaways#

• Three CAPIs are now mandatory: Google, Meta, and OpenAI each require their own server-side Conversions API with distinct endpoints and authentication.
• PII hashing is not uniform: Meta and OpenAI demand SHA-256 pre-hashing; Google hashes server-side — sending wrong data silently breaks match rates.
• Meta CAPI cuts CPA by 17.8%: server-side events deliver higher match fidelity than browser pixels alone.
• OpenAI adoption is accelerating: 5,618 stores now run the OpenAI pixel with 614% QoQ growth.
• Deduplication is triple the complexity: three independent mechanisms must be managed separately to prevent double-counted conversions.
• Zero page-speed impact: all three API calls fire server-side after the page is served.

References#

1. AdsUploader (2026). Meta Conversions API: Complete Guide. Source
2. Meta (2026). Meta Pixel and Conversions API AI Updates. Source
3. Netro Ads (2026). WordPress Plugin for Meta and OpenAI CAPI. Source
4. StoreLeads (2026). OpenAI Tracking Pixel Adoption. Source
5. GlobalDev SignalBridge (2026). Multi-Platform Event Deduplication. Source