Meta Conversions API setup for Stripe
Meta on Stripe needs the charge ID as the shared event ID and the click ID in Stripe metadata. Subscription businesses get the additional benefit that renewals become real events rather than a lifetime value guess made at signup.
Free30 minutesNo obligation
Stripe + Meta CAPI · what breaks
What goes wrong on Stripe
- 01
Stripe Checkout is a different domain
The session splits where the money moves, so browser attribution is at its weakest exactly when it matters.
- 02
Renewals have no browser at all
A card charged on month four fires nothing anywhere.
- 03
Refunds and failed payments ignored
Both are webhook events and both are routinely unwired.
- 04
Lifetime value guessed at signup
Rather than accumulated as payments clear.
Stripe + Meta CAPI · the fix
What changes — Stripe + Meta CAPI
Every charge counted as it clears
First payment, renewal, upgrade.
Click ID in Stripe metadata
So renewals stay attributable indefinitely.
Refunds and failures reversed
So reported revenue tracks collected revenue.
Stripe + Meta CAPI · architecture
How Meta tracking behaves on Stripe
The charge ID does all the work.
- 1
Charge ID as event_id
Unique per payment, available to the webhook.
- 2
Purchase per charge
First payment and renewals as distinct events.
- 3
Click ID from metadata
Written at signup, read at every later charge.
- 4
Customer data from the Stripe customer
Normalized before hashing.
- 5
Refunds reversed
Available as a webhook and rarely wired.
Stripe + Meta CAPI · diagnose
Where Stripe 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 Stripe collected revenue to platform revenue
For a closed month.
- 02
List subscribed webhooks
Usually none, or only the checkout one.
- 03
Check whether click IDs reach Stripe metadata
Determines renewal attribution entirely.
- 04
Check whether refunds do anything
Usually not.
- 05
Establish whether checkout is hosted or embedded
It decides how much the browser can see.
Stripe + Meta CAPI · prove
The QA evidence — Stripe + Meta CAPI
Run on Stripe specifically, on a live conversion rather than in preview mode.
Source of truth
your Stripe charge and invoice records
- Each payment type confirmed arriving as its own event.
- Click ID present in Stripe metadata on a live customer.
- Charge ID confirmed as the deduplication key at every destination.
- Collected revenue reconciled against Stripe for a closed month.
- A real refund tested and confirmed reversing.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
Stripe + Meta CAPI · free audit
What we check in the free audit
- Compare Stripe collected revenue to platform revenue
- List subscribed webhooks
- Check whether click IDs reach Stripe metadata
- Check whether refunds do anything
- Establish whether checkout is hosted or embedded
Checked against
your Stripe charge and invoice records
Free30 minutesNo obligation
Stripe + Meta CAPI · when not to buy
When you don't need this on Stripe
Worth reading before you buy anything, from us or anyone.
- If you sell one-time products through embedded Elements on your own domain and your numbers reconcile, the browser event may genuinely be sufficient.
- If you have no subscriptions and no refunds, most of the recurring complexity here doesn't apply to you.
- The webhook work is well-documented and any backend developer can do it. Hand them this page.
- Check which webhooks you already subscribe to first. Some stacks have more wired than the team realises.
Stripe + Meta CAPI · what we deliver
What gets built for Meta on Stripe
A shared event ID on both paths
The Stripe charge ID, unique per payment and present on the webhook.
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 your Stripe charge and invoice records. 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
Stripe + Meta CAPI questions, answered
The Stripe charge ID, one per payment.
The invoice webhook, referencing the click ID stored in Stripe metadata at signup.
It splits the session, because it's a different domain. The webhook makes that irrelevant for the money event.
Yes, and it's a webhook away. Without it reported revenue only ever climbs.
Free · 30 min
Get Pixel and CAPI counting once on Stripe
WhatsAppFree30 minutesNo obligation
