Google Ads and GA4 tracking for Klarna
Google Ads on Klarna orders is mostly about where the conversion fires. Sourced from the order record it works normally; sourced from the confirmation page it silently misses the buyers who never returned. Watch for a legacy page tag still firing alongside the server event, or the customers who did return will count twice.
Free30 minutesNo obligation
Klarna + Google · 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 + Google · the fix
What changes — Klarna + Google
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 + Google · architecture
How the Google destinations behave on Klarna
Google Ads and GA4 on Klarna orders.
- 1
Send from the order record
Which exists whether or not the browser came back.
- 2
Use the store order ID for deduplication
Stable and already unique.
- 3
Value at the order total, consistently
Klarna's fee is a cost of sale, not a reduction in the conversion value — unless you decide otherwise and say so.
- 4
Watch for the confirmation-page tag firing too
If it still exists, it will double-count the orders where the customer did return.
- 5
Report BNPL as a segment
So its return rate is visible.
Klarna + Google · 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 + Google · prove
The QA evidence — Klarna + Google
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 + Google · 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 + Google · 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 + Google · what we deliver
What gets built for Google on Klarna
GA4 ecommerce events in the recommended shape
Correct names, transaction_id present, currency per order, an items array that agrees with the value.
Click identifiers captured and persisted
gclid, gbraid and wbraid — not just the first, because iOS traffic arrives with the others.
Enhanced Conversions from the data layer
Not from CSS selectors, which break on every redesign silently.
Conversion action settings reviewed
Counting, primary status and attribution window — free to change and more consequential than most tag work.
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 + Google questions, answered
Generally no — the fee is a cost of sale, and every other order's conversion value is gross too. Whichever you choose, apply it consistently, because a per-payment-method value definition is how reconciliation becomes impossible.
No. Orders whose conversions never fired cannot be recreated after the fact beyond the import window, and even inside it only if you have the click identifier on the order. This starts working forward, which is a reason to do it sooner.
It is a strong candidate, especially if BNPL is a meaningful share of orders. Segment your store's orders by payment method and compare each against what Google reports — if the BNPL segment is the one with the gap, you have your answer.
The order record holds the customer email, which makes it usable — hashed before it leaves your systems, and only where consent allows.
Free · 30 min
Get Google Ads and GA4 right on Klarna
WhatsAppFree30 minutesNo obligation
