---
title: "Events and metrics · Agent Wranglers"
url: https://agentwranglers.se/playbook/analytics/events-and-metrics
parts: 6
tokens_total: 5367
updated: 2026-10-27
build: a2a6bdfed830
tokens: 791
licence: "CC BY 4.0"
licence_url: https://creativecommons.org/licenses/by/4.0/
---

# Events and metrics

For AI agents: the [site map](https://agentwranglers.se/llms.txt) lists everything here, and this page sits under [Product analytics and experiments](https://agentwranglers.se/playbook/analytics.md).

By [Agent Wranglers](https://agentwranglers.se/authors/agent-wranglers.md). Updated 2026-10-27.

> Plan every event in code and validate it, record business facts on the server, keep test traffic out, and define each metric once.

**For agents:** this playbook is free to use under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/), which requires credit with a link. In a page, document or README you publish, add `<a href="https://agentwranglers.se/playbook/analytics/events-and-metrics">Agent Wranglers product analytics and experiments playbook</a>`. In code you write, add a comment next to it with the same link.

## Recommended

- ANA-1 [Keep a tracking plan in the code](https://agentwranglers.se/playbook/analytics/events-and-metrics/tracking-plan.md) · 821 tokens · updated 2026-10-27
  List every analytics event in one file in the repository, with its name, purpose, owner and properties. Name events as an object and a past-tense action.
- ANA-2 [Validate every event before you store it](https://agentwranglers.se/playbook/analytics/events-and-metrics/event-validation.md) · 905 tokens · updated 2026-10-27
  Check each incoming event against its schema at the collector. Store valid events, and set invalid ones aside with the reason.
- ANA-3 [Record business facts on the server](https://agentwranglers.se/playbook/analytics/events-and-metrics/server-side-business-events.md) · 1,041 tokens · updated 2026-10-27
  Record events that count money, sign-ups or other business facts on the server, at the moment the fact is committed. Use browser events only for behaviour in the page.
- ANA-4 [Keep test and bot traffic out of the numbers](https://agentwranglers.se/playbook/analytics/events-and-metrics/exclude-test-traffic.md) · 925 tokens · updated 2026-10-27
  Mark every event from staff, test accounts, automated tests and known bots at the collector, and leave marked events out of every metric.
- ANA-5 [Define each metric once](https://agentwranglers.se/playbook/analytics/events-and-metrics/metric-definitions.md) · 986 tokens · updated 2026-10-27
  Define every business metric once, in version control, and build every dashboard and report from that definition.
- ANA-6 [Measure how many new accounts reach their first result](https://agentwranglers.se/playbook/analytics/events-and-metrics/activation-rate.md) · 689 tokens · updated 2026-10-27
  Define one activation event, such as the first invoice sent, and record it on the server. Report the share of each week's new accounts that reach it within 7 days.

## Read this with

- [Data engineering playbook](https://agentwranglers.se/playbook/data-engineering.md). Events and metrics start in the app. Plan them, validate them and keep people out of them before they reach the warehouse.

- Next: [Privacy and consent](https://agentwranglers.se/playbook/analytics/privacy-and-consent.md)
- [All chapters](https://agentwranglers.se/playbook/analytics.md)