Stripe checkout to Google Ads conversion tracking

Send Stripe checkout conversions to Google Ads

When a customer completes a Stripe checkout, this workflow looks up their Google Click ID and uploads the conversion to Google Ads. The result is accurate server-side attribution that connects ad clicks to actual purchases, without relying on browser-side tracking that gets blocked by ad blockers and cookie restrictions.

It works by matching the customer's email in PostHog to the GCLID captured when they first clicked your ad. The conversion value, currency, and timestamp are extracted from the Stripe event and sent to Google Ads in real time.

Enhanced conversions included for better match rates

The workflow includes a SHA256-hashed version of the customer's email alongside the GCLID. This is Google's Enhanced Conversions feature, which improves match rates when the click ID alone isn't enough to connect the dots between a click and a purchase.

Both the GCLID lookup and the hashed email happen in the background. Your team doesn't need to touch anything once the webhook is connected.

How the pipeline works step by step

Stripe fires a checkout.session.completed webhook. The workflow extracts the customer email, payment amount, and currency. It then searches PostHog for that email and pulls the associated GCLID (trying last-touch first, then initial click). If a GCLID is found, it uploads the conversion to the Google Ads REST API using your configured conversion action. If no GCLID exists for that customer, the conversion is skipped.

What you need to connect

You'll need your Stripe webhook pointing to this workflow's /webhook endpoint, your PostHog project credentials, and your Google Ads API credentials (client ID, client secret, refresh token, developer token, customer ID, manager account ID, and conversion action ID). There's also a manual endpoint for testing individual conversions with a known GCLID.