# Product analytics, next to the trace

Page views arrive on their own. Track the rest from the browser, your backend or a span you already emit, and see where people stop on the same dashboards as your latency.

## From one event to a conversion rate

### $pageview: Page views without code

The browser SDK records a page view on every navigation. Your first funnel works before you write a single track call.

### maple.product_event.name: Events from spans

Tag a span you already emit and it becomes an event, with the span's attributes as properties. Works with any OpenTelemetry SDK, and the event links back to its trace.

### identify(): Anonymous to signed in

Pass your user id to identify() and earlier anonymous visits join it, across your subdomains. A server event with the same user id lands on the same person.

### drop-off · paths: Funnels, drop-off and paths

Up to 10 steps, a conversion window, and a breakdown by referrer, UTM, country or any property. Paths show what people did before or after any event.

### source: product_events: Charts and alerts

Product events are a query source like traces, logs and metrics. Chart signups next to error rate, or alert when they drop.

### query_funnel(): Ask your agent

The MCP server lists your events and runs funnels, so an agent can tell you where signups stall without leaving the editor.

## Related

- [Browser Sessions](https://maple.dev/features/browser-sessions.md)
- [Metrics & Dashboards](https://maple.dev/features/metrics-dashboards.md)
- [Distributed Tracing](https://maple.dev/features/distributed-tracing.md)
- [E-Commerce Observability](https://maple.dev/use-cases/ecommerce-observability.md)