We're super excited to announce a massive time-saver for your data design workflow 🤩. This is a feature that a lot of you have been requesting: the ability to bulk-edit your events in Avo.

So the next time you for example need to add that new source to 20 events, or introduce the same set of properties to a bunch of events, you can do it in one go.

In the events table, you can now hover over an event to see a checkmark next to the event name.

Once you've checked all the events you want to update, you can apply changes to them all in one go via the bulk action toolbar...

👉 Add or remove sources, properties, categories, tags or stakeholders

👉 Archive the events you selected

We hope this streamlines your experience defining events in Avo – as always we'd love to hear your feedback. Happy bulk-editing! 🎉

We have released full object support in C# codegen, including name mapping and pinned values in nested objects.

This feature is available on request as of today, please reach out to support to get it in your workspace.

Full public release is coming in the near future.

We’re excited to announce that Stakeholder Domains are now live in your workspace. This lets you segment your Avo schema registry by areas of accountability and ownership into domains, where a specific team can take charge of their data with a clear overview of the data that's most relevant to them.

A domain refers to a certain function or area within your organization. It could be a product area (Search, Checkout, etc), an entire app for specific personas (Drivers, Riders, etc) or a business function independent of the product (Marketing, Sales, Finance, etc.).

To allocate stakeholders to different parts of your schema, you'll first need to set up domains. You can do this by following the steps here.

Once your Stakeholder Domains are in place, you can assign relevant people as domain members. Domain members can filter the events table to show only the events most relevant to them.

Get started with Stakeholder Domains today, and let us know how it goes!

Now you can create variant specific regex rules. Give it a try!

We've launched the public beta for Kotlin Multiplatform codegen support. You can now create and generate code for Kotlin Multiplatform sources. Give it a try!

Today we're announcing an upgrade to event variants that let you tailor your tracking plan updates more closely to fit your use-cases: . This addition makes your tracking plan definitions more precise, reduces the scope of changes and simplifies accurate implementation.

You can either limit the values to a subset of the allowed values on the base event, or expand the set and include additional values specific to the variant. You can even create a brand new value for a property directly from the event variant. Any allowed values you've added will be visible in both the property details view and the branch changes view.

In addition to configuring your sources, properties, property presence and pinned-values we hope that configuring allowed property values will unlock even more use cases for event variants and help you even better define your tracking plan and narrow your implementation impact.

If you have any questions or ideas for further improvements for event variants we'd love to hear them! Don't hesitate to reach out to us via the chat-bubble in the Avo app or send us an email at hi@avo.app.

The JavaScript Codegen now includes support for to log page actions on custom destinations. This function aligns with the one used in our TypeScript Codegen, allowing for a shared interface between the two languages. This simplifies migration and enables seamless code reuse across both JavaScript and TypeScript without any modifications. The function is available on both and platforms. The new function name will be available in your Codegen the next time you run or run Codegen from a sources Codegen settings.

We're proud to announce a couple of enhancements to property validation: and . Both are designed to improve the accuracy of your property definitions, ensuring faster and more accurate implementation.

–the most requested feature in Avo history–provide greater flexibility in managing property values across different events. Previously, any specific property values had to be applied globally, leading to potential misuse and cluttered implementation. Now you can define and manage property values for individual use cases at the event level.

This enables you to contain the scope of changes to your tracking plan and streamline implementation, leaving you with a cleaner and more organized tracking plan. The intuitive UX for editing allowed values directly from either the event or property details gives you complete control and visibility over your allowed property values.

tackles the challenges of validating complex string values that have requirements beyond a set of allowed values. Until now, users had to rely on generic string types and manual descriptions to handle intricate validations like date formats or unique ID patterns. With our new Regex rule type, you can now document and validate these complex string patterns directly by documenting regular expressions and providing real-time examples for validation.

This enhancement not only improves development efficiency by documenting the regex as part of Codegen but is also included in our publishing integrations to allow you to accurately validate property values in your downstream tools.

We hope you'll find these improvements useful when defining your properties in Avo. To read more about event-specific allowed values and Regex validation, head over to our updated property documentation.

Along with some bigger updates we're working on for the properties view we're now displaying pinned values for events on the property details view. This helps you quickly identify pinned values right from the properties view and gives you a nice overview, preventing missing an event for a property that's for example pinned in all cases.

Before:

After:

We have added two fields to the payloads of the Webhook and the Export API, that are useful when working with event variants in Avo

Each event variant is represented by a standalone event in the JSON payload. It will have the same name, as the base event. Additionally, it will have the field included, with the event variant name defined in the Avo Tracking Plan.

You can distinguish an event, that is generated from a variant, from a base/standalone event, by checking the field. The of events that are generated from variants is , while regular events have it as .