Paddle → GA4 · Conversion tracking
Connecting Paddle to GA4
Paddle is the merchant of record, so it holds the transaction and your own database may have no record of the money at all. GA4 is where the business goes to understand what happened, which makes an unattributed conversion there expensive in decisions rather than in ad spend. The join between them succeeds or fails on one thing: whether the GA4 client_id reaches the Paddle transaction before the conversion happens, because GA4 can only match a conversion it can tie back to a click it recognizes.
✓ 30-minute call · No commitment · You leave with a written remediation plan even if we’re not the right fit.
Written guarantee
95%+ conversion accuracy on Paddle → GA4
Measured against your own order records at handover. Miss it and we keep working at no cost until it’s met.
Built on — and certified for — the platforms that matter
Stape
Pro Partner
Meta
Tech Provider
Tag Manager
TikTok
Events API
Microsoft
UET Partner
CAPI Partner
CAPI Partner
Built on the same partner stack used by enterprise DTC brands.
By the numbers
No fake testimonials.Just the math.
70+
Platforms supported
Shopify · Woo · Magento · BigCommerce · 65 more
8+ / 10
Meta EMQ guaranteed
in writing — keep working free until hit
2–4d
Build to live
accurate data flowing within 7 days
$0
Monthly fees, ever
one-time fixed price · you own the stack
400d
Cookie lifetime
max RFC 6265bis allows · 57× Safari ITP
9
Ad channels covered
Meta · Google · TikTok · MS · LI · Pin · Snap · Reddit · X
95%+
Tracking accuracy
verified vs Stripe · GA4 · ad-platform reports
30 min
Free founder call
no SDR · no pitch deck · written remediation plan
Every figure above is either a commitment we put in writing or a countable fact. What your own setup is losing is not on this list, because we haven’t measured it yet — that happens on the call, against your own order records.
Real clients · real videos · real outcomes
Don’t take our word for it. Watch the receipts.
Founders, marketers, and agency owners describing the before-and-after of their Paddle → GA4 tracking rebuild — in their own words, on camera.
Why this join usually fails
The GA4 client_id never reaches Paddle
The single most common cause. Paddle's checkout is an overlay or a hosted page that never navigates, so nothing you set in a cookie follows the customer and no page-load trigger fires. The identifier must be passed in as custom data when the checkout is opened.
An overlay checkout that never navigates
Nothing loads a page, so anything expecting a thank-you page simply never fires — and the customer who closes the overlay on success is invisible.
Everything lands under (direct)/(none)
The classic Measurement Protocol symptom, and it always means the same thing: the client_id was missing or wrong, so GA4 had no session to attach the event to and invented a new user.
Nothing reconciles afterwards
An upload that succeeds is not an upload that matched. GA4 DebugView shows events arriving with their parameters, and Realtime confirms the user and session they attached to. Neither tells you whether you are double-counting — for that, compare GA4's conversion count against the source system's record for the same window.
Architecture
How Paddle and GA4 actually connect
Two systems that know nothing about each other. Everything below exists to give them one shared reference.
Step 1
Paddle holds the truth
Under a merchant-of-record model those three figures genuinely differ, and most Paddle reconciliation arguments turn out to be two people comparing two of them.
Step 2
GA4 needs a click to match
GA4 needs the client_id to attach a server event to the user and session that produced the click. Without it there is no attribution to inherit and the event is orphaned.
Step 3
The identifier is the bridge
The GA4 client_id, captured at the visit and carried into the Paddle transaction. Without it there is nothing to join on and no tool fixes that.
Step 4
The event source decides reliability
Send from the webhook, not the overlay's JavaScript callback — the customer can close the overlay the instant payment succeeds and the callback never runs even though the money moved.
Step 5
Deduplication at the destination
GA4 has no built-in deduplication for Measurement Protocol. If the browser also sends the event, it counts twice. The only reliable approach is to decide per event which side sends it, and enforce that decision — GA4 will not protect you from your own duplicates.
Diagnose it honestly
Working vs. broken, side by side
Both states look identical from the GA4 dashboard, which is why this runs for months before anyone notices.
Normal — not a fault
The GA4 client_id present on the transaction
Visible on the record itself in Paddle, not merely captured somewhere on the site.
Sent from the transaction.completed webhook
Server-side, so it does not depend on the customer's browser still being there.
Deduplicated correctly
GA4 has no built-in deduplication for Measurement Protocol. If the browser also sends the event, it counts twice. The only reliable approach is to decide per event which side sends it, and enforce that decision — GA4 will not protect you from your own duplicates.
Reconciles with the source
GA4's count and Paddle's records agree within a few percent over a closed window.
Actually broken
The GA4 client_id missing on most records
Paddle's checkout is an overlay or a hosted page that never navigates, so nothing you set in a cookie follows the customer and no page-load trigger fires. The identifier must be passed in as custom data when the checkout is opened.
Sent from the browser
Anyone who closes the tab, blocks the script or converts without a page load is invisible. Nothing loads a page, so anything expecting a thank-you page simply never fires — and the customer who closes the overlay on success is invisible.
Counted twice, or not at all
The classic Measurement Protocol symptom, and it always means the same thing: the client_id was missing or wrong, so GA4 had no session to attach the event to and invented a new user.
Nobody has reconciled it
The dashboard shows a number and no one has compared it to Paddle. A wrong number that nobody checks is indistinguishable from a right one.
Diagnostic sequence
Diagnostic order
Each step rules out a class of cause. Run them in order and the last one usually has a single explanation standing.
- 1
Count transactions carrying the GA4 client_id
The ceiling on everything else. Do this before debugging anything downstream.
- 2
Follow one real conversion end to end
From the ad click through Paddle and into GA4.
- 3
Open a Paddle transaction and read its custom data
If the identifier is not there, the join is broken at the source and every other check is wasted effort.
- 4
Check whether server events carry a session and a source
In GA4 Realtime or DebugView, find the event and look at its session and traffic source. A brand-new user with no source on every server event is the missing-client_id signature.
- 5
Read the match rate, not the success message
GA4 DebugView shows events arriving with their parameters, and Realtime confirms the user and session they attached to. Neither tells you whether you are double-counting — for that, compare GA4's conversion count against the source system's record for the same window.
Source-of-truth validation
How it gets proven
Against Paddle's own records, not against either platform's dashboard.
- The GA4 client_id confirmed present on a live transaction.
- A real conversion followed from click through Paddle to GA4.
- Server events confirmed in DebugView attaching to an existing session with the original traffic source intact.
- A purchase where the overlay was closed immediately, confirmed to still report.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later.
Straight talk
When you don't need this
Worth reading before paying anyone, including us.
- If GA4 already reports conversions that reconcile against Paddle's records within a few percent, this join is working and there is nothing to buy.
- Measure identifier coverage yourself first — pull your last hundred transactions and count how many carry the GA4 client_id. Ten minutes, free, and it tells you whether any of this is worth doing.
- If you sell a single one-off product in one currency with no subscriptions, Paddle's own reporting may be all you need.
- GA4 is reporting, not bidding. If your problem is ad platform optimization, fix the ad platform destination first — GA4 will not change what any campaign does.
Who this is for
Honest about who we’re a fit for.
We don’t take every project. Here’s how to tell if we’re right for you.
You’re a great fit if…
- You run Paddle → GA4 (or are migrating to it)
- You spend $5K+/month on paid ads (Meta, Google, TikTok, Microsoft, LinkedIn)
- Your reported ROAS doesn’t match what your bank account is saying
- You want to own your tracking stack — no monthly SaaS fees forever
- You have 2–4 days to do this once and never think about it again
Skip us if…
- You spend less than $500/month on paid ads (browser pixel is fine)
- You want a SaaS dashboard with monthly fees forever (Triple Whale, Hyros)
- You need attribution modeling — we fix the data foundation, not multi-touch reports
- You want a 6-month enterprise consulting engagement (we ship in 4 days)
- You expect us to manage your ad accounts (we don’t — that’s a different service)
If you’re still unsure,book the call anyway— we’ll tell you straight whether we can help.
What working looks like
The GA4 client_id on every transaction
Server-sideCaptured before the conversion and stored where it survives.
Conversions arriving in GA4
8+ EMQConversions appear in GA4 attributed to the original session's source and medium, so acquisition reporting reflects what actually drove revenue.
Reconciled against the source
DedupedPaddle's own records are the reference, not either dashboard.
What gets built
Identifier capture into Paddle
Pass the click identifier as custom data at checkout creation. It then appears on the transaction record and survives to the webhook.
Event source: the transaction.completed webhook
Send from the webhook, not the overlay's JavaScript callback — the customer can close the overlay the instant payment succeeds and the callback never runs even though the money moved.
Dispatch to GA4
Measurement Protocol events with the client_id, session_id and the correct measurement ID and API secret, sent server-side.
Reversals where they exist
Paddle exposes refunds and chargebacks and handles both, so reversals are straightforward and almost never wired.
Pick the package that fits your ad spend
Fixed-fee, no surprises. If your ad spend is meaningful,server-side tracking is what we recommend— it’s the only setup that survives iOS, Safari ITP and ad blockers.
Browser-side starter
Wires the join and verifies it on a live conversion. Honest about its ceiling where the source can only be read from the browser.
- The join built and tested end to end
- Verified on a real conversion
- Reconciled against the source's own records
- Written handover
1st-party server-side
Save $18K–$120K over 5 years vs Triple Whale / Hyros
The join built server-side from the source's own records, so it does not depend on a browser being present when the conversion happens.
- Events sourced from the system of record, not the browser
- Identifier captured and persisted end to end
- Deduplicated at the destination
- Reversals wired where the source supports them
- 95%+ accuracy guaranteed in writing
Full 1st-party stack
Every destination fed from one place, plus monitoring so a broken join surfaces in days rather than at quarter end.
- Everything in 1st-party server-side
- All paid destinations from one container
- CRM and offline loop
- Refunds and cancellations reversed everywhere
- Monitoring per destination
Not sure which tier fits?Book a 30-min scoping call— we’ll tell you straight, no upsell pressure.
How it works
Built in 2–4 days. Accurate data within 7.
We deliver the entire 1st-party server-side stack in 2–4 business days. You start collecting accurate, deduped conversion data the moment it goes live — and within 7 days every signal is flowing cleanly to Meta, Google, TikTok and the rest.
Kickoff + audit
30-min call. We map your current pixels, GTM, dataLayer, consent setup, and ad-platform integrations. You get a written report of every leak.
Build the stack
Server-side GTM container deployed on your subdomain. Meta CAPI · Google EC · TikTok Events API · Microsoft UET wired. Identity match + dedup configured.
QA + go-live
Live-fire test purchases across every funnel step. Meta EMQ verified at 8+. Tag Assistant + Pixel Helper passes. Side-by-side report delivered.
Verify accuracy
Your data flows clean. Within 7 days every signal — Meta, Google, TikTok, Microsoft — is fully accurate. Notion runbook + Loom walkthrough handoff.
Got questions?
The honestanswers.
No buzzwords, no upsell. If we don’t know, we say so.
01Why aren't my Paddle conversions showing in GA4?
Almost always because the GA4 client_id never reached the Paddle transaction. Paddle's checkout is an overlay or a hosted page that never navigates, so nothing you set in a cookie follows the customer and no page-load trigger fires. The identifier must be passed in as custom data when the checkout is opened. Measure coverage before debugging the dispatch.
02What identifier does GA4 need?
The client_id, from the _ga cookie. Measurement Protocol events without it are rejected or create a brand-new user with no session and no source, which is how server events end up filed under (direct)/(none) and make paid channels look worse than they are. Send session_id alongside it so the event joins the existing session, and include engagement_time_msec or the event may not appear as expected in reports.
03Where should the event come from?
The transaction.completed webhook. Send from the webhook, not the overlay's JavaScript callback — the customer can close the overlay the instant payment succeeds and the callback never runs even though the money moved.
04How do I know it worked?
GA4 DebugView shows events arriving with their parameters, and Realtime confirms the user and session they attached to. Neither tells you whether you are double-counting — for that, compare GA4's conversion count against the source system's record for the same window.
Still have questions?Book a 30-min call— bring them all.
The call
What happens on your free 30-min call
No pitch deck, no SDR, no upsell pressure. Founder-led. Bring your ad-platform screens and yourPaddle → GA4 setup — we’ll work through it together.
Min 1–5
We get the lay of your store
What you sell, what you spend on ads, who handles dev. Quick context-gathering — no questionnaire upfront.
Min 5–15
We audit your tracking live
Screen-share. We open your Meta Events Manager, GTM, and ad reports. You see exactly which conversions are leaking.
Min 15–25
We map a fix
What needs rebuilding, what stays. The exact Paddle → GA4 setup we'd ship and what it would recover for you.
Min 25–30
Decide. Or don’t.
If we're a fit, we send a 1-page proposal in writing. If not, you walk away with a free remediation plan you can hand to anyone.
Get Paddle and GA4 joined properly
Book a free 30-minute call. We measure your identifier coverage live on your own account, and you leave with a written plan — including the option that you don't need us.
Free · 30-min consultation · No commitment · Replies in under 2 hours · Available worldwide via WhatsApp
95% tracking accuracy guarantee
Free 30-min consultation · from $400 · 1st-party server-side
95% guarantee · from $400
