If you're running Meta Ads in India without Conversions API (CAPI), you're optimising on incomplete data. This guide covers everything you need to know to set up CAPI for your Indian business — from the simplest method to the most advanced.
What Is Conversions API and Why Do You Need It?
Meta Conversions API (CAPI) is a server-side tracking tool that sends your conversion events (form submissions, purchases, calls) directly from your server to Meta — bypassing the browser entirely. This is different from the Meta Pixel, which runs in the browser and is blocked by iOS privacy features and ad blockers.
Without CAPI, Meta's algorithm is making bidding and targeting decisions based on 45–65% of your actual conversion data. The rest is invisible. This means your campaigns are systematically underoptimised, and your CPL is artificially inflated.
The iOS 14+ Problem: Why Your Pixel Alone Isn't Enough
Apple's App Tracking Transparency (ATT) framework, introduced in iOS 14.5, requires users to opt-in to cross-app tracking. In India, opt-in rates hover around 25–35% — meaning 65–75% of iPhone users block your Pixel from tracking them. Given that iPhone users in India represent a disproportionately high-income, high-intent demographic, this is a serious data gap.
CAPI solves this by sending data server-side — it's not affected by what happens in the browser or app. The Pixel + CAPI combination gives you the most complete picture: browser-tracked events from users who allow it, plus server-side events for everyone else. With proper deduplication, you avoid double-counting.
4 CAPI Setup Methods Compared
| Method | Best For | Setup Time | Technical Skill | Cost |
|---|---|---|---|---|
| Native CAPI (Meta) | WordPress, Shopify | 2–4 hours | Low | Free |
| CAPI via GTM Server | Any website with GTM | 4–8 hours | Medium | Free–₹3,000/mo |
| CAPI via CRM | Zoho, LeadSquared, Kylas | 1–2 days | Medium | CRM plan |
| Custom API Dev | Custom-built sites | 3–5 days | High | ₹20,000–₹80,000 |
GTM Setup: Step-by-Step (Most Popular Method in India)
Google Tag Manager Server-Side CAPI is the most widely recommended method for Indian businesses. It doesn't require a developer and works with any website that has GTM installed.
Create a Server-Side GTM Container
Go to tagmanager.google.com → Create new container → Select "Server" as the target platform. You'll get a server container URL.
Deploy a Tagging Server
Meta recommends using Google Cloud Run or App Engine for your tagging server. For most Indian SMBs, the manual setup costs ₹500–₹2,000/month. Stape.io is a popular managed option (starts at $10/month).
Add Meta CAPI Client to Server Container
In your server GTM container, add the Meta Conversion API tag. Enter your Pixel ID and Access Token (get from Meta Events Manager → Settings → Conversions API).
Configure Event Mapping
Map your website events (Lead, Purchase, Contact) to Meta standard events. Set up deduplication by ensuring event_id matches between Pixel and CAPI sends for the same event.
Test in Events Manager
Go to Meta Events Manager → Test Events. Submit a test form or purchase on your site. You should see both a Pixel event and a Server event — with "Deduplicated" label if set up correctly.
Indian CRM Integrations for CAPI
Many Indian real estate and service businesses use CRMs to manage leads. These CRMs can send conversion data directly to Meta via CAPI — no code required.
| CRM | CAPI Integration | Setup Difficulty | Notes |
|---|---|---|---|
| LeadSquared | Native CAPI connector | Low | Most popular in Indian real estate |
| Kylas CRM | Native Meta integration | Low | Built for Indian SMBs |
| Zoho CRM | Via Zapier or native | Medium | Zapier adds ₹2,000–₹5,000/mo cost |
| Salesforce | Via Meta partner connector | High | Enterprise only |
| Custom WhatsApp CRM | Manual API or webhook | High | Needs developer |
CRM-based CAPI is especially powerful because it can send downstream events — not just "lead submitted" but "lead qualified," "site visit booked," and even "deal closed." This lets Meta optimise for customers who actually convert, not just leads who submit a form.
Testing and Verifying Your CAPI Setup
After setup, verify everything is working correctly:
- Open Meta Events Manager → your Pixel → Overview tab
- Check "Active" status for each event (Lead, Purchase, etc.)
- Click into any event → check "Connection Method" — it should show both "Browser" and "Server"
- Check "Event Match Quality" score — aim for 7.0+ (ideal: 8.0+)
- Check "Deduplication Rate" — should show a small % of events being deduplicated (this is correct behaviour)
Expected Impact on CPL After CAPI Setup
| Metric | Before CAPI | After CAPI (2–4 weeks) |
|---|---|---|
| Conversions Tracked | 45–65% of actual | 85–95% of actual |
| Event Match Quality | 3–5 (poor) | 7–9 (excellent) |
| CPL (reported) | Higher (inflated) | Drops 20–45% |
| ROAS (reported) | Lower (underreported) | Increases 30–60% |
| Algorithm optimisation | Suboptimal | Full data-driven |
Need help setting up CAPI for your website or CRM?
Our team has set up CAPI for 25+ Indian businesses. We handle the full technical setup as part of campaign management.