Integrations·Payments
Connect Paddle Billing with an API key. Every purchase, renewal and refund then reaches Spreelytics automatically, credited to the channel the buyer came from.
paddle · payments · 30d
revenue by channel · last-touch · 30-day window
What it does
Transactions arrive as purchase events and flow into goals, the overview and the acquisition reports.
Connecting creates the notification in your Paddle account. Each transaction then arrives by itself, without you sending any revenue events.
Pass the visitor id in customData when you open the checkout. Paddle.js takes it in the browser, so attribution needs no server code at all.
Charge in as many currencies as you like. Each payment is converted once into your reporting currency at the rate for the day it happened, then frozen.
How it works
01
In Settings → Revenue, paste a Paddle Billing API key that can create notifications and read Transactions and Adjustments. Connecting sets up the webhook for you.
02
Open the checkout with customData: { spreelytics_visitor_id: Spreelytics.getVisitorId() }.
03
From the moment you connect, payments land on the Revenue page, with MRR and ARR for subscriptions, and as purchase events in goals, the overview and the acquisition reports.
Read next
Web analytics
Follow each sale back to the channel that earned it.
Read moreWeb analytics
Turn any page or event into a conversion to track.
Read moreWeb analytics
Break down visitors and revenue by where they came from.
Read moreFAQ
What people ask before they switch it on.
A Paddle Billing API key with Write on Notification settings, and Read on Transactions and Adjustments. Connecting uses it to set up the webhook that delivers your transactions. The read permissions let you import transactions from before you connected. Paddle Classic is not supported.
In customData when you open the checkout: Paddle.Checkout.open({ customData: { spreelytics_visitor_id: Spreelytics.getVisitorId() } }). Add spreelytics_session_id beside it if you like.
It is still recorded and counts toward your totals. It just cannot be traced to a channel. The Channels list counts it as Direct and the Sources list as Direct/None. The URLs and UTM lists leave it out.
Each payment counts as one event, the same as a custom event. Refunds do not count. Payments you import from before you connected do not count either.
Yes, for payments Paddle does not see. The revenue API is in the docs. If you also send a Paddle payment that way under a different id, it is counted twice.
Free up to 100k events a month · no credit card
