Stripe + Google Ads: bid on confirmed revenue, not checkout events
Stripe knows what money actually cleared, including refunds, failed payments, and subscription renewals that a front-end pixel never sees. Feeding Stripe data into Google Ads lets bidding optimize to confirmed revenue rather than optimistic checkout events. This guide covers the setup iClick uses for subscription and high-refund businesses.
A 47-point written audit of your Google, Meta or Shopping account, back in five business days.
Get your auditBook a callWhat this integration unlocks
- Conversions based on confirmed, cleared payments rather than checkout events
- Refund and chargeback adjustments so bidding sees net revenue
- Subscription renewal value fed back to Google Ads
- Accurate value signals for value-based bidding
- A revenue truth layer between the front end and the ad platform
Setup steps
- 1
Capture the click identifier at checkout
For Stripe data to reach Google Ads, the GCLID must be captured at the point of purchase and stored against the Stripe customer or payment, usually in metadata. Without it, there is nothing to match a later confirmed payment back to.
Store the GCLID in Stripe metadata at checkout so every downstream payment event can be attributed.
- 2
Listen to Stripe payment events
Use Stripe webhooks to listen for the events that represent real revenue: payment succeeded, invoice paid for subscriptions, and refund or dispute events. These are the truth about what money cleared, as opposed to a front-end thank-you page that fires regardless.
Build a small service or use a connector to process these webhooks reliably.
- 3
Send confirmed conversions to Google Ads
When a payment clears, send an offline conversion import to Google Ads using the stored GCLID, the confirmed value, and the timestamp. For subscriptions, decide whether to send first-payment value, expected value, or renewal events, based on how you want bidding to weigh recurring revenue.
This replaces the optimistic checkout conversion with one grounded in cleared money.
- 4
Handle refunds and failed payments
When a refund, chargeback, or failed payment occurs, send a conversion adjustment to Google Ads to retract or reduce the value. Businesses with meaningful refund rates that skip this step teach bidding to chase revenue that later disappears.
Common issues
Fix. The identifier was not captured at checkout. Store the GCLID in Stripe metadata at the point of purchase so later payment events can be attributed to the original click.
Fix. Refunds are not being fed back. Send conversion adjustments on refund and chargeback events so bidding optimizes to net, not gross, revenue.
Fix. Only first payment is being sent. Decide on a subscription value approach, expected lifetime value or renewal events, so recurring revenue is properly represented.
Fix. Use one source of truth for the purchase conversion. If Stripe sends the confirmed conversion, ensure the front-end pixel is not also counting the same order.
Common questions
Want this checked on your own account?
A 47-point written audit of your Google, Meta, or Shopping account. Five business days, no sales call.
