Stripe
TrueMetriks tracks every Stripe payment and sends it back to your ad platforms. The video below walks through the full setup; written steps and screenshots are underneath.
Set this up with AI
Copy this prompt into ChatGPT, Claude or whichever AI you use. It carries this whole guide, the pages it depends on, and a link to every video, so it can walk you through it one step at a time.
Connect Stripe to TrueMetriks
Video guide
The connection has two halves - tell Stripe where to send events (steps 1-7) and paste the signing secret back into TrueMetriks (steps 8-10).
Step 1 - Open Stripe Developers and click Webhooks
Inside the Stripe dashboard, click the Developers button in the bottom-left corner. The Developers menu opens. Click the highlighted Webhooks link.
Step 2 - Click Add destination
On the Event destinations page, click the highlighted + Add destination button in the top-right.
Event destinations
Send events from Stripe to webhook endpoints and cloud services.
Step 3 - Configure your event destination
Two things on this screen:
- Event destination scope - pick Your account (highlighted). Connected accounts only applies if you run a Stripe Connect platform.
- API version - leave it on your current default (
2024-12-18.acaciais fine; any current or latest version works).
Configure your event destination
Event destination scope
View docs on event destination scopes
Your account
Events from resources in your account. For Accounts v2, this includes events for accounts created directly within your account.
Connected accounts
Events from resources inside your connected accounts - including their payments, customers, and payment methods.
API version
Step 4 - Select the events TrueMetriks listens for
Scroll down to the Events section. Search and check all three of these:
checkout.session.completed- one-time Stripe Checkout payments + the first payment of any subscription started via Checkout.invoice.payment_succeeded- the first payment of a subscription started without Checkout, every subscription renewal, and every manually-sent invoice (e.g. you invoice a buyer after a discovery call).charge.refunded- every refund of those payments, full or partial. See Refunds.
The first two cover every successful payment, and the third covers refunds. Do not subscribe to charge.succeeded (it overlaps with the payment events above and would double-count).
Events
checkout.session.completed
Occurs when a Checkout Session has been successfully completed.
invoice.payment_succeeded
Occurs whenever an invoice payment attempt succeeds.
charge.refunded
Occurs whenever a charge is refunded, including partial refunds.
The Selected events counter should show 3. Click Continue.
Step 5 - Pick Webhook endpoint as the destination type
Stripe asks where to send the events. Pick the highlighted Webhook endpoint tile, then click Continue.
Choose where you want to send events
Stripe can send events to a webhook endpoint, Amazon EventBridge, or Azure Event Grid.
Destination type
Webhook endpoint
Send webhook events to a hosted endpoint.
Amazon EventBridge
Send events to your AWS account.
Azure Event Grid
Send events to your Azure account.
Step 6 - Copy the webhook URL from TrueMetriks
Open TrueMetriks in another tab. Go to Settings > Integrations and click the highlighted Stripe tile.
Integrations
Connect third-party data sources to fire events into TrueMetriks.
Typeform
Connected
Calendly
Connected
Microsoft Clarity
Configured (1 project)
Stripe
Not connected
Whop
Not connected
On the Stripe page, click the highlighted Copy button next to the Your webhook URL field. The URL looks like https://q.<your-domain>/w/stripe.
Stripe Not connected
Fire offline conversions when a Stripe payment completes. Paste your webhook signing secret from Stripe and add the URL below as a webhook endpoint in your Stripe dashboard.
Your webhook URL
Webhook signing secret
Step 7 - Paste the URL into Stripe and create the destination
Back in Stripe, fill in the Configure destination form:
- Destination name - anything that helps you recognise it later. "TM Purchase" works.
- Endpoint URL - paste the URL you just copied from TrueMetriks.
Click the highlighted Create destination button.
Configure destination
Tell Stripe where to send events and give your destination a helpful description.
Destination name
11/100 characters
Endpoint URL
Webhooks require a URL to send events to.
Step 8 - Copy the signing secret
Stripe creates the destination and lands you on the Destination details page. Scroll to the Signing secret card. Click the highlighted copy icon to copy the whsec_... value.
Destination details
Signing secret
Use this secret to verify that events come from Stripe. You can always view or roll this secret from the destination details page.
Step 9 - Paste the signing secret in TrueMetriks and click Connect Stripe
Switch back to the TrueMetriks Stripe page. Paste the whsec_... value into the Webhook signing secret field, then click the highlighted Connect Stripe button.
Stripe Not connected
Fire offline conversions when a Stripe payment completes. Paste your webhook signing secret from Stripe and add the URL below as a webhook endpoint in your Stripe dashboard.
Your webhook URL
Webhook signing secret
Step 10 - Connected
The page flips to the connected state, showing a green Connected pill and the date you connected. That is the setup done.
Stripe Connected since 31/05/2026
Fire offline conversions when a Stripe payment completes. Paste your webhook signing secret from Stripe and add the URL below as a webhook endpoint in your Stripe dashboard.
Your webhook URL
Subscriptions and renewals
Subscriptions need nothing extra. TrueMetriks reads Stripe's billing reason on every invoice and labels each payment as a new sale or a renewal.
The first payment of a subscription is a new sale. It is recorded once, whether it arrives from Checkout, from the subscription's first invoice (so a subscription started without Checkout is recorded too), or from both.
A renewal is every later charge on the same subscription: the monthly or yearly rebill, and usage-based charges.
A plan change, a manually-sent invoice and a resubscribe after a cancellation count as new sales.
Free trials. A $0 trial start is recorded but is not a sale. The first paid charge after the trial is the new sale, and the charges after it are renewals.
Renewals inside TrueMetriks. A renewal stays a Purchase in your dashboard, so Total revenue includes it. It is credited to the channel that won the subscription's start (the first sale, or the trial signup for a free trial). This applies going forward: payments made before launch are not relabelled.
What your ad platforms receive. A first payment always goes to your ad platforms as a Purchase. For renewals, open Settings > Integrations, click the Subscription renewals tile and pick one under Send renewals to ad platforms as: a custom event (named Renewal unless you change it), a Purchase, or don't send. The tile shows the current choice. The setting is one per site and covers every payment source.
Sites that existed before this setting started on Purchase, so nothing changes for them until they pick another option. Sites created after launch start on a custom event named Renewal.
When renewals go out as a custom event or are not sent, they are not uploaded to Google Ads. When they go out as a Purchase, they upload to Google Ads like any other Purchase.
On Facebook, a custom conversion keyed on Purchase does not fire for a renewal sent as a custom event.
Known limits. A subscription that started before launch keeps its current crediting unless the source supplies a start date. A free trial that is running at launch labels its first paid charge as a renewal for one trial length.
See Revenue for how renewals show in your dashboard.
Refunds
Refunds need the charge.refunded event from Step 4. If you connected Stripe before refunds were supported, open your destination in Stripe, click Edit destination, add charge.refunded to the events and save.
A refund in Stripe, full or partial, is taken off the sale it belongs to. The sale keeps its date and its ad, so the refund lowers revenue, ROAS and profit on the day of the sale. See Refunds on the Revenue page.
Several partial refunds of one payment. Stripe sends the total refunded so far, so each new refund replaces the one before and the sale is never reduced twice.
Refunds never go to your ad platforms. They only change your numbers in TrueMetriks.
Known limit. A refund of a payment TrueMetriks recorded before refunds were supported may not find its sale. It then changes nothing.
Disputes and chargebacks are not taken off.
Verify
Trigger a payment in Stripe and the matching Purchase event shows up in the TrueMetriks dashboard within a few seconds. If the customer's journey is connected to an ad, that Purchase also lands in your connected ad platforms: Facebook CAPI, Google Ads, GA4, TikTok.
Frequently asked questions
Which Stripe events should I subscribe to?
Three: checkout.session.completed and invoice.payment_succeeded for payments, and charge.refunded for refunds. Together they cover every successful payment and every refund. Do not add charge.succeeded, since it overlaps and would double-count.
Will a new subscription's first payment count twice?
No. Stripe fires both events for the first payment, but TrueMetriks records it once and skips the duplicate. Renewals and manually-sent invoices are recorded too, and each renewal is labelled as a renewal.
Are subscription renewals sent to Facebook as a Purchase?
You choose. In Settings > Integrations, the Subscription renewals tile lets you send renewals as a custom event (named Renewal unless you change it), as a Purchase, or not at all. The first payment of a subscription always goes as a Purchase.
Does the Stripe revenue reach my ad platforms?
Yes. If the customer's journey is connected to an ad, TrueMetriks forwards the Purchase to every connected platform: Facebook CAPI, Google Ads, GA4, and TikTok.
Are Stripe refunds taken off my revenue?
Yes, with the charge.refunded event subscribed. A full or partial refund is taken off the sale it belongs to, on the sale's date, so revenue, ROAS and profit are after refunds. Refunds are never sent to your ad platforms.