# Avo > Avo is the data governance platform that keeps every analytics event defined consistently, implemented reliably, and trusted across every team. Built for both humans and AI agents, Avo lets product, data, and engineering teams design a single source of truth tracking plan (events, properties, metrics, journeys), audit it for quality and naming consistency, generate type-safe tracking code, monitor live data quality, and publish definitions to tools like Amplitude, Mixpanel, and Segment. Through the Avo MCP, agents like Claude, Codex, and Cursor can search the tracking plan, design tracking from a PRD or Figma onto a branch using your existing patterns and rules, generate the code snippets and instructions so developers and their agents implement correctly without opening their tracking plan in another tool, and query product data accurately because Avo knows your metric definitions. ## Documentation Learn what Avo is, how the tracking plan works, and how humans and AI agents use it together to design, implement, and govern analytics. Every page below is also available as clean Markdown — append `.md` to any URL. For the entire documentation in one file, see https://www.avo.app/docs/llms-full.txt. ### Getting started - [Getting started](https://www.avo.app/docs/index.md): What Avo is and how to start using it. - [What is a tracking plan?](https://www.avo.app/docs/data-design.md): The core concept behind Avo, a single source of truth for analytics. - [Quickstart: tracking plan in Avo](https://www.avo.app/docs/data-design/quick-start.md): Set up your first tracking plan. - [Deep dive: data design in Avo](https://www.avo.app/docs/data-design/start-data-design.md): The substantive guide to designing analytics data well in Avo. ### Adopting Avo with AI agents - [Overview](https://www.avo.app/docs/adopting-avo-with-ai-agents.md): Why and how to adopt Avo when AI agents are designing and implementing your analytics. - [Setting up a tracking plan](https://www.avo.app/docs/adopting-avo-with-ai-agents/setting-up-a-tracking-plan.md): Get a tracking plan into Avo, even starting from scratch or from another tool. - [Governing AI-generated analytics](https://www.avo.app/docs/adopting-avo-with-ai-agents/governing-ai-generated-analytics.md): How Avo stops AI agents from creating inconsistent, duplicate, or drifting analytics and keeps implementation in sync with the plan. ### Avo MCP (for AI assistants and agents) - [Avo MCP overview](https://www.avo.app/docs/reference/avo-mcp/overview.md): Connect Claude, Cursor, Codex, and other MCP clients to your Avo tracking plan to read the plan, design tracking for new features, and write changes on a branch. Remote server at https://mcp.avo.app/mcp. - [Avo MCP tools reference](https://www.avo.app/docs/reference/avo-mcp/tools.md): Full parameters and return shapes for the MCP tools (list_workspaces, search, get, save_items, workflow). - [Agentic data design](https://www.avo.app/docs/data-design/guides/agentic-data-design.md): How to design analytics tracking with AI agents while keeping events consistent and governed. ### The tracking plan - [The Avo tracking plan: overview](https://www.avo.app/docs/data-design/avo-tracking-plan.md): How events, properties, metrics, sources, and journeys fit together. - [Journeys](https://www.avo.app/docs/data-design/avo-tracking-plan/journeys.md): Organize events into the user journeys they belong to. - [Events](https://www.avo.app/docs/data-design/avo-tracking-plan/events.md): Define and document analytics events. - [Properties](https://www.avo.app/docs/data-design/avo-tracking-plan/properties.md): Define and reuse event properties. - [Metrics](https://www.avo.app/docs/data-design/avo-tracking-plan/metrics.md): Define metrics composed from events. - [Branches](https://www.avo.app/docs/data-design/branches.md): Try out and review tracking-plan changes on a branch before merging them into your source of truth. ### Workflow - [Avo workflow overview](https://www.avo.app/docs/workflow/overview.md): Plan, review, implement, validate, and publish analytics changes on branches. ### Quality and governance - [Tracking plan audit](https://www.avo.app/docs/audit/overview.md): Automated quality and naming-consistency checks for your tracking plan. - [Audit rules](https://www.avo.app/docs/audit/rules.md): The full set of rules the audit checks for, and how to read, fix, and configure them. - [Naming conventions](https://www.avo.app/docs/data-design/best-practices/naming-conventions.md): Best practices for consistent event and property names. - [Defining descriptive events and properties](https://www.avo.app/docs/data-design/best-practices/defining-descriptive-events-and-properties.md): How to write clear, reusable definitions. - [Defining event hierarchy](https://www.avo.app/docs/data-design/guides/organizing-event-hierarchy.md): Structure events consistently to avoid duplication and sprawl. - [Organizing tracking plans](https://www.avo.app/docs/data-design/guides/organizing-metrics-and-events.md): Keep events and metrics organized as the plan grows. - [Documenting purpose meetings](https://www.avo.app/docs/data-design/guides/documenting-purpose-meetings-in-avo.md): Align stakeholders on what to measure and why before building, Avo's method for designing analytics with intent. - [Stakeholders](https://www.avo.app/docs/data-design/avo-tracking-plan/stakeholder-domains.md): Assign ownership of tracking-plan areas to stakeholder teams for governance. ### Observability - [Inspector quickstart](https://www.avo.app/docs/inspector/start-using-inspector.md): Monitor live tracking data quality and find and fix issues in production. ### Type-safe implementation - [Avo Codegen overview](https://www.avo.app/docs/implementation/avo-codegen-overview.md): Generate type-safe analytics tracking code from your tracking plan. - [Quickstart: Avo CLI](https://www.avo.app/docs/implementation/cli.md): Pull generated code and run validation in CI. - [Avo Codegen languages](https://www.avo.app/docs/reference/avo-codegen/programming-languages.md): Supported languages for generated code. ### Publishing, import and export - [Publishing overview](https://www.avo.app/docs/publishing/publishing/overview.md): Push tracking-plan definitions to analytics, CDP, and governance destinations — Amplitude, Mixpanel, Segment, RudderStack, mParticle, Adobe Experience Platform, and Snowplow — or export via webhooks and S3 for custom build pipelines and warehouses such as Snowflake, Databricks, and BigQuery. - [Importing overview](https://www.avo.app/docs/publishing/import/get-tracking-plan-into-avo.md): Get an existing tracking plan into Avo — import from Amplitude, Mixpanel, or Google Sheets, or from Inspector. - [Avo public API](https://www.avo.app/docs/reference/public-api/overview.md): Programmatic access to branches and the tracking plan. ### Reference - [Avo Intelligence](https://www.avo.app/docs/reference/avo-intelligence.md): AI-powered features like Smart Search that make working with your tracking plan faster.