Setting Up Meta Conversions API (CAPI) with First-Party Subdomain Routing

Why Client-Side Meta Pixel Loses 30% of Conversions

Browser ad-blockers, iOS privacy prompts, and network drops cause typical e-commerce stores to lose between 20% to 35% of purchase events before they ever reach Meta Ads Manager.

The Meta Conversions API (CAPI) sends conversion events directly from your server to Meta's Graph API, completely bypassing browser limitations.

Architecture Overview

Here is how a high-performance Meta CAPI pipeline operates with TagFlow:

1. Browser Event: The visitor checks out on your Shopify or WooCommerce store.
2. Custom Subdomain: The event is sent to ss.yourdomain.com via a first-party POST request.
3. TagFlow Container: The server-side GTM container hashes customer data (email, phone, name) using SHA-256 and enriches it with _fbp and _fbc click IDs.
4. Meta Graph API: The enriched payload is dispatched server-to-server with high Event Match Quality.

Ensuring Event Deduplication

To avoid counting duplicate purchases, ensure both your browser Pixel and server CAPI transmit matching event_id and event_name parameters:

// Example Deduplication Payload
{
  "event_name": "Purchase",
  "event_id": "ORDER_109283",
  "user_data": {
    "em": "f660ab912ec121d1b1e928a0bb4bc61b15f5ad44d5efdc4e1c92a25e99b8e44a",
    "ph": "8e8203c945199859f71c4860b24090b852926715f5eead817efbe165a25e1a3b",
    "fbp": "fb.1.1712849000.91283",
    "fbc": "fb.1.1712849000.IwAR28fX..."
  },
  "custom_data": {
    "currency": "BDT",
    "value": 3500.00
  }
}

Results: What to Expect

Stores migrating to TagFlow server-side Meta CAPI typically observe:

• Event Match Quality (EMQ): Increases from 6.2 to 9.4+ / 10.
• Attributed ROAS: 15-25% increase in reported conversions in Meta Ads Manager.
• Faster Page Speed: Reduced third-party client JavaScript execution improves Core Web Vitals.