Geo Analytics is included in WPLocation Pro 1.4.0 and is off by default. Keep WPLocation Free 1.1.0 or newer active with a current licensed local country database. No hosted analytics account, second ZIP or extra Pro license is needed.
Enable collection
- Back up and test on staging. In WPLocation → Diagnostics, confirm Free returns the expected country for a known address.
- Open WPLocation → Geo Analytics. Select “Record anonymous frontend requests” and choose 7, 30 or 90 days of retention. Save. This creates a private aggregate database table and schedules daily cleanup.
- Visit a targeted post or page, a Geo Redirect source, or a page with an active Forms & Campaigns shortcode as an anonymous visitor. Check the dashboard after the request reaches WordPress.
What the dashboard counts
For a targeted post or page, an anonymous GET request is counted once as allowed or blocked by Free’s saved country rules. A sent Geo Redirect is another event. An active campaign form or offer display is counted separately; a fallback also increments the fallback total. The country is the two-letter result of Free’s local lookup, or “Unknown” when lookup does not return a valid country.
Results are grouped by UTC day, country and event. The dashboard shows six event totals, a daily chart with an exact-value table, and a country breakdown. Because some events can happen on the same request, summing the cards does not give a unique request or visitor count.
Privacy and data controls
Geo Analytics stores only day, country code, event type and aggregate count. It does not store visitor IP addresses, cookies, user IDs, page URLs, form entries or order IDs in its table. Logged-in visits, WordPress admin, REST requests, feeds, HEAD and POST requests are excluded. It does not add a browser tracking script or send analytics to WPLocation. Web-server logs, Formidable and other plugins have their own data practices.
Change retention on the same screen. Rows older than the selected period are removed by WordPress cron and when an administrator opens the reporting area. Disabling collection stops new counts; existing rows remain until retention removes them or an administrator uses the confirmed “Delete all analytics data” control. “Export aggregate CSV” downloads the stored day/country/event/count rows for site administrators. Deactivating Pro stops collection and cleanup until Pro is active again; saved rows are retained.
Understand the limits
- A CDN, reverse proxy or full-page cache can serve a response before WordPress runs, so the dashboard can undercount. Bots and repeated requests that do reach PHP may be included. These figures are not unique visitors.
- Geo Analytics does not measure purchases, revenue, form submissions, conversion rates or an individual visitor journey. A campaign form display is not a completed entry.
- Country detection is an estimate based on the local source. “Unknown” can indicate database coverage, an invalid IP or an unavailable source. Check Diagnostics before changing rules.
- WordPress cron depends on traffic or a server cron. Administrators opening the analytics screen also trigger retention cleanup; check the schedule if your site has little traffic.
- Large uncached traffic adds one atomic database update per recorded event. Test database load and cache behavior on your own hosting before enabling on a high-traffic site.
Contact WPLocation with your software versions and the result you expected. Keep keys and customer data private.