Device Detector vs Traffic Monitor

Device Detector is a full featured analytics reporting and management tool that detects all devices accessing your WordPress site. For each call made to your site, Device Detector analyzes the sent header, detects the device doing the call (and its characteristics) and can: modify the is_mobile() WordPress core function to be more precise and reliable; add some CSS classes to the body tag of your site (many classes to choose from); let you use the result of the detection in your own developments; record detected characteristics for reporting. Device Detector can report the following main items and characteristics: KPIs: number of hits, class breakdown, clients types and engines; Classes: Bot, Desktop, Mobile and Other; Devices types: Camera, Car Browser, Console, Feature Phone, Phablet, Portable Media Player, Smart Display, Smartphone, Tablet, TV; Client types: Application Library, Browser, Feed Reader, Media Player, Mobile Application, PIM. Technical characteristics and versions of all browsers; Device identification: brand, model, etc.; OS identification: name, version, etc.; Calling channel: site backend, site frontend, cron job, Ajax request, XML-RPC request, Rest API request, Atom/RDF/RSS feed; For a full list of items, characteristics and supported devices, please see the ‘devices’ tab in the plugin settings. Device Detector supports multisite report delegation and per site configuration (see FAQ). Device Detector supports an extensive set of WP-CLI commands to: get a device detail: see wp help device describe for details; display Device Detector status: see wp help device status for details; toggle on/off main settings: see wp help device settings for details; describe engine capacities: see wp help device engine for details; display devices statistics: see wp help device analytics for details. For a full help on WP-CLI commands in Device Detector, please read this guide. Device Detector is part of PerfOps One, a suite of free and open source WordPress plugins dedicated to observability and operations performance. Based on the amazing Matomo UDD, Device Detector is a free and open source plugin for WordPress. It integrates many other free and open source works (as-is or modified). Please, see ‘about’ tab in the plugin settings to see the details. Developers If you’re a plugins / themes developer and want to take advantage of the detection features of Device Detector, visit the GitHub repository of the plugin to learn how to use it. Support This plugin is free and provided without warranty of any kind. Use it at your own risk, I’m not responsible for any improper use of this plugin, nor for any damage it might cause to your site. Always backup all your data before installing a new plugin. Anyway, I’ll be glad to help you if you encounter issues when using this plugin. Please read carefully the FAQ at the bottom of this page before requesting support. Privacy This plugin, as any piece of software, is neither compliant nor non-compliant with privacy laws and regulations. It is your responsibility to use it – by activating the corresponding options or services – with respect for the personal data of your users and applicable laws. This plugin doesn’t set any cookie in the user’s browser. This plugin may handle personally identifiable information (PII). If the GDPR or CCPA or similar regulation applies to your case, you must adapt your processes (consent management, security measure, treatment register, etc.). Donation If you like this plugin or find it useful and want to thank me for the work done, please consider making a donation to La Quadrature Du Net or the Electronic Frontier Foundation which are advocacy groups defending the rights and freedoms of citizens on the Internet. By supporting them, you help the daily actions they perform to defend our fundamental freedoms!

Traffic Monitor gives you full visibility into how people and bots are hitting your site. Unlike bloated analytics and security plugins, Traffic Monitor focuses on logging raw request data that you control. You’ll know which pages are cached, which bots are visiting, where users are coming from, and how many requests are tied to each IP/browser combination. Perfect for developers, marketers, and site owners who want fast insights—without handing over their traffic data. What Makes It Different ✅ Logs requests for both cached and non-cached pages ✅ Lets you export raw traffic logs as raw CSV for your own analysis ✅ Identifies repeat ad clicks for spotting potential click fraud ✅ Reveals which bots are hitting your site, so you can block them elsewhere (example: Cloudflare) ✅ Tracks IP address, fingerprint, device type, cache status, response code, and more ✅ Displays referrer URLs and query strings ✅ Records the original source of requests by the same visitor as they surf your website ✅ Doesn’t auto-block or inject junk—just clean, useful data ✅ Works great with Cloudflare, caching plugins, and reverse proxies Key Features Logs every page request, including IP address, referrer, user-agent, browser, device, method, and more. Detects cached traffic even if served by Cloudflare, your web host, or a plugin. Identifies bot traffic by bot name and category. View click IDs like gclid and fbclid from ad platforms like Google and Meta. Records repeat ad clicks to detect potential click fraud. Bulk delete or export logs with one click. Search, sort, and drill into data from your dashboard. Built-in help tabs with definitions, setup help, and troubleshooting. Use Cases Debug integrations instantly: Know exactly what URLs are being hit, by which devices, and with what parameters. No guesswork. Spot caching gaps: See which pages are served from cache and which aren’t, even with Cloudflare or plugin-level caching. Understand real-world traffic: Track entry pages, referrers, devices, and browsers—whether human or bot. Catch click fraud signals: Identify repeat ad clicks tied to the same IP/user agent fingerprint or session, even if served from cache. Audit referrers: View exactly which websites or campaigns are driving traffic (including query strings). Filter out noise: Use bot labels and device types to focus only on human traffic when analyzing patterns.