# Get Started With Avo There are a few ways to get started in Avo, all depending on your immediate needs: - [**Try the Avo workflow**](#try-the-avo-workflow-for-your-next-analytics-release): For teams that want a solid workflow for their next analytics release, create a branch in Avo and define new events and properties visually in context of the user journey - [**Find (and fix) your data quality issues**](#find-and-fix-your-data-quality-issues): For teams that are struggling with data quality, install Inspector and get a view of all your data quality issues in one place - [**Audit your tracking plan**](#audit-your-tracking-plan): For teams that want a single source of truth for their tracking plan and review their event and property definitions, import your existing tracking plan into Avo or manually create one You can do these steps in any order or in parallel, and skip those you don’t think apply to you. ## Try the Avo workflow for your next analytics release If you have an analytics release coming up in the next few days, we highly recommend you try out the Avo Workflow for that release. The Avo workflow is a visual way to design your data structures in context of the user journey and covers all the steps required to plan, review, request implementation, implement, validate and publish your analytics release. ![The Avo Workflow: Plan, review, implement, validate and publish your tracking changes](https://www.avo.app/docs/images/avo-workflow.png) Create a workspace in Avo and open your first branch to start defining the event structures for your next release. - [The Avo Workflow](https://www.avo.app/docs/workflow/overview.md): Plan, review, implement and validate every analytics release ## Find (and fix) your data quality issues The first step to better analytics governance is knowing what’s wrong with your data today. Avo Inspector gives you an overview of your current state of tracking and highlights issues and discrepancies in your live event tracking. Avo then provides you with the tools to systematically get to better data, one resolved issue at a time. ![Inspector issues overview](https://www.avo.app/docs/images/inspector/inspector-issues-overview.png) Install Inspector to get started. Set up Inspector via your CDP (Customer Data Platform) or GTM (Google Tag Manager) and start working on your data quality right away. If you don't have a CDP or GTM, install via a custom SDK. - [Get Started With Inspector](https://www.avo.app/docs/inspector/start-using-inspector.md): Install Inspector to get overview of your current state of tracking ## Audit your tracking plan Getting your tracking plan into Avo gives you an instant audit of your event structures. There are three ways to get your tracking plan into Avo: - [Import from Amplitude, Mixpanel or Google Sheets](https://www.avo.app/docs/publishing/import/importing.md) - [Import events from Inspector](https://www.avo.app/docs/inspector/add-events-from-inspector.md) - [Build your tracking plan from scratch](https://www.avo.app/docs/data-design/start-data-design.md) When your tracking plan, or a subset of it is in Avo, you will immediately receive an audit on your tracking plan. The audit surfaces issues like duplicate event and property names and inconsistencies in your naming convention. - [Get your tracking plan into Avo](https://www.avo.app/docs/publishing/import/get-tracking-plan-into-avo.md): All the ways to get your existing tracking plan into Avo - [Audit your tracking plan](https://www.avo.app/docs/audit/quickstart.md): How to get an audit for your tracking plan. --- ## Guides and best practices - [Avo 101 For Developers](https://www.avo.app/docs/implementation/devs-101.md): Codegen, Inspector and Debuggers—What’s the difference? - [Designing Data In Avo](https://www.avo.app/docs/data-design/start-data-design.md): How to define metrics, events and properties step by step - [Multi-Product Workspaces](https://www.avo.app/docs/data-design/guides/organizing-metrics-and-events.md): How to organize a tracking plan for multiple products ## Browse by product - [Tracking Plan Management](https://www.avo.app/docs/data-design/quick-start.md): Collaborate with your team on tracking plan changes - [Tracking Plan Audit](https://www.avo.app/docs/audit/overview.md): Verify that all tracking plan changes follow your tracking plan rules - [Avo Inspector](https://www.avo.app/docs/inspector/start-using-inspector.md): Get overview of your current state of tracking - [Publishing](https://www.avo.app/docs/publishing/publishing/overview.md): Keep your downstream schema registries in sync with the Avo - [Avo Codegen](https://www.avo.app/docs/implementation/avo-codegen-overview.md): Faster, more reliable implementation with type-safe tracking functions - [Avo Debuggers](https://www.avo.app/docs/reference/avo-debuggers/overview.md): Observe events and properties as you trigger them in your app ## Developer Reference - [Avo Codegen](https://www.avo.app/docs/reference/avo-codegen/destinations.md) - [Avo Inspector](https://www.avo.app/docs/reference/avo-inspector-sdks/overview.md) - [Avo Debuggers](https://www.avo.app/docs/reference/avo-debuggers/overview.md)