Website analytics by verified domain

This page turns your verified domains into an entry point for the analytics dashboards. Pick a domain to see every analytics channel that serves it (combo channels excluded). A domain can be attached to more than one parent channel, so the channel list is paginated; open any channel to read its page views, visitors, sessions, traffic sources, devices and visit log. Source code: https://github.com/teakong/danmu.

How the list is built

Domains come from the ownership verification on the domain page. Channels are the push sub channels (combo channels excluded) bound to those domains through their webhook URL. Only channels you own are listed, and only after you sign in, because every dashboard request is authenticated with your own account.

One line of code to integrate

Any push channel except combo channels (pushType=10) can serve as an analytics channel. Paste one script tag before </body>: danmu.js with plugins=stat only reports visits and renders no danmu, and danMu=0 plus hideDialog=1 leaves the page visually untouched. The danmu & analytics demo gives you a ready-to-copy snippet with a channel code, and a channel's copy-code dialog ships the same line.

What a page reports

• Visits: every page load fires one head=visit push with the current page URL, which is how the dashboard computes PV / UV and top pages per path.
• Clicks: clicking any element fires one head=click push. Its body is a compact click description - ancestor path, element id / class, a short text snippet, link target and click position (up to 1000 characters) - not the whole HTML, so click hotspots stay readable.
• Visitors & devices: the dashboard aggregates page views, unique visitors, sessions (deduplicated over 30 minutes), new visitors, unique IPs, distinct pages viewed and visitors online now, plus device type, browser, OS and screen resolution.

What the dashboard shows

Pick today, the last 7 / 15 days or a custom range to read traffic trends, title breakdowns, top pages and device mix. The visit log filters by head, URL, title, IP, visitor and device, and exports to Excel. Each visit can also be pushed to your phone as a notification.

Where it works

• Offline HTML: a file:// page opened by double-click reports just as well - handy for PDF / Markdown documents turned into shareable webpages, so you can see who opened them and how often.
• Any website: drop the same line into the page template. No build step, no backend, and cross-origin reporting is already allowed through CORS preflight.
• WorkBuddy app pages / Qoder sites: leave channelCode empty and the widget claims a channel from the current URL, sending the page title along with it; for multi-page sites, put the same channel code on every page to merge the whole site into one channel while the dashboard still splits PV / UV by URL.

Privacy and caveats

• The plugin writes no cookies or localStorage, makes no DOM changes and fails silently - the host page is unaffected. Clicks are captured in the capture phase, so stopPropagation() in your own code cannot hide them, and the widget's own UI clicks are skipped.
• Optional settings: statHead changes the visit head (default visit); statClick=0 reports visits only, with no click tracking.
• Give each app or site its own channel code so datasets stay separate. The trigger endpoint is unauthenticated and carries no credentials, which makes the channel code a push credential - never commit it to a public repository or paste it into a public page.