Get started
Introduction
ProductLense joins your website analytics to your billing, then subtracts ad spend and processor fees, so you see profit per channel.
- 1 Add the script One tag, about 2.3 KB, no cookies.
- 2 Connect billing Read-only, imports 12 months of payments.
- 3 Identify signups Links payments to the channel that found them.
- 4 Add ad spend Turns revenue per channel into profit.
Install on your stack
- Script tag
- Next.js
- React (Vite)
- SvelteKit
- Nuxt
- Astro
- WordPress
- Webflow
- Framer
- Shopify
- Google Tag Manager
- Vue (Vite)
- Angular
- React Router
- Remix
- Gatsby
- Hugo and Jekyll
- Express
- Laravel
- Django
- Flask and FastAPI
- Ruby on Rails
- Ghost
- Wix
- Squarespace
- Bubble
- Carrd
- Kajabi
- Podia
- Lovable
- Bolt
- v0 by Vercel
- Replit
- Mobile apps and PWAs
- React Native and Expo
- Flutter
- iOS (Swift)
- Android (Kotlin)
Connect your billing
ProductLense is product analytics for founders who sell online. One script counts visitors without cookies, one billing connection brings in every charge and refund, and ProductLense joins the two at the moment each payment is written. The result is revenue, fees and profit for every channel that sent you a paying customer.
What ProductLense answers
- Which channel brought the customers who pay, not just the visitors who click.
- How much each channel earned after processor fees and refunds.
- Whether a paid channel makes money once its ad spend is subtracted.
- How revenue from each channel holds up month after month.
How the pieces fit
| Piece | What it does | Where to start |
|---|---|---|
| Tracking script | Counts pageviews, sessions and custom events, about 2.3 KB gzipped, no cookies | Install the script tag |
identify | Links a visitor to your own user id after signup or login | Identify users |
| Billing connection | Reads customers, subscriptions, payments, refunds and fees from your provider | Connect billing |
| Ad spend | Spend per channel and campaign, entered by hand or as CSV | Add ad spend |
A payment is attributed through a chain: payment, then customer, then your user id, then the visitor, then that visitor's first touch. Each link is described in How payments are attributed.
Where to go next
- New to ProductLense: follow the Quickstart. It takes about five minutes.
- Want the definitions first: read How ProductLense counts.
- Sending data from a server: see the Events API and the Payments API.
- Checking what is collected: see What ProductLense collects.