Debug a tracker install
After installing the snippet on a new site, the Event Explorer is where you confirm events are arriving with the expected shape.
Event Explorer
The investigation surface for website analytics
The dashboard shows curated rollups. The Event Explorer shows the underlying events — filterable by date, type, country, pathname, referrer, session, or visitor — and lets you drill into the safe metadata view per event.
Use cases
What the Event Explorer is for
Ad-hoc investigation, debugging, reporting. The same surface that powers tracker installs and incident response also powers the AI-assisted MCP read path.
Investigate a traffic spike
A spike on /blog/foo last Tuesday? Filter to that day and pathname, browse the source distribution, drill into a single event for the safe metadata view.
Find every visit from a specific referrer
Filter by referrer source to see which pages received Claude (or ChatGPT, Perplexity, Gemini) referrals over a date range.
Reconcile against an external source
Export the filtered slice to CSV or NDJSON for cross-checking against a client warehouse, a campaign report, or a Search Console export.
Confirm an AI crawler reached a page
Filter by AI crawler traffic type and pathname. The crawl timestamp is the answer.
Build a one-off client report
Filter, export, summarise. The data is reproducible — the filter set is the report definition.
How WebmasterID helps
Filter, browse, drill in, export
The Event Explorer is built around four primitives. Each one is independent, and they compose.
- 1. Filter. Date range, traffic type, country, pathname, referrer source, session, visitor, campaign. Filters compose with AND semantics.
- 2. Browse. The filtered event stream is paginated and sortable. Defaults keep latest events at the top.
- 3. Drill in. Open any single event for the safe metadata view: pathname, referrer, traffic type, country, campaign — no raw IPs, no fingerprinting signals.
- 4. Export. CSV or NDJSON of the filtered set. Workspace-scoped; the audit log records the export.
Feature
What you can do with the Event Explorer
The Event Explorer is operator-grade — built to answer questions about real traffic, not to look impressive in a demo.
Cross-site filtering
Filter across every site in the active workspace, or narrow to a single site. The FilterBar is the only control surface you need to learn.
AI traffic isolation
Separate AI crawlers, search-engine crawlers, automation, and humans. Useful when humans and bots would otherwise contaminate the same view.
Source-confidence labels
Per-row confidence labels for attribution. Claude can explain the directional limits, not gloss over them.
Safe metadata drill-down
Per-event detail panel renders the privacy-safe metadata view. Operators see what was recorded; visitors stay anonymous.
Privacy & trust
The Event Explorer respects the same privacy posture as the rest of the platform
No surveillance, no hidden fields, no fingerprinting. The events that land in the Event Explorer are the same events the tracker recorded — and the tracker is small on purpose.
No raw IPs
IPv4 last octet zeroed at the edge; IPv6 truncated to /48. Raw IPs never land in the events table.
No fingerprinting
Canvas, audio, fonts, and device-entropy are not collected. The Event Explorer cannot render what was never recorded.
Workspace-scoped
Operators only see events for sites in workspaces they are a member of. Cross-workspace reads are impossible.
Audit-logged exports
Every export is recorded in the workspace audit log so downstream compliance conversations have a real answer.
Privacy questions? info@helperg.com. See also /privacy-first-analytics.
FAQ
Event Explorer, answered
- What is the Event Explorer?
- It is the investigation surface inside the WebmasterID dashboard. While the main dashboard shows curated rollups, the Event Explorer lets you browse the raw event stream, filter it, and drill into any single event for the safe metadata view. It is built for ad-hoc questions and incident-style investigations.
- What can I filter on?
- Date range, traffic type (human / AI crawler / search-engine crawler / automation), country, pathname, referrer source, session, visitor, and campaign. Filters compose; the resulting set is what you can browse, export, or hand to Claude through MCP.
- Is raw user data visible?
- No. The Event Explorer renders a privacy-safe metadata view per event. Raw IPs are never stored (IPv4 last octet zeroed at the edge; IPv6 truncated to /48). No fingerprinting signals are collected. No session replay.
- Can I export the filtered events?
- Yes. CSV and NDJSON exports of the filtered set are supported. Exports are workspace-scoped; cross-workspace exports are impossible. The audit log records each export.
- Does the Event Explorer work with the Claude / MCP integration?
- Yes. The same filter primitives are exposed through MCP, so Claude can browse the event stream on your behalf in the same shape you do. Operator approval is required for every action — the MCP surface is read-only.
- Is the Event Explorer available on Free?
- The basic Event Explorer ships on Pro. Agency unlocks the multi-workspace, multi-site shape with deeper filters and exports without per-export gating. See /pricing for the current matrix.
Read next
Related cluster pages
The Event Explorer is one surface in a larger observability stack.
Website observability
The end-to-end observability story — Event Explorer is the investigation surface.
Read more →
Bot intelligence
The categorisation that powers the Event Explorer's traffic-type filter.
Read more →
Attribution analytics
The attribution layer surfaced in the Event Explorer's source filter.
Read more →
AI-assisted analytics
The same Event Explorer surface, read by Claude through MCP.
Read more →
Multi-site analytics
The Event Explorer rolls up across every site in the active workspace.
Read more →
Pricing
Event Explorer access by plan.
Read more →