Stripe Google Ads Conversion Tracking with Google Tag Manager Including PayPal (2026)

Quick Answer

Stripe Google Ads conversion tracking works when the buyer comes back from Stripe or PayPal to a thank-you page on your own site with the order ID in the URL. In Stripe, set the Payment Link or Checkout redirect to ?session_id={CHECKOUT_SESSION_ID}. In PayPal, turn on Auto Return and Payment Data Transfer so PayPal adds tx. A Google Tag Manager (GTM) tag on that page reads the ID once, pushes a purchase event, and fires Google Ads, Google Analytics 4 (GA4) and Meta with the value and a transaction ID.

Key Takeaways

• The payment happens off your site: GTM can’t run on checkout.stripe.com or paypal.com, so the sale has to be caught when the buyer returns.
• Stripe gives you the ID: Stripe’s docs say you can put {CHECKOUT_SESSION_ID} in the redirect URL, and UTMs on a Payment Link are carried to that URL.
• PayPal needs two settings: Auto Return and Payment Data Transfer, which sends the transaction ID as tx to your Return URL.
• Use a transaction ID in Google Ads: Google counts a second conversion with the same ID as a duplicate. The ID can be up to 64 characters.
• Reloads must not count twice: the tracker in this guide remembers each order ID in the browser and skips repeats.
• Some buyers never return: closed tabs and delayed bank payments need a server-side backup through Stripe’s API or webhooks.

Introduction The Sale Happened, but Google Ads Shows Nothing

The message I get most often from clients who sell through Stripe goes like this: “Stripe shows sales every day, but Google Ads shows almost none, and GA4 says the revenue came from stripe.com.” The ads are usually fine. The tracking stops at the payment page.

This happens on almost every site that sells through Stripe Payment Links, Stripe Checkout or PayPal buttons. The buyer leaves your domain to pay. Your GTM container isn’t on the payment page, so nothing fires there. If the buyer comes back at all, it’s often to a generic page with no order details, or to Stripe’s own confirmation screen.

The fix isn’t complicated, but it has to be done in the right order: control where the buyer lands after paying, read the order ID there, count it once, and send it to every ad platform with the same ID. I already wrote a Stripe guide focused on GA4 and a general third-party checkout guide. This one is about getting Stripe and PayPal sales into Google Ads with real values, with tested code.

Where Each Checkout Sends the Buyer Back

Prerequisites & Setup Checklist

• Google Tag Manager on every page of your site, including the thank-you page.
• A thank-you page on your domain, for example /thank-you/, that isn’t linked from your menu.
• Access to the Stripe Dashboard (Payment Links) or the developer who set up Stripe Checkout.
• PayPal business account access, if you sell with PayPal buttons.
• A Google Ads purchase conversion action set up with “Use different values for each conversion”.
• A GA4 property and, if you run Meta ads, a Meta Pixel.
• Stripe test mode and a PayPal sandbox account for testing.

Not sure what’s already firing on your site? Run it through my free tracking audit tool before you start.

Video Tutorial Walkthrough

In the video I explain why Stripe, PayPal and other external gateways break purchase tracking, and how GTM, custom code, server-side tracking, Conversions APIs, CRM data, automation, Looker Studio and Consent Mode fit together around the checkout.

Step-by-Step Implementation Guide

Eight phases. Phases 1 to 6 get every returning buyer into Google Ads, GA4 and Meta. Phases 7 and 8 catch the buyers who don’t come back.

Phase 1: Send Buyers Back to a Thank-You Page You Control

1. Stripe Payment Link: open the link in the Stripe Dashboard, click After the payment, and choose to redirect customers to your website instead of showing Stripe’s confirmation page.
2. Use a redirect URL like https://yourdomain.com/thank-you/?session_id={CHECKOUT_SESSION_ID}&product=pro-plan&value=49&currency=USD. Stripe swaps {CHECKOUT_SESSION_ID} for the real session ID. The product, value and currency are fixed text you add per link.
3. Stripe Checkout through the API: ask your developer to put the same template in success_url, and to add the real amount as value if the price changes per order.
4. PayPal Payments Standard: in your PayPal account go to Website preferences, turn on Auto Return, set the Return URL to your thank-you page, and turn on Payment Data Transfer. PayPal then sends the transaction ID as tx.
5. PayPal JavaScript SDK buttons: in your onApprove code, after the capture succeeds, redirect to /thank-you/?paypal_order=ORDER_ID&value=AMOUNT&currency=USD.

Phase 2: Stop Stripe and PayPal from Taking the Credit in GA4

1. In GA4, go to Admin → Data streams → your web stream → Configure tag settings → List unwanted referrals.
2. Add checkout.stripe.com, stripe.com, paypal.com and any other payment domain your buyers pass through.
3. Check that the Conversion Linker tag fires on all pages in GTM, so the Google Ads click cookie is on your domain before the buyer leaves.

Google Ads matches the purchase with its own first-party cookie on your domain, so it doesn’t care about the referral. GA4 does. Without this step, GA4 reports your Google Ads revenue as “stripe.com / referral”.

Phase 3: Add the Purchase Tracker in GTM

1. In GTM, go to Tags → New → Custom HTML and paste the code below.
2. Change CURRENCY to your store currency, and fill PRICES only if some redirect URLs have a product name but no value.
3. Create a trigger: Page View, fires on Page Path contains /thank-you. Use it for this tag only.
4. Name the tag cHTML – Stripe PayPal Purchase and save.

<script>
// Stripe and PayPal purchase tracker for the thank-you page by MD Niamul (mdniamul.com)
// Reads the order ID that Stripe or PayPal adds to your return URL and pushes one
// GA4-style purchase event. Reloads and bookmarks don't count twice.
// GTM: Custom HTML tag, trigger Page View on your thank-you page only.
(function () {
  var CURRENCY = 'USD';                          // used when the URL has no currency
  var PRICES = { 'pro-plan': 49, 'starter': 19 };  // optional: ?product=pro-plan when the URL has no value
  var q = new URLSearchParams(location.search);
  var provider = '', id = '', value = parseFloat(q.get('value')), currency = q.get('currency') || '';

  // Stripe Checkout or Payment Link: redirect URL ends with ?session_id={CHECKOUT_SESSION_ID}
  if (/^cs_(test|live)_/.test(q.get('session_id') || '')) {
    provider = 'stripe'; id = q.get('session_id');
  // PayPal Payments Standard with Auto Return and PDT: PayPal adds tx (and often amt, cc, st)
  } else if (q.get('tx')) {
    if (q.get('st') && q.get('st').toLowerCase() !== 'completed') return;   // skip pending payments
    provider = 'paypal'; id = q.get('tx');
    if (isNaN(value)) value = parseFloat(q.get('amt'));
    currency = currency || q.get('cc') || '';
  // PayPal JS SDK buttons: your onApprove code redirects to ?paypal_order=<order ID>
  } else if (q.get('paypal_order')) {
    provider = 'paypal'; id = q.get('paypal_order');
  }
  if (!id) return;
  id = id.slice(0, 64);   // Google Ads accepts transaction IDs up to 64 characters

  var product = q.get('product') || '';
  if (isNaN(value)) value = PRICES[product] || 0;

  // Count each order once, even if the page is reloaded or bookmarked.
  var seen = [];
  try { seen = JSON.parse(localStorage.getItem('mdn_orders') || '[]'); } catch (e) {}
  if (seen.indexOf(id) > -1) return;
  seen.push(id);
  try { localStorage.setItem('mdn_orders', JSON.stringify(seen.slice(-50))); } catch (e) {}

  window.dataLayer = window.dataLayer || [];
  window.dataLayer.push({ ecommerce: null });   // clear the previous ecommerce object
  window.dataLayer.push({
    event: 'purchase',
    checkout_provider: provider,
    ecommerce: {
      transaction_id: id,
      value: value,
      currency: (currency || CURRENCY).toUpperCase(),
      items: [{ item_id: product || provider, item_name: product || provider + ' checkout', price: value, quantity: 1 }]
    }
  });
})();
</script>

In plain words: the tag looks for a Stripe Checkout session ID (it always starts with cs_test_ or cs_live_), a PayPal tx, or your own paypal_order. It skips PayPal payments marked as pending. It takes the value from the URL, or from your price list. It cuts the ID to 64 characters, because that’s the Google Ads limit. Then it checks whether this order was already counted in this browser, and only pushes purchase the first time.

I tested it in a headless browser: a Stripe test session with a value, a Stripe session using the price list, a reload of the same page (not counted again), a PayPal PDT return, a pending PayPal payment (skipped), a PayPal JS SDK return, a fake session_id (ignored), a 74-character ID (cut to 64), a plain visit with no ID, and a browser with storage blocked. All passed with no errors.

Phase 4: Create the Variables and the Purchase Trigger

1. Create four Data Layer Variables: ecommerce.transaction_id, ecommerce.value, ecommerce.currency and checkout_provider.
2. Create a trigger: Custom Event, event name purchase. Call it CE – purchase.
3. If your site already pushes a purchase event for other orders (WooCommerce, Shopify), add a condition so this trigger only fires when checkout_provider is not empty.

Phase 5: Fire Google Ads, GA4 and Meta on the Purchase

1. Google Ads: add a Google Ads Conversion Tracking tag with your purchase conversion ID and label. Set Conversion Value to the value variable, Transaction ID to the transaction ID variable, and Currency Code to the currency variable. Trigger: CE – purchase.
2. GA4: add a Google Analytics: GA4 Event tag, event name purchase, and tick Send Ecommerce data with data source Data Layer.
3. Meta: fire a Purchase event with value and currency, and pass the transaction ID as the event ID. You’ll need that same ID for the Conversions API in Phase 7.
4. Keep the Conversion Linker on All Pages.

Google’s help page says that when two conversions arrive with the same transaction ID, the second one isn’t counted. That’s your safety net if the page ever fires twice in different browsers.

Phase 6: Test with Stripe Test Mode and the PayPal Sandbox

1. Turn on GTM Preview, then pay a Stripe test Payment Link with the test card 4242 4242 4242 4242.
2. When you land on the thank-you page, select the purchase event in Tag Assistant and check the Data Layer tab: transaction ID, value and currency.
3. Check that the Google Ads, GA4 and Meta tags fired once on that event.
4. Reload the page. No second purchase event should appear.
5. Repeat with a PayPal sandbox buyer account, and check that tx arrives in the URL.

Phase 7: Catch the Buyers Who Never Come Back

1. Some buyers close the tab after paying. Stripe also notes that bank debits and vouchers can take 2 to 14 days to confirm. None of these will ever load your thank-you page.
2. Stape’s own Stripe purchase tracking guide takes the session_id from the thank-you page and lets server-side GTM fetch the full order from the Stripe API, so your secret key stays on the server.
3. For payments with no return visit, use Stripe’s checkout.session.completed webhook, or an n8n, Make or Zapier flow, to send the sale to Google Ads as an offline conversion. My offline conversion tracking guide covers the Google Sheet and Data Manager side.
4. Send the same purchase to the Meta Conversions API with the same event ID, so Meta counts it once.
5. Host server-side GTM on Stape (or Stape EU). Not sure you need it? Read Google tag gateway vs server-side tracking.

Phase 8: Check Consent and Compare the Numbers Every Week

1. Make sure your cookie banner feeds Google Consent Mode v2 on the thank-you page too. Test it with the free Consent Mode checker.
2. Every week, compare Stripe and PayPal payments with GA4 purchases and Google Ads conversions for the same dates. A Looker Studio table with the three side by side makes gaps obvious.
3. If Google Ads is far below Stripe, look first at buyers who didn’t return, then at consent, then at redirects that drop the URL parameters.

Stripe Google Ads Conversion Tracking: The Full Data Flow

Testing & Validation Workflow

1. Redirect test. Pay a Stripe test link. The thank-you URL shows session_id=cs_test_..., not the literal {CHECKOUT_SESSION_ID}.
2. Event test. GTM Preview shows one purchase event with the right value and currency.
3. Reload test. Reloading the page doesn’t push a second purchase.
4. Referral test. In GA4 DebugView or Realtime, the session source stays google / cpc, not stripe.com.
5. Google Ads test. After a day, the conversion action shows the test purchase with its value (remove test orders before you scale spend).
6. Weekly test. Stripe payments, GA4 purchases and Google Ads conversions are within a small, explainable gap.

Troubleshooting Common Mistakes

Mistake 1: The URL shows {CHECKOUT_SESSION_ID} as text

The Problem: the thank-you URL has the literal template instead of a real ID, so nothing fires.

The Cause: the braces were URL-encoded or typed with the wrong name in the redirect field.

The Solution: paste {CHECKOUT_SESSION_ID} exactly as written, with curly braces, in the Stripe redirect URL.

Mistake 2: Purchases show a value of 0

The Problem: Google Ads counts the conversion but the revenue is empty.

The Cause: the Stripe redirect has a session ID but no value, and the product isn’t in the price list.

The Solution: add &value= to each Payment Link redirect, fill PRICES, or let server-side GTM read the real amount from Stripe.

Mistake 3: GA4 credits stripe.com or paypal.com

The Problem: your revenue sits under a payment referral, not under Google Ads.

The Cause: the payment domains aren’t in the unwanted referrals list.

The Solution: add them in GA4 under Configure tag settings, then test a new purchase. Old sessions won’t change.

Mistake 4: The same order counts two or three times

The Problem: one Stripe payment shows as several conversions.

The Cause: the thank-you page fired on reloads, or the Google Ads tag has no transaction ID.

The Solution: use the tracker’s repeat check and map the Transaction ID field in the Google Ads tag.

Mistake 5: PayPal buyers never trigger anything

The Problem: Stripe purchases track, PayPal purchases don’t.

The Cause: Auto Return or Payment Data Transfer is off, so buyers stay on PayPal or return without tx.

The Solution: turn both on in Website preferences, set the Return URL, and catch the rest server-side.

What to Set Up Next

• Build clean campaign links for your Stripe Payment Links with the free UTM builder. Stripe passes those UTMs to your redirect URL.
• Selling on WooCommerce as well? See how I fix missing WooCommerce purchases in GA4.
• Running Google Ads at scale? My Google Ads tracking specialist page shows what I set up for clients.

Want it done for you? See my third-party checkout conversion tracking services and ecommerce server-side tracking service.

Conclusion

Stripe and PayPal aren’t hiding your sales. They just hand the buyer back to you, and most setups don’t catch them when they arrive.

Start with the redirect. Once every Payment Link and PayPal button lands on your thank-you page with an order ID, the GTM part is the easy bit. Then add the server-side backup, because some buyers will always close the tab, and compare your Stripe numbers with Google Ads every week until the gap stops surprising you.

Summary by MD Niamul

Stripe Google Ads conversion tracking works when Stripe or PayPal sends the buyer back to a thank-you page on your own domain with the order ID in the URL. I set the Stripe Payment Link or Checkout redirect to ?session_id={CHECKOUT_SESSION_ID} plus the value and currency, and turn on PayPal Auto Return with Payment Data Transfer so tx arrives. A Google Tag Manager Custom HTML tag on that page reads the ID, cuts it to 64 characters, skips orders it already counted, and pushes a GA4 purchase event. Google Ads, GA4 and Meta tags fire on it with the value and the transaction ID, and Stripe and PayPal go in the GA4 unwanted referrals list. Buyers who close the tab need a server-side backup through the Stripe API or webhooks. I wrote this from setting up checkout tracking for my own clients.