Conversions API CAPI
A method where your servers send conversion events directly to Meta, instead of relying on the browser alone.
In Arabic واجهة التحويلات
What is Conversions API?
The Conversions API, or CAPI, is a way for your systems to send conversion events to Meta straight from the server instead of relying on the visitor's browser alone. When an order is created in the store system, the purchase event goes to Meta from there, so it arrives even if the browser blocks the Pixel.
In most setups CAPI does not replace the Pixel; it runs alongside it. Since the same event can arrive through both, you need a shared event ID so Meta can deduplicate them. Success is measured by the Event Match Quality score in Events Manager, which rises as you send more hashed customer data such as email and phone number.
Why does Conversions API matter in marketing?
It protects you from losing part of your conversions in the browser, so Meta gets a picture closer to reality and your campaigns improve.
- 01
Reduces lost events
Sending from the server is not affected by ad blockers or browser settings the way the Pixel is.
- 02
Improves campaign data
The more complete the events Meta receives, the better its algorithm gets at finding the right customers.
- 03
Allows off-site events
You can send events from your sales or booking system, not only from website pages.
- 04
Needs careful setup
A wrong setup causes duplicate events, so you need a shared event ID and ongoing quality checks.
Worked example
- 1Situation
A clothing store in Tabuk relies on the Meta Pixel and sees that Meta reports fewer orders than the store dashboard.
- 2Data
The store dashboard shows 100 orders a week, while Meta records only 80 through the Pixel.
- 3Calculation
Capture rate = 80 ÷ 100 = 80%. After adding server-side sending, Meta records 95, or 95 ÷ 100 = 95%.
- 4Decision
The store keeps the Pixel, adds the Conversions API with a shared event ID, and checks that the count never exceeds 100 orders.
Common mistakes
No shared event ID
Without a matching event_id between the Pixel and the server, Meta counts the purchase twice and results inflate. Use the order number as the event ID in both.
Sending too little customer data
Sending events with only an IP address lowers match quality. Add email and phone hashed with SHA-256, once you have the customer's consent.
Delayed server sending
Some integrations send events in batches hours later, which weakens their value for optimization. Send in real time where possible and watch event latency in Events Manager.
Frequently asked questions
Does the Conversions API replace the Meta Pixel?
Not in most cases. The Pixel captures browsing behavior like product views easily, and CAPI makes sure key events such as purchases arrive. Running both with deduplication is the setup Meta recommends.
How do I connect the Conversions API to Salla, Zid or Shopify?
Most platforms offer a ready integration from the dashboard or through Meta's official app, usually needing just an access token from Events Manager. Custom-built stores need a code integration or a server container in the tag manager.
What is an acceptable Event Match Quality score?
Meta scores each event out of 10 in Events Manager. There is no single target for everyone, but focus on the purchase event: if Meta suggests adding missing customer parameters, that is your most direct improvement.
Takteek services that help here
The Takteek team sets up the Conversions API alongside the Pixel and checks deduplication and match quality before we use Meta's numbers in budget decisions.
Talk to Takteek
Want to put this to work for your business?
Tell us about your business in four steps and we will come back with a clear plan that starts from your current numbers. The consultation is free.
- A plan built on your numbers
- One team for ads, content and store
- Free consultation, no commitment


