Google Ads and GA4 tracking for Stripe
The Google side on Stripe is about which moment counts. Checkout completion is a page a customer may never see; the charge succeeding is a fact. Source from the charge, use the charge ID as transaction_id, and the refresh and abandonment problems disappear.
Free30 minutesNo obligation
Stripe + Google · 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 + Google · the fix
What changes — Stripe + Google
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 + Google · architecture
How the Google destinations behave on Stripe
Count charges, not checkout page views.
- 1
transaction_id as the Stripe charge ID
Unique per payment, and immune to page refreshes.
- 2
Counting set to every
Several payments from one customer are several conversions.
- 3
Renewals as their own conversion action
So new business and retention are separable.
- 4
Click ID in metadata at signup
The only storage that survives to renewal four.
- 5
Currency per charge
Stripe records it precisely; pass it on.
Stripe + Google · 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 + Google · prove
The QA evidence — Stripe + Google
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 + Google · 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 + Google · 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 + Google · what we deliver
What gets built for Google on Stripe
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 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 + Google questions, answered
The Stripe charge ID — unique per payment and immune to page refreshes.
Every. Multiple payments from one customer are multiple conversions.
Yes. It's the only way to see new business and retention separately in the platform.
No. Send each payment as it clears. Projections report revenue you haven't earned.
Free · 30 min
Get Google Ads and GA4 right on Stripe
Free30 minutesNo obligation
