How do you track Stripe and Paddle game sales by source?
Tie three things to one player ID: the visit that came from your link, the checkout, and the payment webhook. Tag every link with UTM parameters or a short link, run analytics on the page where players buy, give the buyer an ID before checkout, and pass that ID to Stripe or Paddle. When the payment webhook arrives with the ID, your analytics can credit the visits that came before it.
Neither provider knows where a buyer came from on its own. Stripe Checkout and Paddle Checkout record the payment, the customer and whatever you attach. So the attribution happens in your analytics, and the provider only has to carry your ID from the checkout to the webhook. That is the part most direct stores skip, and it is why their sales show as Direct.
This works for any direct sale: the full game as a DRM-free download, a supporter pack, a soundtrack, a Steam key bundle or an unlock inside a web game. The rest of this page shows where each provider lets you put the ID, which webhook events to read, and how refunds, currencies, taxes and fees change the numbers.
Sources: Stripe Checkout Sessions API and Metadata documentation; Paddle custom data documentation; all read 19 November 2026.
How does a sale get its source and campaign?
Through the player's visits, not through the payment. A visit carries the UTM fields of the link that brought it. The payment carries your player ID. Your analytics joins the two on that ID and credits the source and campaign of the visits by the attribution model you choose.
A short link helps where you cannot tag the URL by hand, such as a creator's video description. It adds the UTM fields to the target URL and counts the click. Stripe Payment Links also accept UTM fields, but Stripe only says it passes them on to your redirect URL: "When customers complete a payment, your redirect URL contains the UTM code parameters specified in your payment link URL." That needs the redirect confirmation behavior, and the values must use "alphanumeric characters, dashes, or underscores" within 150 characters.
Send players to a page of your own first, then to checkout. A link that goes straight to a hosted checkout skips your analytics, and the sale has no visit to credit.
- Tag each post, creator, ad and newsletter link with utm_source and utm_campaign, or create a short link for it.
- Send the link to your own store page or web game page, where the web SDK runs.
- When the player buys, create or reuse a player ID and identify the browser with it.
- Pass the same ID to the checkout as user_id, as the next section shows.
- Let the payment webhook bring the ID back, and read revenue by source in your reports.
Sources: Stripe, Track a payment link, read 19 November 2026; our practice.
Where do Stripe and Paddle let you attach your own ID?
Stripe has several places, and they do not copy into each other. Stripe says: "An object's metadata doesn't automatically copy to related objects." So metadata on a Checkout Session stays on the session. For a one-time sale, set it on the object your webhook reads: the Checkout Session itself if your webhook reads checkout.session.completed, the PaymentIntent with payment_intent_data.metadata, or the invoice with invoice_creation.invoice_data.metadata. For a subscription, Stripe copies subscription metadata to each invoice in parent.subscription_details.metadata.
Paddle Billing has one place: custom_data. Paddle says: "Custom data lets you add your own key-value data to subscriptions, transactions, and some other entities in the Paddle API created using Paddle Checkout or the API." Its own example puts utm_source and utm_medium there. Paddle also copies it forward: "Where a transaction has custom data against it, that data is copied to the created subscription for your reference."
Use an opaque ID, not an email. Stripe warns: "Never store sensitive information, such as bank account information or credit card details, to metadata." Stripe also says a client_reference_id on a payment link should not include "sensitive information or secrets such as passwords or API keys." An ID like player_8f3k2 is enough. That last part is our advice.
| Provider | Field | What the provider says | Read by Manalens |
|---|---|---|---|
| Stripe | client_reference_id | "A unique string to reference the Checkout Session. This can be a customer ID, a cart ID, or similar, and can be used to reconcile the session with your internal systems." Up to 200 characters. | Yes. Links the sale when there is no metadata user_id. |
| Stripe | metadata on the Checkout Session | "Set of key-value pairs that you can attach to an object." Up to 50 keys, keys up to 40 characters, values up to 500. | Yes. user_id here links the sale. |
| Stripe | invoice_creation.invoice_data.metadata | invoice_creation: "Generate a post-purchase Invoice for one-time payments." | Yes. user_id here links the sale. Not needed: the session itself is read. |
| Stripe | subscription_data.metadata | Copied to each invoice of the subscription, in parent.subscription_details.metadata. | Yes. user_id here links each renewal. |
| Paddle Billing | customData in Paddle.Checkout.open() | "Pass customData to the Paddle.Checkout.open() method to add custom data to the created transaction." | Yes. user_id in custom_data links the sale. |
Pass the same player ID to analytics and to the checkout
// Browser: link this visitor to a player ID before checkout (web SDK).
await analytics.identify('player_8f3k2');
// Server: a one-time Stripe Checkout sale. No invoice is needed.
await stripe.checkout.sessions.create({
mode: 'payment',
line_items: [{ price: 'price_supporter_pack', quantity: 1 }],
client_reference_id: 'player_8f3k2',
metadata: { user_id: 'player_8f3k2' },
success_url: 'https://example.com/thanks',
});
// Browser: a Paddle Billing checkout for a soundtrack.
Paddle.Checkout.open({ items: [{ priceId: 'pri_soundtrack', quantity: 1 }], customData: { user_id: 'player_8f3k2' } });Sources: Stripe Checkout Sessions API, Metadata and Track a payment link; Paddle, Work with custom data; all read 19 November 2026.
Which webhook events record a sale and a refund?
For Stripe, the sale is invoice.paid when an invoice exists, and checkout.session.completed when any Checkout Session completes. A one-time Checkout payment has no invoice unless you ask for one, so read checkout.session.completed for it, and checkout.session.async_payment_succeeded for a delayed payment method. Count a session with an invoice once, from invoice.paid. If you want invoices anyway, Stripe says: "For one-time payments, turn on invoice creation for each payment link or Checkout Session." It is priced separately: "0.4% on the transaction total", "up to a maximum of $2 USD (or local currency equivalent) per invoice." The refund is charge.refunded, which Stripe describes as "Sent when a charge is refunded, including partial refunds."
For Paddle Billing, the sale is transaction.completed: "Occurs when a transaction is completed." A refund is an adjustment, sent as adjustment.created and adjustment.updated while Paddle reviews it.
Both providers retry and neither keeps order. Stripe "attempts to deliver events to your destination for up to three days with an exponential back off in live mode" and "doesn't guarantee the delivery of events in the order that they're generated." Paddle expects a reply within five seconds, and "For live accounts, we make up to 60 attempts in total over about two days." Both say the same event can arrive more than once, so a handler must skip events it has seen.
Sources: Stripe, Receipts and paid invoices, Webhooks and Refunds; Stripe Support, post-payment invoice pricing; Paddle, transaction.completed, Handle webhook delivery and How webhooks work; all read 19 November 2026.
How should you handle refunds?
Record each refund as its own negative event, linked to the payment it refunds, and keep the original sale. Then you can read gross sales, refunds and net sales side by side, and take the refund off the campaign that got credit for the sale.
Stripe keeps its fee on a refund: "Stripe's processing fees from the original transaction aren't returned." The buyer "sees the refund as a credit approximately 5-10 business days later, depending upon the bank." You can refund part of a payment, and more than once, but not more than the original charge.
Paddle refunds can wait for approval: "Most refunds for live accounts have to be approved by Paddle." A refund starts as pending_approval and moves to approved or rejected. Paddle approves a refund automatically on a verified, active account when it is 400 USD or less, or the equivalent, and less than your balance. Count a Paddle refund only when it is approved.
Sources: Stripe, Refund and cancel payments; Paddle, Refund or credit a transaction; both read 19 November 2026.
How do currencies, taxes and fees change the numbers?
Keep each sale in the currency the buyer paid, and convert only in reports. Stripe amounts are integers in "the charge currency's smallest currency unit", and Paddle sends a three-letter ISO 4217 currency_code with each transaction. A report that adds euros and dollars without a stated rate gives a number nobody can check.
Know whether an amount includes tax. With plain Stripe you are the seller, so any tax you charge sits inside the amount paid. Paddle is the merchant of record and splits the totals: grand_total is "Total due on a transaction after credits but before any payments", grand_total_tax is the "Net tax amount included in grand_total", fee is the "Total fee taken by Paddle for this transaction", and earnings is "the total minus the Paddle fee."
So decide which number answers your question. For comparing channels, the amount the buyer paid is fine, because tax and fees are a similar share of every sale. For a payout, use Paddle earnings or the Stripe balance, not your analytics.
Sources: Stripe, Refund and cancel payments; Paddle, transaction.completed; both read 19 November 2026; our practice.
Should you use Paddle Billing or Paddle Classic?
Paddle Billing, if you have the choice, because it is the current product and its webhooks carry custom_data. Paddle says: "In August 2023, we released a new version of Paddle called Paddle Billing." It also says: "If you signed up for Paddle before August 8, 2023, then you have Paddle Classic."
Paddle's documentation index says: "Paddle Billing and Paddle Classic are distinct products with different implementations, APIs, and features." Classic signs webhooks in the payload, while Billing uses a Paddle-Signature header. So a guide or tool for one does not fit the other. Check which one your account uses before you build the checkout.
Sources: Paddle Billing explained for Paddle Classic users; Paddle developer documentation index; both read 19 November 2026.
How do you set this up in Manalens?
Connect the provider under Settings, then Integrations, with the owner or admin role and a verified MFA session. Each signed webhook becomes an event: a payment is purchase, a refund is refund with a negative amount, and the channel is stripe or paddle, which a website or game cannot send. Signing secrets and read keys are encrypted and never returned to the browser.
A payment links to a player in two ways: a user_id in the Stripe Checkout Session, invoice or subscription metadata or in the Paddle custom_data (for a Checkout Session with no user_id, its client_reference_id), or an identify trait stripe_customer_id or paddle_customer_id. A refund has no metadata of its own, so it takes the player of the other records of the same provider customer when they name exactly one player. A customer ID that matches more than one player stays unassigned, and email is never used to guess.
A one-time Checkout payment with no invoice is counted from checkout.session.completed, under its payment intent, so its refund links to it. A session with an invoice is counted once, from invoice.paid. For Stripe, attribution takes a refund off the payment it refunds only when the refund names it. On Stripe API versions from 2025-03-31 the refund does not name the invoice, so add the read API key to let the link be looked up. The table shows what is read today and what is not yet.
- In Settings, Integrations, click Create webhook endpoint in the Stripe or the Paddle section.
- Register that URL in Stripe or Paddle. For Stripe, send invoice.paid, checkout.session.completed, checkout.session.async_payment_succeeded, charge.refunded and customer.subscription events. For Paddle, send transaction.completed, adjustment.created, adjustment.updated and subscription events.
- Copy the provider's signing secret into Webhook signing secret and click Save signing secret. Ingestion starts.
- For one-time Stripe Checkout sales, put user_id in the Checkout Session metadata or the player ID in client_reference_id. No invoice is needed. For Paddle, put user_id in customData.
- Optional: add a restricted Read API key with read access to invoices or transactions, refunds or adjustments, and subscriptions (for Stripe, also Checkout Sessions), and import past payments.
- Make a test purchase and a test refund in test mode or the sandbox, and check both rows in Activity.
| Data | Today |
|---|---|
| Stripe invoice.paid, including one-time Checkout payments with invoice creation on | Yes. A purchase event with the amount paid |
| Stripe checkout.session.completed and async_payment_succeeded for a one-time payment without an invoice | Yes. A purchase event with the session total, counted once |
| Stripe payment_intent.succeeded without a Checkout Session | Not yet. Use Checkout or a Payment Link, or turn on invoices |
| Stripe charge.refunded | Yes. A refund event with a negative amount |
| Paddle Billing transaction.completed | Yes. A purchase event with the grand total |
| Paddle Billing refund adjustments with status approved | Yes. A refund event with a negative amount |
| Paddle Classic webhooks | Not yet. Paddle Billing only |
| user_id in Stripe Checkout Session, invoice or subscription metadata, or in Paddle custom_data | Yes. Links the payment to the player |
| Stripe client_reference_id on a Checkout Session | Yes. Links the payment when there is no metadata user_id |
| identify traits stripe_customer_id and paddle_customer_id | Yes. Links every payment of that customer |
| UTM values stored in metadata or custom_data | Not yet as a source. The source comes from the player's own visits |
| Provider fees and Paddle earnings | Not yet. Amounts are what the buyer paid, tax included |
| Past payments | Yes. Import with a restricted read API key |
Sources: Manalens revenue documentation and code (apps/api/src/revenue.ts), read on 20 November 2026.
Which reports should you read?
Read revenue by source first, then by campaign, and only then by single sale. In Manalens, four places show Stripe and Paddle payments.
Overview: the Revenue metric adds payments net of refunds, with a legend for each source (your own events, Stripe, Paddle, itch.io and Steam). A payment takes the source, country and device of the buyer's first website page view in the 90 days before it. Attribution: choose the goal purchase, group by source or campaign, and compare the six models. Activity: each payment and refund is a row, such as "Paid $15.00 (Stripe)". A player profile: that player's visits and payments in one list.
Reports convert every currency to the report currency with the European Central Bank reference rate of the day, which is not the rate Stripe or Paddle used. Add currency_mode=only to a report URL to count one currency without conversion.
Sources: Manalens revenue and attribution documentation, read on 19 November 2026.
How do you measure the result?
Manalens is the analytics and growth engine built for games. Once the webhook is connected, check two numbers each week: the share of payments that have a player, and net revenue by source in Attribution with the goal purchase. A low share means the user_id is missing from the checkout, so fix that before you judge any channel.
A click on a store link is not a sale, and a sale is not profit: amounts are what the buyer paid, before Stripe or Paddle fees. Compare channels with each other, not with your payout. To set direct sales next to the stores, add the itch.io purchase match by email, and the automatic Steam sync (in early access), which adds Steam net sales by day to the Revenue metric.
- Match itch.io purchases to players by email →
- Web game analytics on Poki, CrazyGames and itch.io →
- How much do web games earn? →
Sources: Manalens revenue, itch.io and Steam documentation, read on 19 November 2026.
Frequently asked questions
Can Stripe tell me which campaign brought a sale?
Not by itself. Stripe records the payment and what you attach. Payment Links pass UTM fields on to your redirect URL, and client_reference_id carries one ID to the checkout.session.completed webhook. To see sales by source, join the payment to the visits of the same player in your analytics.
Is client_reference_id or metadata better for attribution?
Use the field your analytics reads. client_reference_id lives on the Checkout Session only. Metadata does not copy between Stripe objects, so put the ID on the object your webhook reads: the PaymentIntent, the invoice, or the subscription. Manalens reads user_id in Checkout Session, invoice or subscription metadata, and client_reference_id on a Checkout Session.
Should I put UTM values in Paddle custom data?
You can, and Paddle shows that in its own example, but it only gives you the last touch you saved. A player ID in custom data is more useful, because your analytics can then credit every tagged visit of that player. Manalens reads user_id from custom_data, not the UTM values.
Do refunds come off the campaign that got credit?
They should. In Manalens a refund is a negative event, and attribution takes it off the payment it names. Paddle refunds name their transaction. Stripe refunds on API versions from 2025-03-31 need the read API key so the invoice can be looked up; otherwise attribution stays gross for that refund.
Does Manalens subtract Stripe and Paddle fees?
Not yet. Amounts are what the buyer paid: the Stripe invoice amount paid or Checkout Session total, and the Paddle grand total, tax included. That is fine for comparing channels. For your real income, read Paddle earnings or your Stripe balance, because Stripe also keeps its fee when you refund a payment.
Sources and implementation
- Stripe documentation: Create a Checkout Session (read 19 November 2026) ↗
- Stripe documentation: Metadata (read 19 November 2026) ↗
- Stripe documentation: Receipts and paid invoices (read 19 November 2026) ↗
- Stripe Support: Pricing for post-payment invoices for one time purchases via Checkout and Payment Links (read 19 November 2026) ↗
- Stripe documentation: Track a payment link (read 19 November 2026) ↗
- Stripe documentation: Receive Stripe events in your webhook endpoint (read 19 November 2026) ↗
- Stripe documentation: Refund and cancel payments (read 19 November 2026) ↗
- Paddle Billing developer documentation: Work with custom data (read 19 November 2026) ↗
- Paddle Billing developer documentation: transaction.completed (read 19 November 2026) ↗
- Paddle Billing developer documentation: Refund or credit a transaction (read 19 November 2026) ↗
- Paddle Billing developer documentation: Handle webhook delivery (read 19 November 2026) ↗
- Paddle Billing developer documentation: How webhooks work (read 19 November 2026) ↗
- Paddle Billing developer documentation: Paddle Billing explained for Paddle Classic users (read 19 November 2026) ↗
- Paddle Billing developer documentation: Documentation index for AI agents (llms.txt) (read 19 November 2026) ↗