Payments
Know which posts bring Paddle customers
Completed transactions from Paddle Billing, matched to the visit that led to them.
Available to connect- Access
- Read-only
- Connection
- API key
- History
- 90 days, then as they happen
Which post brought your Paddle Billing customers?
For SaaS makers who sell their plans through Paddle Billing. upTake reads completed transactions and ties each one to the visit, the post or the release that brought the customer.
For example: a changelog entry and a LinkedIn post both announce your yearly plan. The completed transactions of the following days are split by source, so you know whether the changelog readers or the LinkedIn audience bought it.
Paddle custom data and your marketing source
Paddle Billing lets you attach custom data to a checkout: the customData option of Paddle.js, or a data-custom-data attribute on the button that opens it. Paddle keeps it on the transaction, copies it to the subscription for recurring items, and returns it in the dashboard, the API and transaction webhooks. Its documentation even uses utm_source, utm_medium and utm_content as example keys.
upTake reads completed transactions with your API key. Without any change to your checkout, each transaction is matched to the visit seen just before it and marked as estimated.
Read on November 18, 2026: Paddle: work with custom data, Paddle.js: Checkout.open().
From a post to a Paddle payment
- 1. The postReddit · r/SideProjectShared with indiepdf.com/?ut=reddit
- 2. Visits and signups1,204 visits · 88 signupsRecorded by the upTake script
- 3. Payments in Paddle9 customers · $431Matched to the visit before the payment
What upTake reads from Paddle
upTake reads your paid orders and subscription payments from Paddle: the amount, the currency, the date, and the identifiers of the payment and of the customer. The first sync goes back 90 days; after that, only what is new is fetched, and a payment already imported is never counted twice. Each payment is then matched to the visit that led to it: exactly when your checkout passes upTake's visitor identifier, otherwise by time, and a payment matched by time is always shown as estimated.
How to connect Paddle
- You need an upTake project first; creating one takes 5 minutes.
- Click Connect on the Integrations page; a small window asks for what Paddle needs.
- API key: 1. In Paddle, open Developer tools → Authentication and create a new API key. 2. Give it Read access to Transactions, Customers and Adjustments. 3. Recommended: also give it Write access to Notification settings. upTake then sets up the webhook for you, nothing else to do in Paddle. 4. Copy the key and paste it here.
- Webhook secret key (optional): The secret key of the destination from step 1. Without it, new payments and refunds arrive with the next automatic sync, within a few hours.
- upTake checks it with Paddle before saving it.
- To receive payments as they happen, in Paddle: Developer tools → Notifications → New destination. Paste this address and tick transaction.completed, adjustment.created and adjustment.updated.
On the Paddle side, see Paddle's documentation on API authentication.
What you see afterwards
Your revenue appears on the overview, split by the source that brought each customer: the post, the link or the release behind it. The weekly report tells you which actions paid and which only brought attention. Revenue is always shown apart from visits, and anything upTake had to estimate is marked as estimated.
Privacy and access
- upTake never reads or stores card numbers. It never moves money, issues a refund or changes anything in your Paddle account.
- Your visitors' IP addresses are never stored.
- Keys and accesses are stored encrypted and never sent back to your browser. Your data is hosted in the European Union.
- Disconnect Paddle at any time: upTake stops at once, and what was imported stays until you delete it.
Questions about Paddle
Does upTake need write access to my Paddle account?
No. upTake only reads payments. It never moves money, issues a refund or changes anything in your Paddle account.
How far back does upTake import Paddle payments?
The first sync goes back 90 days. After that, only new payments are fetched, and a payment already imported is never counted twice.
What happens when a payment cannot be tied to a visit?
It still counts in your revenue, shown as not traced to a source. A payment matched by time instead of by identifier is always marked as estimated.
Can I try it with a Paddle sandbox account?
Yes. A sandbox API key (it starts with pdl_sdbx_) is recognised and the connection is labelled “Paddle (sandbox)”, so test transactions never mix with a live account by mistake.
Do I need to set customData in Paddle.js?
No. upTake works without any change to your checkout, with estimated matches clearly labelled.
Use Paddle in your own project
Free plan · No card · 5-minute setup
Connect PaddleSee Home in the demo