On this page
The Meta Conversions API integration sends conversion events (Lead, Purchase) from VGraple CRM to Meta for conversations that began from a click-to-WhatsApp ad, so Ads Manager can attribute revenue to the right ad and optimise delivery toward people who buy rather than people who merely start a chat. It is native: VGraple CRM posts events server-side to your dataset with the click ID Meta attached to the conversation.
What syncs
| Data | Direction | Timing |
|---|---|---|
| Lead event when a lead is created from an ad-originated conversation | VGraple CRM to Meta | Within seconds |
| Purchase event when a payment link is paid or an order with value is recorded | VGraple CRM to Meta | Within seconds |
| Click ID (ctwa_clid), hashed phone, event value and currency | VGraple CRM to Meta | With each event |
| Test Purchase event | VGraple CRM to Meta | On demand from Send Test Event |
| Event delivery status and last error | Meta to VGraple CRM | Shown on the settings card |
Setup
- In Meta Events Manager (business.facebook.com/events_manager), create or open a dataset and copy the Dataset ID.
- In Business Manager, create or use a system user with ads_management permission and generate an access token.
- In VGraple CRM go to Settings, then Integrations, then Meta Conversion Tracking.
- Paste the Dataset ID into Dataset ID and the token into Access Token (it shows as saved and masked).
- Toggle Enabled on and click Save.
- Click Send Test Event. An INR 1 test Purchase is posted; check Events Manager's Test Events view, optionally using a Test Event Code pasted into VGraple CRM.
- Run a click-to-WhatsApp campaign; leads and payments from those conversations now appear in Ads Manager as conversions.
Who uses it
Any business spending on click-to-WhatsApp ads: real estate developers, coaching institutes, clinics, D2C brands, travel agencies. The integration matters most once monthly ad spend is large enough that optimising for buyers rather than chats changes the cost per sale, which in practice is anything above a few thousand rupees a day.
How events are matched
Each conversation that starts from a click-to-WhatsApp ad carries a click ID in Meta's referral data. VGraple CRM stores it on the conversation and the lead. When a Lead or Purchase event is recorded, the event is posted to your dataset with that click ID, the hashed phone number, the value and currency, and a timestamp. Meta matches it to the ad click and attributes the conversion to the campaign, ad set and ad. Because the match is by click ID rather than by pixel cookie, it works even though the customer never visited your website.
What you see in Ads Manager
Within minutes of a test event, Events Manager shows the event under your dataset; within a day, Ads Manager's columns for Leads and Purchases from the dataset populate for click-to-WhatsApp campaigns, and you can switch the campaign's optimisation goal to the conversion event once Meta has seen enough of them (usually a few dozen). VGraple CRM's own revenue report by ad remains the source for actual rupees; Ads Manager shows Meta's modelled attribution.
Three recipes
- Click-to-WhatsApp ad -> qualifier flow -> lead created -> Lead event to Meta. Meta starts optimising toward people who complete the qualifier.
- Ad conversation -> payment link paid -> Purchase event with value -> ROAS in Ads Manager. Revenue tracking in VGraple CRM and Ads Manager now agree.
- Two ad sets, one number -> compare cost per Purchase by ad set in Ads Manager, and revenue by ad in VGraple CRM. Kill the ad set that starts chats but not sales.
Limits and gotchas
- Only click-to-WhatsApp conversations carry a click ID; organic, QR and Lead Ad conversations are not attributed through CAPI (Lead Ads have their own attribution in Ads Manager).
- Owners only: the settings are secrets.
- Events are matched within Meta's attribution window (up to 7 days after the click by default).
- The access token must belong to a system user with ads_management on the same portfolio as the dataset; a token from a different business fails with an error shown on the card.
- CAPI does not send message content, and hashed identifiers follow Meta's specification.
The Conversions API guide covers event mapping and testing.