See which traffic sources bring revenue
Visitor counts don't pay the bills. PageLens attributes every payment to the visit it came from, so you see revenue by channel, referrer, UTM campaign, country and landing page — still without cookies.
Connect Stripe or Paddle
Add one webhook in Stripe (checkout.session.completed, invoice.paid) or Paddle (transaction.completed) and paste its signing secret. Pass the same user id to pagelens.identify() and to the checkout, and each payment — including subscription renewals — lands in the buyer's visit. Signatures are verified and retries are counted once.
Or any checkout, with one line
On a thank-you page, call pagelens.track('purchase', { revenue: 49, currency: 'USD' }). It works with Gumroad, Lemon Squeezy, Shopify or your own checkout, and from the iOS and React Native SDKs. Servers can send purchases through the API.
What you see
Revenue, purchases, revenue per visitor and average order, compared with the previous period; a revenue chart; and breakdowns by channel, referrer, UTM source and campaign, country, landing page, device and event. Click any row to filter the whole dashboard.
Read-only by design
PageLens only receives payment notifications. It can't read your Stripe or Paddle account or move money, and the signing secret is stored encrypted.
Create a free PageLens account: 7-day trial, no card, no cookie banner needed.
Start free trialQuestions
What happens to payments PageLens can't match to a visit?
They are still counted, under an Unattributed row, so totals stay correct. Passing the user id to both pagelens.identify() and your checkout maximises matching.
Which currencies are supported?
Any ISO currency. Zero-decimal currencies such as JPY are handled. The report uses the currency with the most purchases in the period and lists the others separately, without conversion.
Do I need cookies for revenue attribution?
No. The purchase is joined to the visit on the server, using the session and the user id you pass at checkout.