Meta Conversions API setup for Klarna
Meta on Klarna is the textbook case for deduplication doing real work: the pixel fires for buyers who returned and not for those who did not, while the server event fires for all of them. A shared event ID from your store order ID lets Meta pair the two, so every order counts exactly once regardless of which path the customer took.
Free30 minutesNo obligation
Klarna + Meta CAPI · what breaks
What goes wrong on Klarna
- 01
The customer redirects away and does not return
Klarna approves, the order is placed, and the confirmation page never loads. The sale is real and the conversion does not exist.
- 02
Authorization and capture are separate moments
Counting at authorization risks orders that never capture; counting at capture delays the signal.
- 03
Klarna orders under-reported and blamed on the campaign
The channels that skew toward BNPL users look worse than they are.
- 04
Returns higher on BNPL
Pay-later carts return at a higher rate in many stores, and unreversed returns overstate revenue.
Klarna + Meta CAPI · the fix
What changes — Klarna + Meta CAPI
Orders sent from the store's own record
Server-side, so the redirect stops mattering.
A deliberate decision on authorization versus capture
Written down, so the number means one thing.
Returns reversed
Which matters more here than on card orders.
Klarna + Meta CAPI · architecture
How Meta tracking behaves on Klarna
The Meta destination on Klarna orders.
- 1
Purchase from the server with a shared event_id
Because the pixel may or may not have fired depending on whether the customer returned.
- 2
Customer data from the order record
Normalized before hashing.
- 3
Returns reversed
BNPL return rates make this material.
- 4
Currency explicit
Klarna operates across many markets.
- 5
Payment method as a custom parameter
Useful for understanding which audiences skew BNPL.
Klarna + Meta CAPI · diagnose
Where Klarna 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
Count Klarna checkouts started against confirmation pages loaded
The gap is the share of BNPL orders your browser-side setup cannot see.
- 02
Check whether the conversion fires from the order or the page
If it is the page, you have found the cause.
- 03
Compare store orders paid with Klarna against reported conversions
Per order, for a closed window.
- 04
Check whether the return rate on BNPL differs
In most stores it does, and unreversed returns then overstate BNPL revenue specifically.
- 05
Confirm no double counting for customers who did return
Both the page tag and the server event may fire.
Klarna + Meta CAPI · prove
The QA evidence — Klarna + Meta CAPI
Run on Klarna specifically, on a live conversion rather than in preview mode.
Source of truth
Your store's order records for orders paid with Klarna, cross-checked against Klarna's own settlement reports
- A Klarna order completed with the browser closed at the redirect, confirmed to still report.
- A Klarna order where the customer did return, confirmed to report exactly once.
- A return confirmed to reverse at each destination.
- Store orders paid with Klarna reconciled per order against each platform for a closed window.
- The authorization-versus-capture decision documented before anything was sent.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
Klarna + Meta CAPI · free audit
What we check in the free audit
- Count Klarna checkouts started against confirmation pages loaded
- Check whether the conversion fires from the order or the page
- Compare store orders paid with Klarna against reported conversions
- Check whether the return rate on BNPL differs
- Confirm no double counting for customers who did return
Checked against
Your store's order records for orders paid with Klarna, cross-checked against Klarna's own settlement reports
Free30 minutesNo obligation
Klarna + Meta CAPI · when not to buy
When you don't need this on Klarna
Worth reading before you buy anything, from us or anyone.
- If Klarna is a very small share of your orders, measure the share before commissioning anything — it may not move a decision.
- If your conversions already fire from the order record rather than the confirmation page, this is largely working.
- The checkouts-started against confirmations-loaded count is free and takes ten minutes. Do it first.
- If your BNPL provider is different, the same shape applies — the redirect is the problem, not the brand.
Klarna + Meta CAPI · what we deliver
What gets built for Meta on Klarna
A shared event ID on both paths
your store's 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 Your store's order records for orders paid with Klarna, cross-checked against Klarna's own settlement reports. 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
Klarna + Meta CAPI questions, answered
A shared event_id derived from the store order ID, on both the pixel event and the server event. When the customer returns, Meta pairs them; when they do not, only the server event exists and it still counts once. That is exactly the case deduplication is designed for.
In most stores they buy higher-value carts and return more often. Both are worth knowing before anyone judges a campaign that skews toward them, and both are only visible if the payment method is on the conversion.
Yes, and it matters more here than on card orders because the return rate is higher. Without it, reported ROAS on BNPL-heavy campaigns drifts upward permanently.
Not inherently — you are sending the same order data. What differs is whether the event fires at all, which is the whole point of moving it server-side.
Free · 30 min
Get Pixel and CAPI counting once on Klarna
WhatsAppFree30 minutesNo obligation
