LiveMaply

A visitor has been stuck on your booking page for five minutes, and your analytics will tell you about it tomorrow. Most website analytics show visits after they happened, so that visitor leaves before anyone can help. LiveMaply puts the people on a site at this moment on a world map, each with the page they are viewing and where they came from. The location is an estimate from the IP address, at city level. From the map, an operator can pick a visitor and open a chat, which appears in a widget on the site.

A JavaScript tracker in the site's template collects these visits. The same script feeds a statistics page with traffic sources and the busiest hours of the week, with known bots left out. Operators can give a returning visitor a private alias and keep saved replies ready for the chat. The tracker sets a visitor cookie and keeps analytics IP addresses in hashed form, the privacy policy says. Site owners have to cover it in their own consent settings.

Bots and scanners rarely run that script, so Abuse Control uses a separate PHP collector on the server. It also works with WordPress and sees only the requests that pass through it. It sorts traffic into people, search and AI crawlers, unknown bots and signature matches like probes for configuration files.

Suspicious activity is then grouped into campaigns with the paths and response codes behind them. With a Cloudflare account connected, a campaign can get a temporary challenge or block, and AutoProtect can do this by itself above a score you set. Without that connection, actions are only recorded for manual follow-up.