Conversion tracking for Chargebee
Chargebee is a billing system, which means it holds the only complete record of what a subscription business actually earned — and it sits entirely outside the browser. Trials convert on a schedule, renewals bill on a cron, dunning retries create several invoice events for one billing period, and upgrades change the recurring amount without any page load. Almost every Chargebee-backed business reports its signups accurately and its revenue not at all.
Free30 minutesNo obligation
Chargebee tracking · 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 tracking · the fix
What changes — Chargebee tracking
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 tracking · architecture
What Chargebee actually lets you do
What Chargebee gives you, and where the gaps are.
- 1
Comprehensive webhooks
Subscription, invoice, payment and dunning events, all server-side and all reliable.
- 2
Custom fields on customer and subscription
Where the click identifier lives so it survives past the trial.
- 3
A clear paid-versus-failed distinction
Which most billing integrations ignore and which materially changes the numbers.
- 4
Hosted checkout pages
On a Chargebee domain, so the identifier must be passed deliberately rather than carried by a cookie.
- 5
No native ad-platform conversion sending
Chargebee reports revenue well and sends conversions nowhere. That gap is the work.
Chargebee tracking · 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 tracking · prove
The QA evidence — Chargebee tracking
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 tracking · 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 tracking · 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 tracking · what we deliver
The event map on Chargebee
Subscription created (trial)
A leading indicator. Report it; do not bid on it unless volume forces you to.
First payment succeeded
The acquisition event. Sent once, at expected lifetime value.
Recurring payment succeeded
Renewal revenue. Report it; think before sending it anywhere.
Payment failed / dunning
Not revenue. Explicitly excluded, or you will count one period several times.
Subscription cancelled
Reverse the lifetime value where the destination accepts it.
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 tracking questions, answered
Payment succeeded, always. An invoice generated is a bill you have sent, not money you have received, and in a business with any dunning at all the difference is large. This single distinction resolves most Chargebee revenue discrepancies we are asked to look at.
Key the conversion on the billing period rather than on the payment attempt. A period that eventually succeeds after four retries is one payment, and every destination needs to see it as one.
Yes — 30 days sits comfortably inside the 90-day import window, provided the click identifier survived the trial. That persistence is the part that needs building, because no browser cookie you can rely on lasts that long.
Monthly recurring revenue times your average customer tenure, from your own Chargebee data. Sending the first month's payment makes a customer who will stay three years look like a small transaction, and bidding will treat them as one.
Free · 30 min
Get Chargebee tracking done properly
WhatsAppFree30 minutesNo obligation
