Which car actually gets looked at — and which turns into an enquiry

Without this

You know how many cars you have, and not which ones people look at. So you cut the price on a car that will not move, assuming price is the problem, when the problem is that nobody has opened its page at all. Meanwhile a car that is viewed constantly and enquired about never tells you something else entirely — but you do not know which case you are in, so the decision is a guess and the loss is real.

What is measured, and what is not

• One row per car per day: a number that grows, not a new row per visit — so the data stays light however large your storefront gets
• No cookies, no visitor identifier, no device fingerprint
• And what is used to spot a repeat within half an hour is never stored and never logged anywhere
• A thirty-day window for views, with empty days shown as visible zeros so the axis does not shrink and make a flat spell look busy
• The five most-viewed cars, by the car’s name rather than its id
• Enquiries in five types: general enquiry, booking, purchase, availability question, viewing request
• A conversion rate: closed divided by total — and an enquiry curve over the last seven days
• CSV export, and a printable report carrying your showroom’s name in Arabic or English
• Your numbers are confined to your showroom in the database itself — no other dealer sees them, and you do not see theirs
• And the counter never brings a page down: a fault in it is a non-event for your visitor and never interrupts their browsing