Unique visitor 
Session Time is the most mysterious of parameters. You wrote in its tooltip:
"
Session Lifetime. Default: 10 minutes. Don't set too high."
In the future configuration page, would you explain in more details this critical parameter?
Let us consider that the webmaster thinks in term of "
unique visitor."
The webmaster wants to define a unique visitor on a
session time --let us say-- of
one day.
If the visitor refreshes the home page by F5 in IE, the counter would
not be incremented.
The counter will be incremented if the same visitor (with the
same IP or not)
visits the home page the next day or beyond.
Does the webmaster need to indicate as session time:
1440 (minutes
= 24 hours)?
Is it compatible with your advice "
Don't set too high"?
Because in your fifth image, you indicated:
Session Time:
1.
What is the relationship of this parameter with the size of the MySQL database
on an archive of 70 days?
What is the criterion for the automatic deletion of old records?
Advanced Parameters and performance 
You could discuss about the impact in "
Advanced Parameters" of:
Caching:
Yes
# Days Archive:
70
"
Number of days (for?) which you want to store the statistics. Default: 70 days. Don't set too high."
When you advise: "
Don't set too high", the
help on the configuration could explain
why.
At first glance, to manage the statistics of the current month and the previous month,
31 * 2 = 62 days would be sufficient? Why a window of 70 days?
For a beginner who discovers the module, if "
Yes" and "
70" are the values by default,
there is no need to present this fourth image before the fifth one,
because nobody will change these
difficult parameters without additional information.
At the limit, you could avoid showing these advanced parameters in an
introduction.
Indicating "
Support Caching" is sufficient.
Maximum of connections in a day 
In a future version, what about the new persistent counter:
Max daily connectionsthat the webmaster could reset?
IP log utility already integrated 
A chapter for
"Advanced" webmaster could present the
vvisitcounter MySQL database
from the phpmyadmin perspective.
Is there a way to identify a (ro)bot from a real user through the IP address?
Optionally could you provide an online tiny tool to convert a "
tm" value
that one could find in the column just before the "
ip" column?
The
idea is to reuse the
Vinaora Visitors Counter as an IP log utility!
