The Definitive Guide to Meta Conversions API (CAPI) Server-Side for Operations Above BRL 100k/month

Meta Ads Signal Architecture in Large-Scale Operations

Companies that invest significant budgets in paid media operate in an auction that is highly sensitive to the quality of the data fed back to it. The Meta Ads machine learning algorithm uses conversion events to calibrate ad delivery and estimate each user's likelihood to buy.

Since Apple's App Tracking Transparency (ATT) and the spread of cookie-blocking policies in browsers such as Safari and Firefox, the traditional browser-based pixel has become vulnerable. A relevant share of the transactions completed on the site never reaches Ads Manager when tracking depends only on scripts running on the customer's device.

Anatomy of the Meta Conversions API (CAPI) Payload

The Conversions API creates a direct communication channel between the company's server and Meta's servers. The call fires synchronously or asynchronously when payment is confirmed, sending hashed data through secure REST calls.

Below is an example of a technical JSON payload structured for the /v20.0/{pixel_id}/events endpoint:

{
  "data": [
    {
      "event_name": "Purchase",
      "event_time": 1726752000,
      "event_id": "order_89412",
      "event_source_url": "https://empresa.com.br/checkout/sucesso",
      "action_source": "website",
      "user_data": {
        "em": ["4f728c35d90953a79d0362f6b86f1f4ab8826c7d7b3226db202888cf3e2840c8"],
        "ph": ["99c927f87f4c026939943485703ff3cb79ff735c0cf3ff3e0b25e173ffb612c6"],
        "client_ip_address": "177.18.240.12",
        "client_user_agent": "Mozilla/5.0 (iPhone; CPU iPhone OS 17_5 like Mac OS X)...",
        "fbp": "fb.1.1718000000.123456789",
        "fbc": "fb.1.1718000000.PAZnRzaAUY-c9wZG9m..."
      },
      "custom_data": {
        "currency": "BRL",
        "value": 4850.00,
        "content_type": "product",
        "order_id": "ORD-2026-89412"
      }
    }
  ]
}

Event Deduplication with a Shared event_id

To make sure a conversion is not counted twice, the recommended engineering approach sends the event redundantly and relies on native deduplication. The browser fires the Purchase event through the pixel while the server container simultaneously sends the payload with the same unique event_id.

Meta's infrastructure processes both events, compares the identification key and consolidates the record. If ad-blocking extensions prevent the browser event from firing, the server still delivers the data to the auction intact.

SHA-256 Hashing and Identifier Normalization

Meta requires all of the user's personal data (PII) to be hashed with SHA-256 before it travels over the network. The hash is only reliable, though, if the data is standardised first:

• Email: Trim leading and trailing spaces and convert to lowercase (example: [email protected]).
• Phone: International format with country code and area code, without spaces, dashes or parentheses (example: 5511999998888).
• First and last name: Lowercase, with no punctuation or honorific titles.
• fbp and fbc parameters: Must be preserved exactly as stored in the first-party cookies, with no change of format.

Frequently Asked Questions about Meta Conversions API (CAPI)

Engineering Implementation Roadmap

1. Dedicated Container Hosting: Provision Google Cloud Run containers or AWS instances under a subdomain the brand owns (example: dados.seudominio.com.br).
2. First-Party Cookie Configuration: Convert the _fbp and _fbc parameters into Set-Cookie headers with the HttpOnly and SameSite=Lax directives.
3. Upfront Data Normalization: Clean and sanitize the data before applying the SHA-256 hash function.
4. Health Monitoring in Events Manager: Check the deduplication rate and the match quality score in Meta Events Manager on a regular basis.