Virling joins every visit to the payment that followed, so you see which channels bring paying customers. One binary, no database to run.
X sent 44% of visitors and 10% of revenue. A visitor from ChatGPT was worth 24 times one from X. Example data.
Click any payment to see the visits before it: where they first came from, what they read, and what made them buy.
Credit goes to the last channel that wasn't direct, or the first touch if you prefer. Renewals keep the source of the first payment.
Download it, start it, add the script tag. Events and settings live in embedded storage next to the binary, so a backup is a file copy.
$ curl -fsSL https://virling.com/install | sh
$ virling serve
listening on http://0.0.0.0:8080
# then add one tag to your site
<script defer src="https://stats.you.com/v.js"
data-site="you.com"></script>
$ docker run -d -p 8080:8080 \
-v virling:/data \
ghcr.io/virling/virling:latest
# then add one tag to your site
<script defer src="https://stats.you.com/v.js"
data-site="you.com"></script>
Virling pulls payments and refunds itself. No webhooks to set up, no write access to your account.