DevDome Analytics – Real Traffic Without Bot Noise
| 开发者 | devdome |
|---|---|
| 更新时间 | 2026年8月12日 06:30 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Visitors, pageviews, sessions, live visitors, top pages, referrers, countries, devices.
- Bots and AI crawlers (Googlebot, GPTBot, ClaudeBot and others) reported separately from humans.
- Visits referred by AI assistants such as ChatGPT and Perplexity.
- Outbound-link click tracking that keeps counting when ad blockers stop the analytics script.
- Reports from the last 24 hours up to 12 months.
- Cookieless on new installs: nothing is stored on your visitors' devices, so no cookie banner is needed for DevDome.
- Returning-visitor tracking is optional and off on new installs.
- Administrators and editors are not tracked by default, and you can exclude any role.
- The browser Do Not Track signal is respected by default.
- No form values, post content, user accounts, customer or order data are collected.
- Every tracking feature has its own switch, plus one master switch.
安装:
- Install and activate the plugin from Plugins > Add New.
- Open DevDome > Analytics.
- Select Connect Via DevDome Account, or enter your DevDome Account ID manually.
- Review the Settings tab and enable only the tracking features you want.
常见问题:
Do I need a DevDome account?
Yes. DevDome Analytics is a connector for the hosted DevDome Analytics service, where analytics events are processed and full reports are displayed. A free plan is available. No visitor data is collected until you connect the site.
Does it remove all bot traffic from visitor reports?
It detects known bots and AI crawlers and reports them separately from human visitors. Unknown, new, or deliberately disguised bots may not always be identifiable.
Is anything sent before I connect?
No visitor data, ever. Before the site is connected, the tracking script is not added and no analytics events are sent. The one exception is a connection-status check (this site's domain and its secret token, nothing else) when you open the plugin's own screen, so a site you already connected on devdome.com shows as connected here without a second connect step.
Does it set cookies?
General traffic tracking is cookieless on new installs. Returning-visitor tracking is optional and disabled by default. Outbound-link tracking stores random IDs in localStorage and sessionStorage after a visitor clicks an external link. Disable Track Outbound Links if you do not want that storage. See the Privacy section for full details.
Can I exclude myself and my team?
Yes. Logged-in administrators are excluded by default. You can exclude any additional WordPress role.
Will it slow down my site?
The tracking script loads asynchronously and does not block page rendering. The plugin does not write analytics events to your WordPress database.
Does it work with caching plugins?
Yes. The tracking snippet is the same for every visitor, so it works with full-page caching. Connecting or disconnecting also clears common page caches so the change is applied.
Which crawlers can it report?
The current detection list includes GPTBot, ChatGPT-User, ClaudeBot, PerplexityBot, Google-Extended, Bytespider, CCBot, Googlebot, bingbot, Slurp, DuckDuckBot, Baiduspider, YandexBot, AhrefsBot, SemrushBot, MJ12bot, DotBot, and Screaming Frog. The plugin reports detected crawlers; it does not block them.
What happens when I disconnect?
Tracking stops immediately. You can also delete the site's hosted analytics data when disconnecting or by selecting Reset Analytics. Data that remains inactive is deleted automatically after 90 days.
Does it support WordPress multisite?
Yes. Each site connects separately and has its own settings, Site ID, and reports.
Where do I see the reports?
The WordPress Overview tab shows key metrics. Full traffic, referral, click, location, device, and crawler reports are available in your DevDome account.
更新日志:
- First-Party Delivery is honest about why it is unavailable: while the site is not connected the switch is disabled with a Connect button above it, and on the Free plan it shows "Included in the Pro plan and above" instead of switching itself back off. Plan changes now reach the screen within minutes.
- The manual Account ID connect option was removed. Connecting is always the one-click, signed-in flow.
- Disconnecting from the plugin now also unlinks the site on DevDome servers and clears every cached account detail, so every DevDome plugin on the site agrees immediately.
- The DevDome Dashboard (suite hub) was redesigned: cleaner cards, your account email and plan on the overview, and update buttons shown only when an update really exists.
- One button system across the suite: the same Connect button and the same Save Settings button in every DevDome plugin.
- New bug-report button in the page header.
- New: First-Party Delivery, an optional ad-block-resistant mode (off by default, included in the DevDome Pro plan and above). The tracking script is served from your own domain and events relay through your own site server-side with randomized per-site names, so ordinary blockers of third-party analytics domains cannot drop them. Bypasses most, not all, blockers. Every relayed field is validated and sanitized, identity always comes from the plugin's own settings, and the relay accepts only same-site browser requests.
- Connecting works again for fresh installs: the plugin serves a one-way fingerprint of its site token at
/.well-known/devdome-connect-proof.txt, which the DevDome service verifies against your site before accepting the connection. No token, secret, or visitor data is exposed by it. - One connection, both sides: a site connected through the devdome.com dashboard now shows as connected in wp-admin by itself, and if the site is removed or its token rotated on the dashboard, the plugin flips to disconnected with a clear notice instead of staying green while calls fail. A local Disconnect always sticks.
- Fixed: the Overview tiles never loaded on sites using plain permalinks (the WordPress default). They now show the same numbers as the DevDome dashboard everywhere, and an unavailable answer leaves the placeholders instead of showing zeros.
- First-Party Delivery hardening: forwarded visitor IP and country headers are trusted only when the connection they arrived on vouches for them; events relay correctly on subdirectory and subdirectory-multisite installs; relayed forwards no longer block the visitor's request; in-app (social webview) visits keep their traffic source; the served script copy is refreshed only when its content really changed; and the
/dd-eclick endpoint requires the browser's own same-site Origin header too. - The tracking script used for First-Party Delivery ships inside the plugin package and is copied, never downloaded, into your uploads folder.
- Turning First-Party Delivery on requires a real answer from the plan check; an unreachable service or a rejected credential no longer enables it, and a rejected credential switches it off with a notice instead of silently losing events.
- Toggling First-Party Delivery clears common page caches so cached pages stop beaconing to a stale endpoint.
- The daily refresh event is removed on plugin deactivation, and uninstalling always cleans up the cron event and the generated script file.
- The plan check sends the site token in a request header instead of the URL.
- New optional First-Party Delivery mode (off by default, included in the DevDome Pro plan and above): the tracking script is served from your own domain and events are relayed through your site server-side, using randomized names unique to your site, so ordinary ad blockers that block third-party analytics domains cannot drop them. Bypasses most, not all, blockers. Every relayed field is validated and sanitized before forwarding, identity always comes from the plugin's own settings, and the forward authenticates with your site token. All other tracking is unchanged on every plan.
- Unified DevDome suite icons and updated the suite hub with one-click installs for WordPress.org plugins.
- No request is made to DevDome before you act: the one-click connect link is now requested only when you press "Connect Via DevDome Account", and the account check no longer runs until a connection has been started or completed. Off by default, opt-in by a button press.
- The connect screen now says exactly what connecting sends before you press the button.
- Every field of the relayed outbound-click event is individually validated and sanitized before it is forwarded, and the site and account identifiers in it now always come from the plugin's own settings, never from the request body.
- Request paths and IP addresses read from server variables are sanitized where they are read.
- First release on WordPress.org.
- The admin screen's styles and behaviour now load as enqueued files instead of inline blocks.
- The tracking snippet is enqueued too: the plugin no longer writes script tags into the page markup. Outbound-click counting is unchanged, including on sites where a blocker stops the tracker file from loading.
- Internal rename: every function, class, constant, option and transient the plugin owns now carries its own identifier prefix. Existing settings and your DevDome connection are carried across automatically.
- Fixed a fatal error that could break wp-admin on sites running several DevDome plugins when this one loaded first.