What is Meta CAPI? Complete Guide for eCommerce Brands (2026)

Meta’s Conversions API, or CAPI, is a server-side connection that sends conversion events — purchases, leads, sign-ups — from your server directly to Meta, rather than from the visitor’s browser. Because it does not run in the browser, it still delivers the events that iOS privacy settings and ad blockers stop the Meta Pixel from sending.

What is Meta CAPI?

Related Articles

• Meta Pixel vs Conversions API: Key Differences Explained
• Meta CAPI Setup for Shopify: Step-by-Step Guide
• How to Improve Meta Event Match Quality (2026 Guide)
• Free Tracking Audit Checklist: Is Your Ad Tracking Working?

Meta CAPI (Conversions API) is a server-side tracking tool that sends your conversion data directly from your web server — or CRM — to Meta’s advertising platform. Unlike the Meta Pixel, which relies on a browser, CAPI sends data through a secure server-to-server connection that cannot be blocked by ad blockers, iOS privacy settings, or browser restrictions.

Meta officially describes CAPI as a “business tool” that connects your marketing data directly to Meta, helping you measure ad performance, optimise delivery, and find new customers — even in a privacy-first world.

Why Did Meta Create the Conversions API?

The short answer: Apple’s iOS 14 update (2021) destroyed Facebook’s ability to track users via browser-based pixels. After the ATT prompt rollout, Meta lost visibility into ~40% of iOS conversions. Advertisers saw ROAS drop, CPAs rise, and reporting collapse.

Meta’s response was to move tracking upstream — to your server, where Apple cannot interfere. This is what CAPI does.

How Does Meta CAPI Work?

Here is the data flow when a customer purchases on your store:

1. Customer action: Shopper completes a purchase on your website.
2. Server event fires: Your server (or third-party platform like Shopify) sends a Purchase event to Meta’s CAPI endpoint with customer parameters.
3. Meta receives event: Meta uses the customer data (email hash, phone hash, IP, User-Agent) to match the event to a Facebook/Instagram user profile.
4. Attribution: If matched, Meta attributes the conversion to the ad that drove the purchase.
5. Optimisation: Meta’s algorithm uses this signal to find more customers who are likely to convert.

The key difference from pixel-only tracking: even if the browser never fires the pixel event (ad blocker, Safari ITP, App Store policy), the server still sends the event directly to Meta.

Meta CAPI vs Meta Pixel: The Critical Difference

Feature	Meta Pixel (Browser)	Meta CAPI (Server)
Data source	User’s browser	Your web server / CRM
Blocked by iOS 14?	Yes (partially)	No
Ad blockers?	Yes, often blocked	No, bypasses browser
Data richness	Limited (browser only)	Full customer data
Event match quality	4-6 / 10 typical	8-10 / 10 typical
Setup complexity	Low	Medium-High

Best practice: Run both Pixel AND CAPI simultaneously with deduplication enabled. This is called “redundant tracking” — it catches events that either method misses. Meta automatically deduplicates matching events using the event_id parameter.

Who Should Use Meta CAPI?

If any of the following apply to your business, Meta CAPI is not optional — it is essential:

• eCommerce brands running Facebook/Instagram ads to drive sales
• Lead generation businesses optimising for form fills, calls, or CRM deals
• Subscription services tracking recurring payment events
• Anyone seeing Event Match Quality below 7.0
• Advertisers targeting iOS users (likely 50-60% of your audience)
• Brands using iOS-first social proof (Fashion, Beauty, Lifestyle, Fitness)

What Events Can You Send via Meta CAPI?

Meta CAPI supports all standard Meta events, including:

• Purchase — most important for eCommerce
• Lead — form submissions, quote requests
• AddToCart — product interest signals
• InitiateCheckout — checkout intent
• ViewContent — product page views
• CompleteRegistration — sign-ups
• Subscribe — subscription events
• Custom events — anything specific to your funnel

You can also send offline events and CRM events via CAPI — for example, when a lead closes in Salesforce weeks after clicking an ad.

Customer Parameters: The Secret to High Match Quality

The more customer information you send with each CAPI event, the better Meta can match it to a user profile. Here are the parameters ranked by impact on Event Match Quality (EMQ):

Parameter	API Key	EMQ Impact
Email address	em	Very High ⭐⭐⭐⭐⭐
Phone number	ph	Very High ⭐⭐⭐⭐⭐
First name	fn	High ⭐⭐⭐⭐
Last name	ln	High ⭐⭐⭐⭐
Date of birth	db	Medium ⭐⭐⭐
City / State / Zip	ct, st, zp	Medium ⭐⭐⭐
External ID	external_id	Medium ⭐⭐⭐
IP + User-Agent	client_ip_address, client_user_agent	Supporting ⭐⭐

All PII (email, phone, name) must be SHA-256 hashed before sending. Meta hashes on their end too, so they match against hashed first-party data from Facebook/Instagram profiles.

How to Set Up Meta CAPI (Overview)

There are three main setup methods:

1. Native Platform Integration (Easiest)

Shopify, WooCommerce, and other major platforms offer built-in or plugin-based CAPI integrations. These require minimal technical knowledge but offer less control over data quality.

2. Via Google Tag Manager (Server-Side GTM)

Server-Side Google Tag Manager acts as a CAPI proxy. Your website sends events to your GTM server container, which forwards them to Meta CAPI. This adds flexibility without requiring custom code.

3. Direct API Integration (Most Powerful)

Build a custom server-side integration using Meta’s Graph API. Full control over every parameter, deduplication logic, and error handling. Recommended for brands with developer resources.

At WebDataSolve, we typically implement server-side CAPI via direct API integration, achieving Event Match Quality scores of 8.5–9.5 for eCommerce clients. Book a free audit to see what your current score is and how to improve it.

Common Meta CAPI Mistakes to Avoid

• Missing deduplication: Sending events via both Pixel and CAPI without an event_id causes double-counting. Always set a unique event_id on both.
• Sending raw PII: Never send unhashed emails or phone numbers. Meta requires SHA-256 hashing.
• Missing phone format: Phone must include country code, no spaces or dashes (e.g., +8801712345678).
• Not sending IP + User-Agent: These supporting parameters improve match quality even without other PII.
• Ignoring test events: Always validate your integration using Meta’s Test Events tool before going live.

Frequently Asked Questions About Meta CAPI

Does Meta CAPI replace the Meta Pixel?

No. You should run both together. The Pixel handles browser-side signals (like ViewContent, AddToCart for users who haven’t purchased yet). CAPI handles high-value conversion events server-side. Together they give Meta the most complete picture of your funnel.

Is Meta CAPI GDPR compliant?

CAPI itself is a technical tool — compliance depends on how you implement it. You must have a legal basis for processing customer data (typically consent or legitimate interest) and disclose this in your privacy policy. For EU audiences, ensure you only send data for users who have consented to marketing tracking.

How long does it take to see results after setting up CAPI?

Event Match Quality improves within 24-48 hours of setup. Ad performance improvements (lower CPA, better ROAS) typically appear within 1-2 weeks as Meta’s algorithm relearns with better data. Some advertisers see immediate uplift if they were previously missing significant iOS conversion data.

How much does Meta CAPI cost?

Meta CAPI itself is free — it’s a Meta API. You pay only for ad spend, as usual. However, implementation requires developer time or a specialist service. Server-Side GTM has hosting costs (~$50-100/month). Direct API integration is a one-time development investment.

{“@context”:”https://schema.org”,”@type”:”FAQPage”,”mainEntity”:[{“@type”:”Question”,”name”:”What is Meta CAPI?”,”acceptedAnswer”:{“@type”:”Answer”,”text”:”Meta CAPI (Conversions API) is a server-side tracking solution that sends conversion data directly from your server to Meta, bypassing browser limitations, ad blockers, and iOS privacy restrictions.”}},{“@type”:”Question”,”name”:”Does Meta CAPI replace the Meta Pixel?”,”acceptedAnswer”:{“@type”:”Answer”,”text”:”No. Best practice is to run both together with deduplication. The Pixel tracks browser-side behavior; CAPI sends server-side conversion events. Together they maximise attribution coverage.”}},{“@type”:”Question”,”name”:”How much does Meta CAPI cost?”,”acceptedAnswer”:{“@type”:”Answer”,”text”:”Meta CAPI is free to use. Costs come from implementation (developer time or specialist service) and optionally server-side GTM hosting ($50-100/month).”}},{“@type”:”Question”,”name”:”How long does Meta CAPI take to show results?”,”acceptedAnswer”:{“@type”:”Answer”,”text”:”Event Match Quality improves within 24-48 hours. Ad performance improvements (lower CPA, better ROAS) typically appear within 1-2 weeks as Meta’s algorithm relearns.”}}]} {“@context”:”https://schema.org”,”@type”:”Article”,”headline”:”What is Meta CAPI? Complete Guide for eCommerce Brands”,”description”:”A complete guide to Meta CAPI (Conversions API) — what it is, how it works, who needs it, and how to set it up for eCommerce brands in 2026.”,”datePublished”:”2026-06-24″,”dateModified”:”2026-06-24″,”author”:{“@type”:”Person”,”name”:”Saifur Rahman”,”url”:”https://webdatasolve.com/”},”publisher”:{“@type”:”Organization”,”name”:”WebDataSolve”,”logo”:{“@type”:”ImageObject”,”url”:”https://webdatasolve.com/wp-content/uploads/2026/06/saifur-photo.webp”}}}

Related guides: How to Improve Meta Event Match Quality | Meta Pixel vs Conversions API | Meta CAPI Setup for Shopify

Want this done for you? See our Meta Pixel + Conversions API setup service, or read real tracking fixes in our case studies.