Meta Conversions API Setup: Pixel + CAPI Guide for India

If your Meta reports show fewer sales than your Shopify or CRM does, your tracking is probably leaking. Browser-based tracking loses events to ad blockers, privacy settings and slow pages, and Meta's delivery system then optimises on an incomplete picture. The Meta Conversions API is the standard fix.

This guide explains what the Conversions API is, how to set it up next to the Pixel, how deduplication works and how to confirm it is working. It is written for marketing leads and founders who run or review Facebook and Instagram campaigns in India.

What is the Meta Conversions API?

The Meta Conversions API (CAPI) is a server-to-server connection that sends your website, app and CRM events directly to Meta instead of relying on the visitor's browser. Meta documents it in its Conversions API documentation, and the events land in the same dataset the Pixel uses.

The Meta Pixel is a snippet that runs in the browser. CAPI runs on a server you or a partner control, so it can send events even when the Pixel is blocked, and it can add details only your backend knows, such as a confirmed payment or a lead that became a customer.

Why use the Pixel and Conversions API together?

Use both, because each covers the other's blind spots. The Pixel is quick and rich in browser context, while CAPI is more dependable and can carry backend facts.

Meta calls running both a redundant setup. When the same event arrives from both paths, deduplication keeps the count honest.

Which Conversions API setup route should you choose?

Pick the lightest route that sends the events you need. A partner integration suits most stores, and a custom build suits businesses with their own backend or CRM.

These ranges are indicative estimates from project experience, not quotes, and hosting is billed separately by your cloud provider.

How do you set up the Meta Conversions API step by step?

Setup follows the same eight steps whichever route you choose.

1. Audit what you have. List the events fired today, check for duplicate Pixels and note which tool sends them.
2. Choose your events. Start with the ones that drive optimisation: Purchase, Lead, InitiateCheckout, AddToCart and ViewContent, plus a qualified-lead event if sales can feed one back.
3. Open the dataset in Events Manager. Meta now treats the Pixel as a dataset. Confirm you are working in the right business portfolio and ad account.
4. Create access. Generate a system user token or use your partner's login flow, and store the token securely on the server only.
5. Add the server event. Send the event name, time, source URL, action_source and customer details along with an event_id.
6. Pass the same event ID from the Pixel. Generate the ID once, use it as eventID in the browser call and as event_id on the server.
7. Test. Add a test event code in Test Events, complete a real checkout or form and confirm both copies arrive.
8. Go live and monitor. Remove the test code, then watch the diagnostics tab for a week.

Meta's deduplication guide explains the event ID requirement in detail, so share it with your developer before step 5.

How does event deduplication work?

Deduplication means Meta counts a conversion once when the Pixel and the Conversions API both report it. It compares the event name and the event ID, and the events must reach the same dataset within 48 hours of each other.

Three rules prevent most problems:

• Generate the event ID once per action, such as an order number plus event name, and reuse it for every retry.
• Match the strings exactly. A number sent as 12345 on one side and "12345" on the other, or different casing, can break the match.
• Do not rely on email or fbp for deduplication. Those fields help Meta recognise the person, not merge the event.

A healthy account usually shows a share of events reported by both paths, since some people block the Pixel and only the server copy arrives.

What customer data should you send, and how?

Send the identifiers you already collect with permission, because richer data improves how often Meta can match an event to a person. Meta scores this as Event Match Quality, shown in Events Manager.

• Hash before sending: email, phone number, first name, last name, city, state and PIN code, using SHA-256 after trimming and lowercasing as Meta specifies.
• Do not hash: fbp (the browser ID cookie), fbc (the click ID from the ad URL), client IP address and user agent.
• Format phone numbers with the country code, for example 91 for India, and digits only.
• Include value and currency on purchases, using INR consistently, or optimisation and ROAS reporting will be wrong.

For lead ads, a landing page form is a good place to capture fbc and consent together. Our guide to Facebook and Instagram ads cost in India shows why wasted clicks get expensive when lead tracking is weak.

What mistakes break Conversions API tracking?

Most failures come from setup conflicts rather than from Meta. These are the ones we see most often:

• Two server-side senders running at once, such as Shopify's app plus a Gateway, which doubles purchases.
• Missing or mismatched event IDs, so nothing is deduplicated.
• Unhashed personal data, which Meta rejects or flags.
• Server events firing before payment, for example on "order placed" for COD orders that later cancel.
• No value or currency on purchase events.
• Test codes left in production, so live events appear only in Test Events.

If you run Cash on Delivery, decide which event counts as a purchase. Many Indian stores send Purchase on order confirmation and feed back cancellations or returns through a separate process, since Meta's standard events do not track RTO automatically.

How Arham Technology approaches Meta Conversions API setup

Arham Technology treats tracking as part of the ad account, not an afterthought. Under our Facebook and Instagram ads service, the pixel and CAPI work covers:

1. Tracking audit. We list every Pixel, tag and app that sends events, and note duplicates and gaps.
2. Event plan. We agree which events map to real business value, including a qualified-lead or paid-order definition.
3. Implementation. We configure the route that fits your stack, whether a partner app, Gateway or server build.
4. Verification. We test deduplication and review Event Match Quality before campaigns scale.
5. Monitoring. We check diagnostics weekly and document the setup so your team can maintain it.

For stores, the work pairs with Shopify development, and for lead businesses with a tracked landing page. Better signals support, but do not guarantee, lower acquisition costs. Pair them with fresh creative, as covered in our post on Meta ads creative hooks, formats and testing.

What should you do next?

Open Events Manager today and check three things: how many tools send events, whether Test Events shows both browser and server copies, and what your Event Match Quality is for Purchase or Lead. Fix duplicates before you add new events.

If you would like a second pair of eyes, contact Arham Technology with your site platform and recent ad spend, or read about our Facebook and Instagram ads management.