Status · Open to roles and freelance
Tracking and measurement

Meta Conversions API setup checklist for Indian advertisers

If your Meta campaigns only learn from browser events, the best leads, sales and CRM stages may never reach the algorithm, so here is a six-step checklist to fix that.

By Prince Sharma16 Oct 20266 min read

Why the Pixel alone leaves gaps

Meta describes the Conversions API (CAPI) as a way to connect your own marketing data, such as website, app, CRM and offline events, to its systems. Meta says the goal is better ad targeting, a lower cost per result and the ability to measure outcomes.

Meta also recommends a redundant setup: send the same events through both the Meta Pixel and the Conversions API. That way a network problem or a page error does not cost you a conversion.

For lead generation and D2C brands in India, the real outcome often happens after the click: a form fill, a call, a WhatsApp chat or an order confirmation. Server-side events let you report those moments instead of only the page view.

Step 1: Choose a few events that match the business

Start small. Pick the two or three events that map to money: Lead or Purchase, plus one later-stage event such as a qualified lead. Use the standard event names Meta understands, and keep the names identical in the Pixel and on the server.

A practical judgement call for brands with many cash-on-delivery orders: decide whether a Purchase fires at order placement or at confirmation, and keep that rule fixed so reporting stays comparable over time.

Step 2: Send the required fields

For website events, Meta requires an action source, the event source URL and the client user agent. Each event also carries a name and a Unix timestamp for when it actually happened.

Timing matters. Meta says events can be up to seven days old, but if any single event in a request is older than that, the whole request fails. Meta advises sending events as they happen, ideally within an hour. A request can hold up to 1,000 events, and one invalid event causes the entire batch to be rejected, so validate before you send.

Step 3: Add customer information and hash it correctly

Meta uses customer information parameters to match a server event to a person on its platform. Only matched events can be used for attribution and ad delivery optimisation. Unmatched events still support basic measurement. Meta lists email, phone, first name, last name and IP address among the high-quality parameters, and says sending more of them improves Event Match Quality, which Events Manager scores out of 10 for web events.

Hashing rules to get right:

  • Hash email, phone, names, city and similar fields with SHA-256.
  • Email: trim spaces and use lowercase before hashing.
  • Phone: remove symbols, letters and leading zeros, and include the country code. For an Indian mobile number that means the digits start with 91, with no plus sign and no zero in front.
  • Do not hash the IP address, user agent, or the fbp and fbc cookie values. Send them as they are.
  • Refresh fbp and fbc values regularly, because they can change.

Indian forms often collect a mobile number more reliably than an email, so a clean, correctly formatted phone field can make a real difference to match rates.

Step 4: Deduplicate Pixel and server events

If the same purchase arrives from both the browser and the server, Meta needs to know it is one event. The recommended method is to send the same event name and the same event ID from both sources. Generate a unique ID for each event and pass it as eventID in the Pixel call and as event_id in the server payload.

Meta says matching events are deduplicated within 48 hours of the first event with that ID, and the first one received is generally the one kept. Events that come from only one source are not deduplicated, so a repeated server event stays repeated.

Step 5: Test before you trust it

Use the Test Events tool in Events Manager. It gives you a test code that you add to your request as test_event_code, so you can watch events arrive. Meta notes that test events are not dropped and still flow into Events Manager, so remove the test code from production payloads. Meta says you should be able to verify events within about 20 minutes of sending them.

Check three things: events appear from both sources, duplicates are merged, and Event Match Quality is moving up as you add parameters.

Step 6: Check your consent notice

India's Digital Personal Data Protection Rules were notified in November 2025. The government's release describes an 18-month phased compliance period, and says each data fiduciary must give a clear, easy-to-understand consent notice that states the specific purpose of collecting and using personal data.

If your website and forms send customer details to ad platforms, make sure your notice says so in plain language. This is not legal advice, so confirm the details with a qualified lawyer.

Quick checklist

  • Two or three business-critical events chosen and named identically in Pixel and server
  • Action source, event source URL and client user agent sent on every website event
  • Events sent in near real time, none older than seven days
  • Email and phone normalised and hashed with SHA-256; IP, user agent, fbp and fbc left unhashed
  • Indian phone numbers sent with the 91 country code and no leading zero
  • Same event name and unique event ID in both Pixel and server payloads
  • Test Events run, then the test code removed from production
  • Event Match Quality reviewed in Events Manager
  • Consent notice reviewed against current data practices

Frequently asked questions

Do I still need the Meta Pixel if I use the Conversions API?

Meta recommends using both. The Pixel and the server send the same events, and deduplication stops them being counted twice.

What happens if I skip the event ID?

Meta deduplicates most reliably when the event name and event ID match across both sources. Meta also describes an alternative method that uses fbp and external ID.

How do I know it is working?

Open Test Events in Events Manager, send a test event with the test code, and confirm it appears. Then watch Event Match Quality and duplicate handling for a few days. Remove the test code before going live.

Does the DPDP law change how I can use CAPI?

It raises the bar on clear consent notices and stated purposes, with obligations phased in over 18 months. Review your notice and ask a lawyer how it applies to your business.

Related reading

Sources

Need a second pair of eyes?

I work with foreign brands entering India, Japanese brands in India and Southeast Asia, Indian brands going global, and startups, SaaS and D2C teams. In a previous performance marketing role I managed up to US$80,000 per month across Google, Meta and Microsoft Ads. Past results are not a promise, but they are why I take measurement seriously.

If you would like feedback on your tracking and ad setup, request the free website audit at princesharmaa.com/#audit. I reply within 3 business days.

Get a free website auditEmail help@princesharmaa.comChat on WhatsApp

Connect on LinkedIn ↗

About the author. Prince Sharma is a performance marketing consultant and senior manager with 7+ years across Google, Meta and Microsoft Ads, focused on India and international growth markets. He also leads digital operations for a confidential performance marketing and AEO agency.