We’ve been busy talking with many of you about what really gets in the way of high-quality data. One message kept coming up: unclear ownership.

When no one knows who owns what, releases get delayed and trust breaks down. So we’ve built new functionality to make ownership real: visible, actionable, and enforceable.

This update builds on the foundation we introduced last year, and it’s a big step toward scalable, collaborative governance.

Why data breaks when ownership is unclear 💔

In our latest blog post, we dig into why data ownership is still so hard to operationalize. Here’s what stood out:

• Ownership often lives outside the tools where work happens
  
  
• Central data teams become bottlenecks, pulled into too many manual reviews
  
  
• Product teams want to own their data, and central teams want to empower them, but there’s no structure to support it
  

Read the blog post → Who owns this event?

Introducing: Actionable data ownership ⚡️

Automated reviews. Enforced accountability. No more guesswork.

We’ve built on the stakeholder foundation we introduced last year, making ownership in Avo more flexible, visible, and finally integrated into the way people work. Now, data ownership isn’t just documented. It’s operational.

Clarify accountability for events, variants and properties

Until now, stakeholder teams could be assigned as stakeholders on events and event variants. With this release, they can also be assigned to properties. And, more importantly, designated as owners across all three item types. That means there’s no ambiguity about who’s responsible for what.

Stay aligned on schema changes

Instantly see which teams are impacted by branch changes, so you can reduce risk and loop in the right collaborators early.

Get the right eyes on your data

Avo notifies your team in Slack when your data structures are affected, whether by drafted branch changes or Inspector issues. No more chasing reviews and fixes in DMs.

Protect mission-critical tracking

Require stakeholder teams to approve changes before branches are merged, enforcing quality without manual oversight.

Prevent silent edits and ambiguous ownership

Lock branches after approval, and enforce audit rules to block merges if new events lack owners. Ensure accountability from day one.

Focus reviews where it matters

Filter branch views to show only changes since your last review, so you never have to re-read what you’ve already signed off on.

Connect ownership downstream

Include metadata on stakeholders and owners in your schema publishing, so your downstream tools and workflows stay in sync—automatically.

Read all the juicy details -> The full release update

How Delivery Hero Aligns Tracking Across 11 Brands 8x Faster 🏃💨

New customer story!

When you're operating in 70+ countries with 11 brands, managing data quality at scale gets complicated, fast. Here's how Delivery Hero used Avo to create a federated governance model that aligned their teams and accelerated reviews:

✔ 8x faster tracking alignment
✔ 5x faster debugging
✔ High-quality data for ML, billing, and analytics

Avo is the true foundation for our data solutions. Before Avo, aligning data collection across brands took months. Now, it takes about a week.

— Cathy Wong, Senior Data Governance Manager, Delivery Hero

Read the full story → Delivery hero case study

New quality-of-life updates 💆

We’re always listening to your feedback and improving Avo to match how your team works. Here are a few recent updates that make your workflow smoother:

Properties in multiple bundles

Previously, each property could only belong to one bundle. That forced teams to split bundles or duplicate work. Now, you can assign properties to multiple bundles, making your tracking more flexible and reusable across teams.

This feature is currently in closed beta. Reach out if you’d like to try it.

Learn about property bundles ->

Bulk edit Inspector issues

Triage faster with fewer clicks. You can now bulk ignore or resolve issues directly in the Inspector view, perfect for cleaning up a backlog or quickly closing out known duplicates.

Learn about bulk editing Inspector Issues->

Import improvements: variants and name mapping

Our import functionality just got more powerful. You can now include event variants and name mappings in your uploads. Plus, importing via API is now supported in a closed beta, contact us to get access.

Importing variants and name mapping ->

Rich text in all descriptions

You’ve had rich text support in category and metric descriptions, and in comments. Now, it’s available in event and property descriptions too, so you can better document context and communicate clearly across teams. 

More updates coming soon!