Quick Answer
For accurate Meta Pixel ecommerce setup in India, install the browser Pixel and the server-side Conversions API (CAPI), sending both with one shared deduplication eventID. Pixel alone misses purchases after iOS ad-tracking limits and ad-blockers; CAPI recovers them without double-counting, restoring reliable ROAS.
Why Meta Pixel alone under-reports your sales
The Meta Pixel is a small piece of JavaScript that fires from the shopper's browser when someone views a product, adds to cart, or completes a purchase. It worked well for years. But after Apple's iOS App Tracking Transparency prompt, plus widespread ad-blockers, browser extensions, and dropped connections on patchy tier-2/tier-3 mobile networks, a large share of those browser events never reach Meta. The result: your Ads Manager shows fewer purchases than your order dashboard, reported ROAS looks weak, and Meta's optimisation gets starved of the conversion signals it needs to find buyers.
For an Indian store running COD-heavy traffic on cheap data plans, the browser-only gap is often the difference between a campaign that looks unprofitable and one that is quietly working. You cannot fix a number you cannot see.
How the Conversions API (CAPI) closes the gap
The Conversions API sends the same events from your server instead of (or alongside) the browser. When a Razorpay payment confirms or an order is recorded, your server posts a Purchase event straight to Meta — no browser, no ad-blocker, no dropped tab in between. Server events are far more reliable because they do not depend on the shopper's device finishing the request.
The catch: if both the Pixel and CAPI report the same purchase, Meta could count it twice and inflate your numbers. That is why deduplication matters.
Deduplication: one shared eventID
The fix is simple in principle. Every conversion is stamped with a single, identical eventID (and matching event name) on both the browser Pixel event and the server CAPI event. Meta sees two events with the same eventID, understands they are the same purchase, and keeps only one. You get the reliability of the server signal and the rich browser signals, with zero double-counting.
HOD Media ships this end-to-end: a per-tenant Meta Pixel plus Conversions API, with a shared dedup eventID across browser and server, built into the storefront. You add your Pixel ID and access token once; the store handles ViewContent, AddToCart, InitiateCheckout, and Purchase on both channels automatically. HOD also fires each event to your own per-tenant pixel and a platform-level pixel under the same dedup eventID, so neither view double-counts a sale. Because HOD additionally recovers browser-drop orders through an idempotent Razorpay webhook, purchases that would otherwise vanish still fire a clean, de-duplicated conversion.
Pixel vs Conversions API vs both
| Aspect | Browser Pixel only | CAPI only | Pixel + CAPI + dedup eventID |
|---|---|---|---|
| Survives ad-blockers / iOS limits | No | Yes | Yes |
| Rich browser context (page, device) | Yes | Limited | Yes |
| Captures dropped-connection orders | No | Yes | Yes |
| Risk of double-counting | N/A | N/A | None (deduped) |
| Reported ROAS accuracy | Understated | Better | Most accurate |
Purchase tracking that fixes ROAS
Accurate ROAS depends on Meta receiving every real purchase with its correct rupee value. With HOD, the Purchase event carries the order value in ₹ so your return-on-ad-spend is measured against actual revenue, not a browser-truncated subset. Cleaner Purchase signals also help Meta's optimisation and let you build reliable value-based Lookalike audiences from real buyers.
A few India-native practices to keep the data honest:
- Fire Purchase on payment confirmation, not on the thank-you page load — vital for UPI and card flows where the shopper's tab can close before redirect.
- Decide how to treat COD up front. Cash-on-delivery orders can inflate Purchase counts if a chunk later becomes RTO (return-to-origin); pick a rule and apply it consistently.
- Send the order value net of nothing hidden — keep GST and shipping handling consistent between your store and Meta so ROAS math ties out.
Setup checklist
- Create a Meta Pixel/dataset and generate a Conversions API access token in Events Manager.
- Enter your Pixel ID and token in your storefront settings.
- Confirm both browser and server events arrive for the same test order.
- Verify the shared eventID is deduplicating in Events Manager (events should not show as separate).
- Check that Purchase value is passed in ₹.
On hodmedia.in this is configuration, not code — the per-tenant Pixel and Conversions API, shared dedup eventID, Razorpay checkout with your own keys, and a branded order-tracking page are built in. That means an Indian store owner gets iOS-resilient purchase tracking without hiring a developer to stitch a server integration together, and can trust the ROAS shown in Ads Manager when deciding where to spend the next ₹1,000.
Do I still need the browser Pixel if I set up the Conversions API?
Yes, use both. The browser Pixel captures rich context like the page and device, while the Conversions API sends reliable server-side events that survive ad-blockers and iOS tracking limits. Running both with a shared deduplication eventID gives you the fullest, most accurate picture without double-counting purchases.
What is a dedup eventID and why does it matter?
A dedup eventID is a single identifier stamped on the same conversion sent by both the Pixel and the Conversions API. Meta uses it to recognise the two events as one purchase and count it only once. Without it, sending events from both channels can double-count sales and overstate your ROAS.
How does the Conversions API improve my ROAS reporting in India?
Many browser Pixel events are lost on patchy tier-2 and tier-3 mobile networks, ad-blockers, and iOS limits, so Ads Manager under-reports purchases. The server-side Conversions API sends the Purchase event with its rupee value directly from your server, recovering those missing conversions. That gives Meta accurate revenue data and makes your reported ROAS trustworthy.
Should I track cash-on-delivery orders as Meta purchases?
You can, but decide a consistent rule because COD orders in India often become RTO (return-to-origin) and can inflate your Purchase count. Some stores fire Purchase at order placement and accept some RTO noise; others reconcile later. The key is applying the same logic every time so your ROAS math stays reliable.
Does HOD Media handle the Pixel and Conversions API setup for me?
Yes. HOD Media provides a per-tenant Meta Pixel plus Conversions API with a shared dedup eventID built into the storefront. You add your Pixel ID and access token once, and the store fires deduplicated ViewContent, AddToCart, InitiateCheckout, and Purchase events across browser and server, with order values passed in ₹.