Definition

The Meta Conversions API (CAPI) is a server-side method for sending conversion events (purchases, leads, signups) directly from your website server or CRM to Meta — bypassing browser limitations like ad blockers and iOS App Tracking Transparency (ATT).

Detailed Explanation

CAPI complements the Meta Pixel (browser-side). Together they provide event deduplication using matching event_id values — the same event sent via Pixel and CAPI is counted once.

Benefits: improved attribution after iOS 14.5+, better data for ad optimization, and resilience when cookies are blocked.

Implementation options: Meta’s partner integrations (Shopify, WooCommerce plugins), Google Tag Manager server-side, direct API calls, or automation tools (n8n, Zapier).

Nepal Context

Nepali e-commerce sites with high mobile traffic and ad blockers lose significant Pixel data. CAPI via WooCommerce plugin or GTM server container recovers conversions that would otherwise be invisible to Meta Ads Manager — critical for ROAS optimization.

Practical Examples

  1. Plugin route: WooCommerce Facebook plugin sends Purchase events server-side automatically.
  2. GTM server-side: Server container receives webhook, forwards to Meta Graph API with hashed email/phone.
  3. Offline events: Import COD-confirmed orders from spreadsheet via Conversions API weekly.

Key Takeaways

  • CAPI = server-side event tracking for Meta Ads.
  • Always deduplicate with Pixel using shared event_id.
  • Send hashed PII (email, phone) for Event Match Quality improvement.

Common Mistakes

  1. CAPI only, no Pixel — lose browser signals; run both.
  2. Duplicate events without deduplication — inflated conversion counts.
  3. Not sending customer data parameters — low Event Match Quality scores.