Key takeaways
- The Meta Conversions API sends conversion events from a server to Meta; Meta recommends running it alongside the Pixel and sharing the same events through both.
- Deduplication needs the same event_name and a matching event_id on the browser and server copies, received within 48 hours of each other.
- Event Match Quality is a 0 to 10 score for website server events; email and click ID carry the highest priority among customer information parameters.
- Shopify and WooCommerce stores can switch on the Conversions API through official integrations; lead-gen brands get the most from Conversions API for CRM.
- Under India's DPDP Act, consent must be free, specific, informed and withdrawable as easily as it was given, so the consent flow belongs in the setup plan.
The Meta Conversions API (CAPI) is a server-to-server connection that sends website, app, offline and CRM events to Meta, so conversions still reach the ad system when a browser blocks or drops the Meta Pixel. A correct setup in 2027 runs the meta conversions api next to the Pixel, deduplicates the two with a shared event_id, and sends enough hashed customer information for a strong Event Match Quality score. This guide covers each setup path for Shopify, WordPress and lead-gen brands in India, how to test it, and where the DPDP Act applies.
What is the Meta Conversions API, and how is it different from the Pixel?
The Meta Pixel is JavaScript that runs in the visitor's browser. The Conversions API is a POST request from the business's server (or a platform acting for it) to Meta's /events edge at graph.facebook.com/{API_VERSION}/{PIXEL_ID}/events. Meta's Business Help Centre calls running both with the same events a "redundant setup" and says the Conversions API can capture website events the Pixel misses because of network issues or page loading errors.
| Point | Meta Pixel | Conversions API |
|---|---|---|
| Where it runs | Visitor's browser | Server, platform or cloud gateway |
| Affected by ad blockers | Yes | No, per Shopify's data-sharing documentation |
| Events it can send | Website events | Website, app, physical store, CRM and business messaging events |
| IP address and user agent | Added automatically | Must be sent manually (client_ip_address, client_user_agent) |
| Timing | Real time | event_time up to 7 days in the past; physical store events within 62 days |
| Batching | Not applicable | Up to 1,000 events per request |
Meta's developer documentation recommends sending events as soon as they occur, ideally within an hour, even though the API accepts older timestamps. If any event_time in a request is more than 7 days old, Meta returns an error for the whole request and processes none of the events. Meta's help article on best practices sets a target of a 75% event coverage ratio of Conversions API events to Pixel events.

How does deduplication with event_id work?
When the same purchase arrives from the browser and the server, Meta needs to know it is one purchase, not two. Meta's recommended method uses two keys:
- the Pixel's eventID must match the Conversions API's event_id; and
- the Pixel's event name must match the Conversions API's event_name.
On the Pixel side, eventID is the fourth argument of the track call, for example fbq('track', 'Purchase', {value: 1499, currency: 'INR'}, {eventID: 'ORDER-10421'}). On the server side, the same order number goes in event_id. Meta's server event documentation suggests an order number or transaction ID for purchases, and a random number shared between both copies for events without a natural ID.
Meta discards the later copy when it finds the same pair sent to the same Pixel within 48 hours. When the two copies do not differ meaningfully in content, Meta says it generally keeps the one received first. A fallback method compares event_name with fbp or external_id, but Meta notes it generally works only when the browser event arrives first, so event_id remains the reliable route.
Use the platform order ID as event_id for Purchase, never a value generated separately in the browser and on the server. Two independent random numbers will never match, and every order then counts twice in Ads Manager while Events Manager shows nothing wrong at a glance.
What is Event Match Quality, and which customer parameters matter?
Meta describes Event Match Quality (EMQ) as a 0 to 10 score of how well the customer information sent with a server event can match events to Meta accounts. It is available for website events sent through the Conversions API with action_source set to website, and it uses the last 48 hours of data, so events must flow regularly for the score to stay current. Meta's help centre ranks the parameters by priority:
| Priority | Parameters (API key) | Hashing |
|---|---|---|
| High | Email (em), click ID (fbc) | em: SHA-256 after trimming and lowercasing; fbc: do not hash |
| Medium | Phone (ph), external ID (external_id), browser ID (fbp), country, date of birth (db), Facebook Login ID | ph, country, db: hash; external_id: hashing recommended; fbp and fb_login_id: do not hash |
| Low | First name (fn), surname (ln), city (ct), postcode (zp), lead ID | fn, ln, ct, zp: hash; lead_id: do not hash |
Three formatting rules matter most for Indian customer data. Phone numbers must include the country code, so a Mumbai mobile is sent as 91 followed by the ten digits, with symbols and leading zeros removed, then hashed. Country is the lowercase ISO code "in", hashed, and Meta says to send it even when every customer is in one country. And client_ip_address and client_user_agent must never be hashed; the user agent, together with event_source_url, is required for every website event sent through the API.
For click-to-WhatsApp campaigns, which many Indian D2C and real estate brands run, Meta's customer information parameters include ctwa_clid, the click ID generated for ads that click to WhatsApp. Storing it against the chat lets later sales from that chat be matched to the ad.

Which setup path fits the business?
Meta's comparison of setup options lists a Meta-enabled Conversions API (web only, free, one click, sends the same events as the Pixel and deduplicates them automatically), direct integration (2 to 4 weeks for a new build, developer needed), and partner integrations. Meta lists direct integration as supporting web, app, offline, CRM and business messaging events, while what a partner integration can send depends on the partner. The decision table below maps those options to common Indian stacks.
| If the business runs on | Use | Why |
|---|---|---|
| Shopify | Facebook & Instagram app, Enhanced or Maximum data sharing | Native, no code; Standard is Pixel only |
| WooCommerce | Meta for WooCommerce plugin | Official Meta plugin with Conversions API support |
| WordPress lead site | Meta pixel for WordPress plugin | Official plugin; includes Conversions API support |
| Any website, no developer, web events only | Meta-enabled Conversions API, or Conversions API Gateway for more control | Free or cloud-cost only, no code |
| Custom stack, COD delivery events, app or offline sales | Direct integration | Full control of events and parameters |
| Lead ads with a CRM (real estate, education, finance) | Conversions API for CRM, direct or through a CRM partner | Sends lead stages back for qualified-lead optimisation |
Meta CAPI on Shopify
In the Shopify admin, go to Sales channels > Facebook & Instagram > Settings > Data sharing settings, turn on customer data sharing, and choose a level under Choose level. Shopify's help page explains that Standard uses only the Pixel, while Enhanced and Maximum add the Conversions API, which sends the purchase event server to server and shares name, location, email and phone for matching; Maximum also applies Meta's latest advertising technology. Shopify notes that order-value events use the order's total price, including duties, taxes and discounts, so the reported value includes GST. Do not add a second server-side purchase integration on top, or purchases will double count unless both use the same event_id.
WordPress and WooCommerce
Meta publishes two official plugins on WordPress.org: Meta for WooCommerce (version 3.7.8, 400,000+ active installations in October 2026), which installs the Pixel, syncs the catalogue and is tagged for the Conversions API, and Meta pixel for WordPress (version 5.2.2), which installs the Pixel with Conversions API support for lead and content sites. For Meta pixel for WordPress, setup runs through the Facebook Business Extension flow, where the site owner agrees to share an access token with the site. Test plugin updates on a staging copy first, since a conflict on a busy store affects checkout.
Conversions API Gateway
The Gateway is a self-serve option configured in Events Manager that runs on the business's own cloud account. In Events Manager, open the Settings tab, find "Set up with Conversions API Gateway" and click Get started; Meta's setup guide then hands over to an AWS quick-create stack, which takes about 30 to 40 minutes. The CapigSetupURL in the stack outputs opens the Gateway admin, where data can take 5 minutes to 2 hours to appear. Meta says the Gateway generates the event_id deduplication key automatically, supports several pixels and domains, recommends a custom domain, and costs only the cloud resource or partner fees.
Direct server integration
For a direct build, generate a token in Events Manager: choose the pixel, open the Settings tab, and in the Conversions API section click Generate access token under Set up manually (the link is visible only to users with developer privileges). Each event needs event_name, event_time, user_data and action_source; website events also need event_source_url and client_user_agent. This is the route for COD delivery events and for stores whose checkout runs on a custom stack.
Conversions API for CRM and offline leads
For lead-gen brands, the event that matters is not the form fill but what happens after it. Conversions API for CRM sends CRM stages back to Meta, matched on the Meta lead ID where the CRM has it. Meta's fit guidelines are at least 200 leads a month, a target stage that happens within 28 days of the lead, a target stage conversion rate between 1% and 40%, and uploads at least once a day; for best results the CRM should store the 15 to 17 digit Meta lead ID, with click ID, phone or email as the fallback. Since April 2026, Meta no longer allows new campaigns to use the "Maximize number of qualified leads" goal without a Conversions API integration, and existing campaigns are affected from August 2026, according to Meta's Business Help Centre page on performance goals for lead ads. The real estate Facebook ads guide covers which CRM stage to send.
How is the setup tested in Events Manager?
- Open Events Manager > Data Sources > the pixel > Test Events. The tool shows a test ID.
- Send server events with that ID in the test_event_code parameter, and browse the site in another tab to fire Pixel events.
- Check that each server event appears with the expected parameters; Meta says events should be verifiable within about 20 minutes.
- Place a test order, then in Events Manager select the dataset, click View details on Purchase and check the Event deduplication tab to confirm the browser and server copies are deduplicated rather than counted twice.
- Remove test_event_code before production. Meta warns that events sent with it are not dropped: they flow into Events Manager and are used for targeting and ads measurement.
- After 48 hours of live traffic, read the Event matching tab on Purchase and follow the recommended actions Events Manager lists.
Illustrative examples: what the numbers look like
Illustrative example: event coverage and reported ROAS
All figures are assumptions. A Shopify brand spends ₹5,00,000 in a month. Its store records 1,600 orders worth ₹20,00,000.
- Pixel only: Ads Manager attributes 1,000 purchases worth ₹12,50,000. Reported ROAS = ₹12,50,000 ÷ ₹5,00,000 = 2.5.
- After moving to Enhanced data sharing, server Purchase events received: 1,380 against 1,500 Pixel purchases. Coverage = 1,380 ÷ 1,500 = 92%, above Meta's 75% target.
- If attributed purchases rise to 1,150 worth ₹14,37,500, reported ROAS = ₹14,37,500 ÷ ₹5,00,000 = 2.875, about 2.9.
Store revenue did not change; Meta simply sees more of it. Judge the change on store and courier data, and use the ROAS calculator to set the break-even target before reading Ads Manager.
Illustrative example: COD delivered event
All figures are assumptions. A COD-heavy brand spends ₹3,00,000 and records 1,000 placed orders at ₹300 per purchase. Of those, 720 are delivered, so cost per delivered order is ₹3,00,000 ÷ 720 = ₹416.67. If the courier status reaches the store's server late and 25% of delivered events are sent more than 7 days after their delivery time, Meta rejects them, so only 720 × 0.75 = 540 delivered events count. That gap is why the delivered event needs a fast courier webhook.
What does the DPDP Act mean for the Conversions API in India?
The Digital Personal Data Protection Act, 2023 governs the customer emails and phone numbers a business collects at checkout or on a lead form, which are the same details it hashes and sends to Meta. Section 6(1) says consent must be "free, specific, informed, unconditional and unambiguous with a clear affirmative action" and limited to the data needed for the stated purpose. Section 6(3) requires consent requests in clear and plain language, with an option to read them in English or a language in the Eighth Schedule. Section 6(4) gives the right to withdraw consent at any time, as easily as it was given. The DPDP Rules, 2025 were notified in November 2025 with an eighteen-month phased compliance period, and they require a separate, clear consent notice explaining the purpose. The government's summary lists penalties of up to ₹250 crore for failing to maintain reasonable security safeguards, up to ₹200 crore each for failing to notify a breach or breaching obligations on children's data, and up to ₹50 crore for any other violation.
Meta's own help centre says its Business Tools Terms require lawful rights to collect, use and share data and require contact information to be hashed. Shopify's help page puts the same duty on the merchant: data sharing is a choice, and the store's privacy policy must explain it. In practice that means a plain-language notice at checkout and on lead forms, a consent record per customer, no events for people who withdraw, and no parameters beyond those needed for matching. This is general information, not legal advice; check the current MeitY notification on compliance dates before relying on one.
How do COD brands send delivered orders as a custom event?
For brands with high COD and RTO, Purchase on the thank-you page rewards the algorithm for orders that may never be delivered. The fix covered in the Meta ads playbook is a separate custom event, such as DeliveredPurchase, sent through the Conversions API when the courier marks the order delivered.
- Store fbc, fbp, client_user_agent, the event_source_url and the hashed email and phone at checkout, because the courier webhook has none of them.
- Send action_source "website", value and currency "INR" on every delivered event, with event_time set to the delivery time and the event sent within 7 days of it.
- Use a new event name, never Purchase, so it neither double counts nor deduplicates against checkout.
- Build a custom conversion on it in Events Manager (Meta allows 100 per ad account) and report on it next to Purchase for two to four weeks before optimising on it.
Meta's server event parameters also include original_event_data for delayed events that should be associated with an earlier acquisition event. The RTO guide covers the delivery data the event depends on.
Common mistakes with the Conversions API
- No event_id, or different IDs on each side. Purchases double count. Fix: use the order ID on both the Pixel and the server event.
- Two server integrations at once. A Shopify app at Maximum plus a GTM server container both send Purchase. Fix: keep one server source per event, or share event_id across both.
- Phone numbers without 91. Indian numbers sent as ten digits match poorly. Fix: normalise to country code plus number, then hash.
- Hashing the wrong fields. Hashed IP, user agent, fbc or fbp values cannot be used. Fix: hash only contact fields such as em, ph, fn, ln, ct, zp and country.
- Leaving test_event_code in production. Fix: remove it after testing; test events still count in measurement.
- Delivered events with action_source "system_generated". They get no Event Match Quality score. Fix: send them as website events with the stored checkout parameters.
- Treating consent as a cookie banner only. Fix: collect DPDP-style consent for the purpose of ad measurement, record it, and stop sending events for people who withdraw.
What to do this week
- Events Manager > select the dataset > Purchase or Lead > View details > Event coverage: compare server events with Pixel events against the 75% coverage target.
- Events Manager > Data Sources > pixel > Test Events: send a test order with test_event_code and confirm deduplication.
- Shopify admin > Sales channels > Facebook & Instagram > Settings > Data sharing settings: confirm the level is Enhanced or Maximum, not Standard.
- WordPress > Plugins: confirm the Meta for WooCommerce or Meta pixel for WordPress plugin is current, and test the update on staging first.
- Events Manager > Purchase > View details > Event matching: note the Event Match Quality score and add email, phone with 91, external_id and fbc where missing.
- Checkout and lead forms: add a plain-language consent notice and a way to withdraw, and log consent per customer.
Write a one-page event map before touching any setting: each event, its source (Pixel, app, server, CRM), its event_id rule and the parameters it carries. A shared map stops two people from adding overlapping integrations that double count the same event. For a managed setup across Meta tracking and campaigns, see Meta ads management.
Frequently asked questions
Sources (checked October 2026): Meta for Developers: Get started with the Conversions API; Meta for Developers: Using the API and Test Events; Meta for Developers: Handling duplicate Pixel and Conversions API events; Meta for Developers: Server event parameters; Meta for Developers: Customer information parameters; Meta for Developers: Conversions API Gateway; Meta for Developers: Conversions API Gateway setup guide; Meta for Developers: Conversions API for CRM; Meta Business Help Centre: About performance goals for lead ads; Meta Business Help Centre: Compare Conversions API setup options; Meta Business Help Centre: Best practices for Conversions API; Meta Business Help Centre: About event match quality; Meta Business Help Centre: View server event details in Events Manager; Shopify Help Center: Facebook data sharing; WordPress.org: Meta for WooCommerce; WordPress.org: Meta pixel for WordPress; MeitY: Digital Personal Data Protection Act, 2023; PIB: Government notifies DPDP Rules (November 2025); PIB: DPDP Rules, 2025 notified (backgrounder)



