The geolocation session count doesn’t seem accurate
The geolocation service is powered by an IP-to-location API. When a user visits a page with a geolocation condition or DKI shortcode for the first time during their session, a request is sent to the geolocation database to compare the user’s IP with the location information stored in the database.
What is a geolocation session?
A geolocation session starts when a visitor first accesses a page with a geolocation trigger or a Geolocation DKI shortcode and lasts until the visitor closes their browser or has been inactive for 25 minutes (note that this time frame may vary slightly depending on the browser and server hosting the website).
Not every page view should count as a session!
- The geolocation session is initiated only when a visitor accesses a page with a geolocation trigger or a geolocation DKI shortcode, and a request to the IP-to-location API is made to compare the visitor’s IP with the location in the database.
- If the user browses several pages within the same visit, it will still be considered a single session. The session will end when the visitor closes the browser or after 25 minutes of inactivity, though this duration may vary slightly depending on the browser and server.
Blocking IPs from the geolocation service
If-So offers two options to help identify and block bots — we recommend using both.
- “Block Bots” mode – automatically blocks search engines and bots that declare themselves as bots.
- Manual blocking – logs all geolocation requests, provides a list of IPs that extensively tri
Click here to learn how to activate these options.