Website analytics:which pageproduced the enquiry.
Website analytics here starts with the answer no counter gives you: every enquiry card names the page and the section it was sent from — no setup, no goals, no tagged links. The counter itself, Google Analytics or Yandex Metrica, connects with a single identifier in the admin panel, without a line of code: the fields come with the SEO Advanced module — 4,900 ₸ a month, alongside sitemap.xml, robots.txt and canonicals.
Page + section
the source is written on every enquiry card
3 languages
Russian, Kazakh and English versions counted separately
0
repeat enquiries merged into one
What you will be asking in week two
Enquiry attribution — the thing external analytics rarely shows you
A counter counts people; the platform counts enquiries. Which is why “what page brought me this customer” is answered by a line on the card rather than by a report.
Page and section on every card
An enquiry arrives on the board already signed: the page address and the block the form sat in. If a landing page carries the form in two places, you can see which one did the work.
Repeats are never merged
A second enquiry from the same person becomes its own card. A repeat usually means nobody answered the first one — that is something to see, not something to hide.
The language version is visible
Russian, Kazakh and English pages are different pages with different content, so they are different on the card too.
A board instead of an inbox
Enquiries sit on a kanban board by stage rather than in a mail thread: how many are new, how many are in progress and how many have been hanging for a fortnight is something you read off the board, with no export and no formula.
Nothing lands in spam
The enquiry is stored on the site's side rather than sent as an email that may not arrive. The notification is a copy, not the only copy.
It works from the first minutes
Attribution needs no setup, no link tagging and no goals. It is on for as long as the page has a form.
Who counts what: the platform, the counter, and nobody
A short, exact list. The platform does what external analytics does not do at all — it ties a specific enquiry to a specific page and section.
The platform shows
Taken from the enquiries themselves
- The page each enquiry was sent from
- The section or block the form sat in
- The language version of the page
- The date and time of the enquiry
- Repeat enquiries, as separate cards
- The stage the enquiry has reached on the board
Left to the counter
The counter counts traffic, we count enquiries — and it connects in one field
- Visits and unique visitors
- Traffic sources and ad campaigns
- On-page behaviour: scroll depth, click maps
- Funnels, cohorts, audience segments
- Session recordings
- A/B tests
Built as a bespoke project
Outside the subscription — we build it as its own project, from 1,500,000 ₸, on the same site
- Pasting arbitrary code or a tag manager
- A dashboard with charts inside the admin panel
- End-to-end analytics joined to ad accounts
- Call tracking and number substitution
- Export into BI tools
Where the counter identifier goes, and what it covers
Once, in the admin panel, with no template edit and no developer. After that the counter looks after itself.
The counter
The enquiry card
What to look at in the first seven days, in order
The order here is not decorative: each step only makes sense once the previous one has produced data.
Day 1. Install the counter and send yourself a test enquiry
With no traffic there is nothing to read yet — but you can confirm the counter responds and that the form reaches the board. The test card gets deleted afterwards.
Counter recording, enquiry delivered
Day 2–3. Check the page on the cards is the right one
The first real enquiries are the moment to see whether the recorded page matches where the person actually wrote from. If the site has one shared form on every page, it shows up immediately.
Attribution agrees
Day 4–5. Find the pages that stay silent
The counter shows visits, the board shows enquiries. Pages with the first and none of the second are your list of things to fix, and it is usually short.
A list of pages with no enquiries
Day 7. Compare two numbers and make one decision
Visits from the counter and enquiries from the board for the same week. The decision is then simple: few people means work on traffic; plenty of people and few enquiries means work on the page.
One decision for next week
Good web analytics will tell you how many people reached a page, and will not tell you which page brought you this particular customer.
Counters are already free and attach to our sites through a single field, so we put the work into what they do not have: the platform closes the one gap counters leave open — the link between a specific enquiry and the specific page and section it was sent from. The counter counts traffic; the board counts money.
The three pictures you will see most often
Attribution is not useful in itself — it is useful because afterwards you know where to go by hand. All three of these are fixed in the admin panel.
Visits yes, enquiries no
The counter shows the page and not one card has come from it. The problem is usually not traffic: either the page has no form, or the form sits below where people get to. The section holding the form is moved in the editor, with no developer.
Every enquiry from one page
One page collects everything and the rest are quiet. That is a ready-made plan of work: move the form block that did the job onto the two or three pages where an enquiry is actually possible, and leave the reference pages to be read. Moving a section takes a minute in the editor.
Enquiries from a version you never finished
The Kazakh or English page is collecting enquiries on half-translated content. That is not a curiosity, it is the reason to finish it: the people are already there.
The enquiry card, the counter, and a spreadsheet
Three ways to answer “where do the customers come from”. A counter stays useful and connects here in one field — but the part you asked the question for, the platform answers itself.
| The INIT platform | External counter | Manual spreadsheet | |
|---|---|---|---|
| You can see which page produced a specific enquiry | Through configured goals | If somebody typed it in | |
| You can see which section of the page did the work | |||
| The counter connects by identifier, with no code in the template | The script is pasted into the site template | ||
| Every enquiry can be opened and answered, not merely counted | If somebody typed it in | ||
| From the finding to the page edit — in one window | |||
| Unaffected by ad blockers | |||
| Works from launch with no configuration | |||
| A repeat enquiry is visible separately | If somebody noticed |
The counter connects with one identifier in the Analytics tab, which comes with the SEO Advanced module at 4,900 ₸ a month, alongside sitemap.xml, robots.txt and canonicals. “Through configured goals” in the next column is a job of its own: an event on the form, a goal in the counter and tagged pages.
What people ask about analytics before launching
The answers are short because the questions are specific.
Launch a site and watch where the first enquiry comes from
A 3-day trial, no card required. A technical address is issued immediately — the form starts collecting enquiries within minutes, and by the end of the trial you can see which pages bring them.
- A your-name.shardit.app address is issued immediately
- Page-and-section attribution works with no add-on
- Enquiries from the trial site land on the same kanban board
Read next
Neighbouring sections that answer the question this one raises.
