Conversions API Setup
Meta's Conversions API sends purchases from your store's server straight to Meta, alongside the browser pixel. Set up properly, every order reaches Meta once, including cash on delivery and buyers who close the tab early, with email and phone attached so Meta can match the sale to the person its ad reached.
Prices shown are starting points. The final cost depends on the size and scope of your project, and we confirm it in writing before any work begins.
The pixel alone misses a substantial share of conversions. That matters less for reporting than for optimisation: Meta's algorithm learns from the events it receives, so missing events mean it forms a worse model of who buys and spends your budget accordingly.
On Indian stores the gap is usually larger than owners expect. A purchase only reaches Meta when the buyer lands on the thank you page. Cash on delivery buyers who leave early, one-click checkout apps that finish the order elsewhere, ad blockers and Safari each take a slice. On one store we measured, the browser alone caught under half of the day's orders.
Switching on the Conversions API is not the same as fixing it. We regularly find server events still in Meta's test mode, so they never count for delivery, or server events that fire from the same thank you page as the pixel and so miss exactly the orders they were meant to catch. Match quality is the other half: a Purchase without the buyer's email and phone is an order Meta can rarely tie to a person.
Correct implementation requires deduplication: the same conversion arriving from both browser and server must carry a matching event ID, or it is counted twice and every metric becomes untrustworthy in the other direction.
We prove it against your own orders. During rollout we compare Shopify's order count with what Meta received, hour by hour, and you see that table, not a green tick in Events Manager.
Case study
An Indian D2C eyewear brand on Shopify
The problem
The brand sold through a one-click checkout app, with a large share of cash on delivery. Purchases reached Meta only when the buyer finished on the thank you page, so about four in ten orders never arrived. The server events that existed were in test mode, an old domain was still feeding the pixel, and almost no Purchase carried an email.
What we did
Every order is now sent to Meta from the store the moment Shopify records it, with the buyer's details, and the browser and server share one order id so Meta counts each order once. Test mode was switched off and the old domain blocked. We checked Shopify against Meta every half hour while it rolled out, and every step had a one click way back.
The result
From the first full day, every Shopify order reached Meta. Over one seven hour window Shopify recorded 78 orders and Meta received 78 from the store; the browser alone caught 35. We did not promise more sales, and we do not here. Meta now learns from every real order.
What's included
- Conversions API integration for your platform
- Event deduplication with matching event IDs
- Customer information parameters for match quality
- Event Match Quality monitoring and improvement
- Purchase, lead and custom event coverage
- Consent-compliant configuration
- Before-and-after event volume comparison
Questions people actually ask
Will CAPI double-count my conversions?
Only if deduplication is set up incorrectly. Browser and server events must share an event ID so Meta recognises them as the same conversion. Getting this wrong is the most common implementation error and it inflates every number.
What is Event Match Quality and why does it matter?
It scores how well Meta can match your events to real users, based on the customer parameters you send: email, phone, name, location, all hashed. Higher match quality means better attribution and better optimisation. Below about 6 out of 10 is worth fixing.
Does Shopify have this built in?
Shopify's Meta channel provides a basic CAPI integration that covers standard events. It works for simple stores. Custom events, better parameter coverage and higher match quality generally need a dedicated implementation.
We use Shopflo, GoKwik or Shiprocket checkout. Does the Conversions API still work?
Yes, and that is where it matters most. Those checkouts finish the order outside your theme, so the pixel often never sees it. We send the order from the store itself, so the checkout app no longer decides what Meta receives.
Will cash on delivery orders reach Meta?
Yes. We send every order Shopify records, prepaid or cash on delivery. If your team cancels many orders later, we discuss how to handle them before going live.
How do I know it is working?
We show you Shopify orders against Meta Purchase events by hour and by day, plus the match score and which buyer details are present. If a number drifts during rollout, we see it within half an hour.

