How to Send Purchase Value from Your CRM to Meta
How to send the deal value of a converted lead from your CRM to Meta as a Purchase event: what counts as value for a lead business, the right number and currency format, GST, late deals and how to check it worked.
Written by Qualimize Team
Founder, Qualimize
- Published
- Last updated
- Reading time
- 10 min read
Table of contents
- 01 The short answer
- 02 Why value matters more than the event itself
- 03 Decide what counts as value
- 04 Get the format right
- 05 Late deals and the 7-day window
- 06 What if the rep does not know the value?
- 07 Checking that value arrives
- 08 A worked example, end to end
Full article
The short answer
To send purchase value from your CRM to Meta, send a Purchase event through the Conversions API when a lead pays, with custom_data.value set to the amount as a plain number and custom_data.currency set to INR. Meta requires both fields on Purchase. Attach the Meta lead ID and hashed contact details so Meta can tie the revenue to the ad that produced the lead.
The hard part is not the code; it is deciding what number to send and entering it consistently. This guide covers both, with examples from typical Indian lead businesses.
Why value matters more than the event itself
A Purchase event without a real value tells Meta that a sale happened. A Purchase event with a value tells Meta how much the sale was worth. For a business where one customer pays ₹8,000 and another pays ₹2,40,000, that difference is the whole point.
With values flowing, Ads Manager can show conversion value next to spend, so you can compare campaigns on revenue rather than on lead count. A campaign that produces fewer leads but larger deals stops looking like a loser.
It also changes how you talk to your agency or marketer. Instead of arguing about cost per lead, you can look at revenue per rupee of spend by campaign, using numbers your sales team entered.
There is a further benefit for businesses with a wide price range. A clinic that sells both ₹1,500 consultations and ₹60,000 treatment plans, or a travel agency selling weekend trips and international packages, needs Meta to know which leads became the expensive sales. A Purchase event without value treats every sale as equal, and the campaign that brings many small sales looks the same as the one that brings fewer large ones. Value is what separates them.
Decide what counts as value
Lead businesses rarely have a single checkout total, so you need a rule. The best rule is the amount that is actually collected and that reps can enter without guessing. Write it down and apply it to every deal.
Example: a Jaipur coaching centre sends the course fee for the batch the student joined, say ₹38,000. A Pune real estate broker sends their own brokerage, not the property price, because brokerage is their revenue. A developer selling directly might send the booking amount at the booking stage. A travel agency sends the package price, or the margin if it wants Meta to favour profitable trips.
Whatever you choose, be consistent about GST. Either always send amounts including GST or always excluding it. Mixing the two makes comparisons between campaigns quietly wrong by the GST rate, which is 18% on most services.
- Use money actually collected, or contracted, not hoped-for amounts
- Use your revenue (fee, commission, margin), not the customer's total spend elsewhere
- Pick one GST rule and keep it
- If payments come in instalments, decide whether value is the first payment or the full contract
Get the format right
value is a number. Send 38000, not ₹38,000 and not 38,000 with an Indian comma format. currency is a three-letter ISO code; for rupees, that is INR. Meta's Pixel reference lists value and currency as required on Purchase, so a Purchase without them is incomplete and gives Ads Manager no revenue to report.
Send the Purchase event with event_time set to when the payment was recorded, action_source set to system_generated for CRM events, the Meta lead ID unhashed and email and phone hashed after normalising. Use a stable event_id for the purchase, such as the lead ID plus purchase, so a retry does not create a second sale.
If the same customer pays you twice for two separate purchases, those are two Purchase events with two different event IDs. If a payment is refunded, there is no standard refund event to cancel the Purchase; the safest approach is to keep your CRM accurate and accept that Meta's view of that sale will not be reversed.
Late deals and the 7-day window
Meta's server event documentation says event_time can be up to 7 days before you send the event. People sometimes read this as meaning a deal must close within 7 days of the lead. It does not. The window is between the payment being recorded and the event being sent.
Example: a lead comes in on 1 March, and the student pays on 20 April. The CRM sends Purchase on 20 April with event_time of 20 April. That is well within the window. The problem only arises if the rep records the payment on 20 April but the event is sent on 30 April, or if someone back-dates event_time to 1 March.
This is why the value should be entered when the deal closes, not at month end. A rep who enters ten conversions on the last Friday of the month either sends them with the wrong date or, if they are dated to the real payment day, pushes some of them past the window, and Meta rejects any request containing an event that is too old.
What if the rep does not know the value?
Sometimes a status changes to Converted before anyone enters the amount. You then have two choices: wait for the value before sending, or send Purchase with a placeholder.
Waiting keeps your revenue data honest but risks the 7-day window if the value is entered late. Sending a placeholder keeps the signal timely, but inflates or deflates conversion value. If your CRM sends a placeholder, know what it is. Qualimize, for example, sends the recorded deal value and currency when a rep has entered it, and a nominal value of 1 otherwise, never 0, so revenue reports are only meaningful once reps enter deal values.
The practical fix is process, not code: make the amount a required step when a rep marks a deal won, and check weekly that converted leads have values.
A simple weekly check takes five minutes. Filter your CRM to leads converted in the last seven days, sort by deal value, and look at the bottom of the list. Any converted lead with no value, or a value that is obviously a typo such as 38 instead of 38000, is a lead whose revenue Meta will never see correctly. Fixing it within the week keeps the next event inside Meta's window.
Checking that value arrives
In Events Manager, open the Purchase event and look at a recent event's details. You should see value and currency among the parameters received. Then compare a week's total value in Events Manager with the total of converted deals in your CRM for the same week. They will rarely match exactly, because Meta only counts what it can attribute, but a large gap usually means values are missing or formatted wrongly.
In Ads Manager, add the conversion value columns for Purchase to your campaign view. Once a few weeks of data build up, you can compare campaigns on revenue against spend instead of on leads alone.
Expect Meta's numbers to stay lower than your CRM's. Some customers will not match to a Meta account, some will fall outside your attribution setting, and some leads came from other channels entirely. The point is not a perfect match but a consistent signal you can compare across campaigns.
A worked example, end to end
Example: a Jaipur coaching centre runs two Meta campaigns for a ₹38,000 foundation course, one for Class 10 students and one for droppers. In a month, the first campaign produces 300 leads at ₹120 each and the second 150 leads at ₹220 each. On cost per lead, the first campaign looks almost twice as good.
The centre's rule is simple: the counsellor marks a lead Converted only when the first fee instalment is paid, and enters the full course fee, excluding GST, as the deal value. Each time that happens, the CRM sends a Purchase event with value 38000, currency INR, the Meta lead ID and the hashed phone and email.
By the end of the month, the first campaign has 6 admissions and the second has 9. Spend was ₹36,000 and ₹33,000. Revenue recorded was ₹2,28,000 and ₹3,42,000. Per rupee of spend, the second campaign earned about ₹10.4 and the first about ₹6.3. These are illustrative figures, but the pattern is worth checking for in your own data: the campaign with the dearer leads can be the better business.
Without purchase value, Meta would have kept favouring the cheaper leads, because that was all it was told about. With value, both the centre and Meta can see which campaign produces fee-paying students.
Comparison tables
What to send as value, by business type (examples)
| Business (example) | Stage that triggers Purchase | Value to send | Why |
|---|---|---|---|
| Coaching centre, Jaipur | Fee paid | Course fee, e.g. 38000 | It is the revenue collected |
| Real estate broker, Pune | Deal registered | Brokerage, not property price | Brokerage is the broker's revenue |
| Developer selling direct | Booking amount paid | Booking amount | Collected at a known date |
| Visa consultancy | Service fee paid | Service fee | Government fees are pass-through |
| Travel agency | Advance paid | Package price or margin | Choose one and stay consistent |
Value and currency: right and wrong formats
| Field | Right | Wrong | Why it fails |
|---|---|---|---|
| value | 38000 | ₹38,000 | Not a number |
| value | 38000 | 0 | A sale worth nothing distorts value reports |
| currency | INR | Rs or ₹ | Must be a 3-letter ISO currency code |
| event_time | Time payment was recorded | Date the lead arrived | Back-dating breaks the 7-day window |
FAQ
How do I send offline sales value to Facebook ads?
Send a Purchase event from your CRM through Meta's Conversions API when the sale is recorded, with value as a plain number, currency as a three-letter code such as INR, action_source set to system_generated, and the Meta lead ID plus hashed email and phone so Meta can match it to the ad.
Is value required on the Meta Purchase event?
Yes. Meta's standard event reference lists value and currency as required parameters for Purchase. Without them, Ads Manager has no conversion value to show for that sale.
Should I include GST in the purchase value sent to Meta?
Either works, as long as you are consistent. Pick one rule, include GST or exclude it, and apply it to every deal, otherwise revenue comparisons between campaigns are off by the GST rate, 18% on most services.
Can I send a Purchase event for a deal that closed months after the lead?
Yes. Meta's 7-day limit applies to the gap between event_time and when you send the event, not between the lead and the sale. Send Purchase promptly when the payment is recorded, with event_time set to that moment.
What value should a real estate broker send to Meta?
Usually the brokerage earned, not the property price, because brokerage is the broker's revenue. A developer selling directly might send the booking amount at the booking stage. The key is one consistent rule.
Where does Qualimize fit?
In Qualimize, the status your workspace attaches to the Converted tier sends a Purchase event when a rep moves a lead into it. It carries the deal value and currency when the rep has entered the deal value on the lead (entered by hand), and a nominal value of 1 otherwise, never 0. Qualimize does not pull payment amounts from billing or accounting tools, so the value is only as good as what your team records.
Key takeaways
- Send Purchase with value as a plain number and currency as INR; Meta requires both.
- Decide what value means for your business (fee, brokerage, booking amount) and apply it to every deal.
- Pick one GST rule and keep it.
- The 7-day limit is between recording the payment and sending the event, not between lead and sale.
- Make entering the deal amount part of marking a lead won, or your revenue data will be placeholders.