Meta Conversions API setup for Lemon Squeezy
Meta on Lemon Squeezy is worth doing when your spend justifies it and not before. The mechanics are simple — a shared event ID from the order ID, currency sent per event because digital products sell everywhere, and refunds reversed. The judgement call is whether the Conversions API earns its setup cost at your volume.
Free30 minutesNo obligation
Lemon Squeezy + Meta CAPI · what breaks
What goes wrong on Lemon Squeezy
- 01
Hosted checkout on another domain
Your first-party cookies do not travel there, so the identifier has to be passed deliberately.
- 02
The order record living outside your database
Lemon Squeezy is the merchant, so it holds the authoritative record.
- 03
License and subscription renewals with no browser
Digital products renew on a schedule like any subscription.
- 04
Tax-inclusive pricing
What the customer paid and what you receive differ, and comparing them produces a gap that looks like a bug.
Lemon Squeezy + Meta CAPI · the fix
What changes — Lemon Squeezy + Meta CAPI
Orders sent from webhooks
Server-side, so a closed tab stops costing you a conversion.
The identifier carried through checkout
Via custom data, verified on a real order.
An honest answer about whether to build this
For a store at low volume, the native reporting may be enough and we will say so.
Lemon Squeezy + Meta CAPI · architecture
How Meta tracking behaves on Lemon Squeezy
The Meta destination on Lemon Squeezy.
- 1
Purchase from the webhook with a shared event_id
So the overlay pixel and the server event count once.
- 2
Customer data hashed and normalized
Lemon Squeezy holds a confirmed email.
- 3
Currency per event
Global sales make the account default wrong constantly.
- 4
Renewals as a custom event or not at all
Never as Purchase.
- 5
Refunds reversed
Available and rarely wired.
Lemon Squeezy + Meta CAPI · diagnose
Where Lemon Squeezy 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
Open a real order and check its custom data
If the identifier is absent, nothing downstream can attribute it.
- 02
Compare Lemon Squeezy orders against reported conversions
Per order, for a closed window.
- 03
Check whether the overlay callback is the only trigger
If so, closed tabs are costing you conversions.
- 04
Confirm currency is sent per order
Digital goods sell everywhere.
- 05
Check whether refunds reverse
Usually not.
Lemon Squeezy + Meta CAPI · prove
The QA evidence — Lemon Squeezy + Meta CAPI
Run on Lemon Squeezy specifically, on a live conversion rather than in preview mode.
Source of truth
Lemon Squeezy's order records — completed orders by date, net of refunds
- A test order completed with the identifier confirmed in its custom data.
- An order where the overlay was closed immediately, confirmed to still report.
- A refund confirmed to reverse.
- Orders reconciled per order against each platform for a closed window.
- Currency confirmed correct on a non-default-currency order.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
Lemon Squeezy + Meta CAPI · free audit
What we check in the free audit
- Open a real order and check its custom data
- Compare Lemon Squeezy orders against reported conversions
- Check whether the overlay callback is the only trigger
- Confirm currency is sent per order
- Check whether refunds reverse
Checked against
Lemon Squeezy's order records — completed orders by date, net of refunds
Free30 minutesNo obligation
Lemon Squeezy + Meta CAPI · when not to buy
When you don't need this on Lemon Squeezy
Worth reading before you buy anything, from us or anyone.
- If you are selling a small volume of digital products, the native reporting is genuinely adequate and this work will not pay for itself. That is the honest answer for a real share of Lemon Squeezy stores.
- If your orders and platform conversions already reconcile within a few percent, nothing here needs doing.
- If you are not running paid media, skip the ad-platform half entirely.
- Decide gross versus net yourself first — it resolves a good number of these questions with no build at all.
Lemon Squeezy + Meta CAPI · what we deliver
What gets built for Meta on Lemon Squeezy
A shared event ID on both paths
the Lemon Squeezy order ID
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 Lemon Squeezy's order records — completed orders by date, net of refunds. 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
Lemon Squeezy + Meta CAPI questions, answered
A shared event_id derived from the order ID on both the pixel and the Conversions API event, then verified in Events Manager on a real purchase.
If you are not spending meaningfully on Meta, no. It is real work and it earns its cost when the optimization signal is worth improving. We would rather tell you that than build it.
The confirmed email and country from the order, normalized before hashing. That is most of what Lemon Squeezy has, and it is enough for a decent score.
As a custom event at most. Never as Purchase, or your reported ROAS grows every month regardless of what your campaigns do.
Free · 30 min
Get Pixel and CAPI counting once on Lemon Squeezy
WhatsAppFree30 minutesNo obligation
