Integrations·Payments
Connect your Lemon Squeezy store. Its orders, subscription charges and refunds then come into Spreelytics by themselves, credited to the channel that brought the buyer in.
lemon squeezy · payments · 30d
revenue by channel · last-touch · 30-day window
What it does
Orders arrive as purchase events and flow into goals, the overview and the acquisition reports.
Connecting creates the webhook on your store. Each order and subscription charge then arrives by itself, with no revenue events for you to send.
Add the visitor id to the checkout’s custom data. On a plain buy link, your page adds it as a URL parameter on click, so no backend is needed.
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, enter your store ID and a Lemon Squeezy API key. Connecting creates the webhook on that store.
02
Add Spreelytics.getVisitorId() to the checkout as checkout[custom][spreelytics_visitor_id], or to the buy link when it is clicked.
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.
Your store ID and a Lemon Squeezy API key, entered once in Settings → Revenue. The webhook is created on that one store. The key also reads your past orders when you import them.
In the checkout’s custom data. Through the API that is checkout_data.custom; on a buy link it is the URL parameter checkout[custom][spreelytics_visitor_id], which your page adds when the link is clicked.
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 Lemon Squeezy does not see. The revenue API is in the docs. If you also send a Lemon Squeezy payment that way under a different id, it is counted twice.
Free up to 100k events a month · no credit card
