Analytics WooCommerce Optional

Headless Meta Pixel

Full Meta Pixel integration for headless stores. Proxy browser events to the Conversions API (CAPI) with automatic PII hashing, event deduplication, and WooCommerce purchase tracking.

View Source

Features

REST endpoint for frontend pixel initialization

Server-side Conversions API (CAPI) forwarding

SHA-256 hashing of all PII (email, name, phone, address)

Event deduplication via matching event_id (browser + server)

Automatic WooCommerce purchase tracking on order status change

Per-event toggles and test event code support

API Endpoints

Method	Path	Description
GET	/headless-meta-pixel/v1/config	Returns pixel_id
POST	/headless-meta-pixel/v1/track	Proxy browser events to Conversions API

API Example

// Track event via Conversions API
const response = await fetch(
  "https://store.example.com/wp-json/headless-meta-pixel/v1/track",
  {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({
      event_name: "AddToCart",
      event_id: "evt_abc123",  // for deduplication
      custom_data: {
        currency: "INR",
        value: 1499.0,
        content_ids: ["SKU-001"],
        content_type: "product",
      },
    }),
  }
);

{
  "success": true,
  "events_received": 1,
  "fbtrace_id": "A2b3C4d5E6f7G8h9"
}

FAQ

How does event deduplication work?

Your frontend sends events with an event_id. The /track endpoint forwards the same event_id to CAPI. Meta deduplicates events with matching IDs, so each conversion is counted once.

Is PII handled securely?

All personally identifiable information (email, name, phone, address) is SHA-256 hashed before being sent to Meta, as required by the Conversions API specification.