Kinsta’s hosting plans are based on the total number of monthly visits to your site on the server. The number of visits in a given month is the sum of the unique IP address seen within a 24-hour period as recorded in the Nginx logs. We recently moved from a bandwidth-based pricing model over to a visitor-based pricing model due to the fact that this is easier to understand, calculate, and decide which hosting plan might be right for you.
What is a Visit?
Kinsta records the exact number of visits to your WordPress site that occur directly on the web server. You can see a summary of the visitors in the MyKinsta analytics “Resource Usage” report and can currently filter it by the previous 24 hours, 7 days, or 30 days.
The chart is fully dynamic and includes additional drill-down details. For example, if you highlight a specific point in time on the graph it will show you some comparison statistics, such as the total number of visitors being higher than the previous day, etc.
What Triggers and Doesn’t Trigger a Visit
Here are few examples of what exactly triggers and doesn’t trigger a visit at Kinsta:
- When a human arrives to your site and loads the page, this is a visit.
- When a human arrives to your site, and then browses to a new page, this is a still considered one visit.
- When a human arrives to your site from two different browsers, this is treated as one visit due to the fact that it is the same IP address.
- When a human arrives to your site at home and then later from work they will have used two different IP addresses to access the site and will be counted as two different visitors. This also means that every visit in a day from a given location will be only counted once no matter how many devices were used to load your site from that location as long as the visitor in question uses the same internet connection.
Kinsta Visitor Counts and Other Analytics Tools
It’s important to understand that Google Analytics or another third-party analytics tools might show something different from what we have calculated. This is due to the fact that many tools are attempting to show you the total number of real human visitors, after having filtered out bots and crawlers. All tools also show a different number based on their own set of rules — who they consider to be irrelevant/bot traffic and those that they don’t.
Bots and Discrepancy in Analytics
When a bot visits your site, it may or may not be counted as a visit.
We do not count visits from well-known “bot” user-agents and do our best to filter them. However, bots have also been known to spoof user agents, in which case they might appear legitimate in our access logs, but don’t show up in Google Analytics. Because of this, it could very well be that there is a discrepancy between the total visits we show and another tool.
If you are struggling with a discrepancy or bot traffic, we recommend implementing a reputable security solution such as Cloudflare or Sucuri. These services have extensive databases of what should be treated as “bad” traffic, in which case they can prevent it from ever hitting your Kinsta site. Many of our clients see much less of a discrepancy between our analytics and what Google Analytics might be reporting after utilizing one of these services. This can, in turn, can save you money by limiting the plan needed for your site.
Additional block rules can also be added by our Kinsta support team. For example, if you need to deny a specific User-Agent or IP address. Due to how our infrastructure works, this should be done at the server-level. Please open up a ticket if you need assistance.