Limy Agent Analytics

Limy Agent Analytics captures HTTP request metadata from your WordPress site and sends it to Limy’s analytics platform for bot detection and traffic analysis.

What it does:

• Logs request method, path, status code, user agent, and timing
• Queues logs locally and sends them in compressed batches via cron
• Provides an admin dashboard to configure and monitor the plugin
• Redacts sensitive query parameters automatically

Key features:

• Gzip-compressed API delivery — saves 60-80% bandwidth
• Size-aware batch chunking — no oversized payloads
• Jittered retry backoff — prevents thundering-herd failures
• O(1) event capture — zero overhead on every page load
• Lazy service loading — admin code never loads on the frontend

External Service

This plugin sends request log data to the Limy analytics API at https://stream.getlimy.ai. An API key is required.

• Limy Terms of Service
• Limy Privacy Policy

When tracking is active, the plugin records every front-end request that reaches WordPress and sends the records to the API about once a minute. The “Test Connection” button also sends one test event.

Optional data sources, enabled only by an administrator in Settings > Limy Agent Analytics > Data Sources:

• WP Engine access log: on WP Engine, the plugin reads the origin access log that WP Engine provides to the site (the same log linked from wp-admin under WP Engine > Information), which also records pages served from WP Engine’s cache. It is fetched from the site’s own *.wpenginepowered.com address; the log address is not stored or sent anywhere.

• Web server access log: the plugin reads the access log that your host already writes and sends its entries (including pages served from cache) instead of capturing requests itself. Lines for other hosts, static assets and excluded routes are skipped. To check that a log belongs to this site, the plugin requests your home page once with a limy_log_probe parameter.

Data sent per request: HTTP method, host, request path, query parameters (up to 20, with sensitive names such as password, token, key, email or code redacted), response status code, client IP address (and the address of the connecting proxy, if any), user agent, referer URL, request duration, and content length. Referer URLs and query values can contain personal data; exclude routes or add parameter names to the redaction list in the plugin settings if needed.