Meta Conversions API setup for Chargebee
Meta on Chargebee means sending the first payment as a Purchase with a stable event ID, keeping trial signups as a separate custom event for optimization volume, and never sending renewals as Purchase. Chargebee's dunning behaviour matters here too: four retries for one billing period must produce one conversion, not four.
Free30 minutesNo obligation
Chargebee + Meta CAPI · what breaks
What goes wrong on Chargebee
- 01
Trial-to-paid conversions happening with no browser present
The moment a business actually starts earning is invisible to anything that fires from a page.
- 02
Dunning retries counted as revenue
A failed payment retried four times can produce four invoice events for one billing period.
- 03
Signups optimized instead of paid conversions
Free-trial signups attract people who like free trials, and no budget fixes that.
- 04
Upgrades and downgrades never reflected
The recurring amount changes and reported value does not.
Chargebee + Meta CAPI · the fix
What changes — Chargebee + Meta CAPI
Trial-to-paid as the acquisition conversion
Sent from the first successful payment, not from the signup.
Value based on expected lifetime
Monthly recurring revenue times your own average tenure, documented.
Failed payments and dunning excluded
An invoice created is not an invoice paid.
Chargebee + Meta CAPI · architecture
How Meta tracking behaves on Chargebee
The Meta destination on Chargebee.
- 1
Send the first payment as Purchase
Once, with lifetime value, from the payment webhook.
- 2
Trial signup as a separate custom event
Useful for optimization volume, never as Purchase.
- 3
Customer data hashed from the Chargebee record
Normalized first, which is where match quality is usually lost.
- 4
Renewals as a custom event or not at all
Sending them as Purchase inflates ROAS by your whole subscriber base.
- 5
Cancellations reversed
Because the lifetime value you sent has now proven wrong.
Chargebee + Meta CAPI · diagnose
Where Chargebee tracking breaks, in diagnostic order
Each check rules out a class of cause, so by the last one there is usually a single explanation standing.
- 01
Compare Chargebee revenue to reported revenue for a closed month
The gap is the renewal and trial blind spot.
- 02
Check whether the identifier is on the customer or only on the signup
If it did not survive the trial, trial-to-paid cannot be attributed.
- 03
Check whether the event fires on invoice or on payment
Invoice-based firing counts money you have not received.
- 04
Look for dunning retries counted more than once
Four attempts for one period is common and it inflates everything downstream.
- 05
Measure trial length against every import window
Before assuming an offline upload is even possible.
Chargebee + Meta CAPI · prove
The QA evidence — Chargebee + Meta CAPI
Run on Chargebee specifically, on a live conversion rather than in preview mode.
Source of truth
Chargebee's subscription and invoice records — paid invoices by payment date, net of refunds and failed payments
- A test subscription taken through trial to first payment, with exactly one conversion firing at the payment.
- A dunning sequence confirmed to produce one conversion, not one per retry.
- A cancellation confirmed to reverse at each destination that accepts one.
- Chargebee paid invoices reconciled against reported revenue for a fully closed month.
- The lifetime value model shown as a calculation from your own churn data.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
Chargebee + Meta CAPI · free audit
What we check in the free audit
- Compare Chargebee revenue to reported revenue for a closed month
- Check whether the identifier is on the customer or only on the signup
- Check whether the event fires on invoice or on payment
- Look for dunning retries counted more than once
- Measure trial length against every import window
Checked against
Chargebee's subscription and invoice records — paid invoices by payment date, net of refunds and failed payments
Free30 minutesNo obligation
Chargebee + Meta CAPI · when not to buy
When you don't need this on Chargebee
Worth reading before you buy anything, from us or anyone.
- If your trial is longer than 90 days, offline upload of the first payment cannot work against the original click. We will tell you that before quoting.
- If Chargebee revenue and reported revenue already agree within a few percent, this is working.
- If you have no paid acquisition, the reporting fix matters and the ad-platform work does not.
- If your churn history is too short to model lifetime value, use a conservative figure and say it is conservative.
Chargebee + Meta CAPI · what we deliver
What gets built for Meta on Chargebee
A shared event ID on both paths
the Chargebee invoice ID for the first payment
Standard event names, exactly cased
Meta matches on name and ID together, so a case difference alone produces two events.
Customer data normalized then hashed
Lowercase and trimmed email, phone in E.164. This is where nearly every low match quality score comes from.
fbc and fbp forwarded from the browser
fbc only exists if fbclid was captured on landing — a very common gap.
Written guarantee
95%+ tracking accuracy
Measured against Chargebee's subscription and invoice records — paid invoices by payment date, net of refunds and failed payments. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
Chargebee + Meta CAPI questions, answered
Because Meta counts them all and your reported ROAS then includes revenue from customers acquired long before the campaign ran. On a business with good retention this compounds monthly until the reported figure is several times the truth.
Chargebee holds a confirmed billing email and usually a full billing address, which is better data than most signup forms produce. The gains come from normalizing before hashing, which is easy to get wrong and invisible unless you check the resulting score.
As a custom event, yes — they give the algorithm volume to learn from when paid conversions are sparse. Just never as Purchase, and never as the optimization target once paid volume supports it.
If you sent lifetime value at acquisition, yes. You told Meta a customer was worth three years; when they cancel in month two that claim is wrong, and leaving it uncorrected means every subsequent optimization decision inherits the error.
Free · 30 min
Get Pixel and CAPI counting once on Chargebee
WhatsAppFree30 minutesNo obligation
