See which channel brought the money
A 7 KB script, every report on one screen, and revenue credited to its source. No cookies, no consent banner.
Free forever · about 1,400 visits a month · no card
This is what your dashboard looks like
Last 30 days
Pick a channel to see its revenue
Visitors
2 997
Customers
54
Revenue
23 191 100 UZS
of revenue
100%
Demo site data. Yours will be your own.
Revenue belongs to the channel, not to the last click
How it works today
Google Analytics shows where visitors came from. How much money each source brought is not there: payments happen on your server, not in the browser.
How it works here
You send a payment event from your own server. We find the visitor and credit the sum to the channel that first brought them.
For example
Someone arrives from Telegram, comes back a week later through Google search and buys. The revenue goes to Telegram, because Telegram is what won the customer.
One model, first touch. There is no choice of models yet.
The week-long example needs the data-persist="1" attribute: it keeps the id in your site's localStorage. Without it a visitor id changes every day, so visits can only be linked within one day. In the EU, keeping that id may require the visitor's consent — that call is yours.
Channel report
-
Telegram 31 14 273 000 UZS
-
Direct 11 4 873 200 UZS
-
Google 10 3 522 400 UZS
-
Instagram 2 522 500 UZS
Event from your server
POST https://analitic.my-it.uz/api/v1/event
Authorization: Bearer da_••••••••
{
"name": "order_paid",
"email": "customer@example.com",
"amount": 350000,
"currency": "UZS"
}Coming: Payme, Click, Uzum
What else it does
- CSV export
- Realtime, with a delay measured in seconds
- Goals and events
- UTM tags are merged into readable channels for you
- A 7 KB script
- Every report on one screen
How it differs from Google Analytics
Compared on the points that usually decide the choice.
| Analitic | Google Analytics 4 | |
|---|---|---|
| Script size | 7 KB | about 50 KB |
| Cookies | not used | used |
| Consent banner | not needed | needed |
| First data | within seconds | realtime view, full reports later |
| Revenue by channel | in the main report | requires ecommerce setup |
| Retention | events by plan, daily totals while the account exists | up to 14 months |
| Interface | one screen | sections and a report builder |
Google Analytics does more: cohorts, ad audiences, BigQuery export. If you need those, it is the better fit.
Who this is for
Three situations where visit counts are not enough.
Telegram shop
Traffic arrives from the channel, from Instagram and from search. Orders land in direct messages with nothing tying them to a source.
One order event from the server shows the channel brings fewer clicks than Instagram but more revenue.
Online school
Ads lead to a course page, but payment arrives days later and often from another device.
Revenue is credited to the first touch, so the payment stays attached to the ad that brought the student.
SaaS
Sign-up is free, so the number of sign-ups says nothing about which channel pays off.
A subscription payment event carrying the amount shows revenue per channel, not just sign-ups.
Where the data lives
The servers are in Paris, France — inside GDPR, the strictest personal-data regime there is.
Country and city are resolved from a local database: a visitor address is never sent anywhere.
Three steps to your first numbers
-
Add your site
Give it a domain and a timezone.
-
Paste the script
One line in <head>. SPAs need nothing extra.
-
Read the reports
The first data lands within seconds.
<script defer data-site="YOUR_SITE_ID" src="https://analitic.my-it.uz/js/da.js"></script>