![Dive deep into Event Variants đ¤ż](https://cdn.prod.website-files.com/65bd765adb9e34fba478f2e7/668ff2d2a3cb80e31494ad11_July%20NL%20cover.png)
Dive deep into Event Variants đ¤ż
Your passion for better data is what drives us. And based on your valuable feedback, weâre announcing better ways to govern your data and bring even more precision to your data design.Â
Introducing Event Variants: a powerful way to create variations of existing events to suit specific scenarios. We briefly touched on Event Variants in our last update, but this time letâs take a closer look at how you can use Event Variants to add a layer of granularity to your tracking plan and bring clarity to your developers when it comes to implementation.Â
Today, weâll cover:
âĄď¸ What Event Variants are, and why theyâre useful
âĄď¸ How to pin properties to variants
âĄď¸ Adding images to show when a variant should be triggered
âĄď¸ Making variants source specific
𧪠Beta previews: Set advanced event naming rules and define allowed property values at the event level.
Event Variants: An airline example âď¸
Imagine youâre managing data governance at a major airline. You have an event âFlight Bookedâ, but you want to get more precise when it comes to variations of that event, letâs say for roundtrip and one-way flights.Â
With Variants for âRoundtripâ and âOne-wayâ bookings, you can add specific rules and conditions to the event to describe these scenarios.
1. Use Variants to only require properties where relevant
When creating the event, you add the typical properties youâd want to see included in all scenarios in the base event, such as name, ticket number, and so on. For your different flight booking types, youâll also need variant-specific properties. So for roundtrip flights, you may want to specify âInbound Flight Numberâ and âInbound Departure Timeâ properties which are only required for roundtrip bookings. With Event Variants, youâll now have this crucial information clearly documented without needing to set up a separate event for each booking type.Â
![](https://cdn.prod.website-files.com/65bd765adb9e34fba478f2e7/668ff317f3f6afb589e33bf4_AD_4nXfi9rNY3jAl2WQfZD7eMP50tNdppBZv36gEFfLuxLmBWYcFh68XJYDEzitHHRtTafR5YMGiuFSDvUhH-Oe4-dwLElDT1S6FvrNi_KmYsymeVlvjt7uchPkb668JmutTOflME3Tz4Qsh_NF8SXO0H1WdrmE.png)
2. Specify booking type with a pinned property value
Letâs say youâve added âBooking Typeâ as a property on the base event. You can bring more clarity here by pinning the property value âOne-Wayâ or âRoundTripâ to either variants, to ensure events for one way bookings always have âBooking Typeâ set as âOne Way Booking Typeâ, and vice versa. Pinning properties in this way will make implementation easier, since developers will get clearer instructions on how the event should be sent for each scenario. If you're using Codegen, developers won't even have to think about the pinned property valueâit's automatically sent to all your destinations when the Event Variant is triggered.
![](https://cdn.prod.website-files.com/65bd765adb9e34fba478f2e7/668ff317f772150996144f0c_AD_4nXea8zrhLgAbbxyctK7cyYwoawbVS3ErYSnSadDI1yuwclG7tVoXYmIcGaKA1zEDARBiz9MNoUQ4oI9hX8gFh1k1ajPTjSpxTDbugPZuCG9uU4tKGS8r0Lf1u6OZyFsQFq6bvBVU4J2YvO_tXemr0GO1JsPQ.gif)
3. Show where the flight booking originates with Event TriggersÂ
When collaborating on data design, itâs a good idea to make it crystal clear where an event should be triggered. Now, we can add triggers to each variant with screenshots, to make it clear when each variant should be triggered.Â
![](https://cdn.prod.website-files.com/65bd765adb9e34fba478f2e7/668ff4c6a0005578fc3cbbef_LatestTriggers.gif)
Itâs as simple as taking a screenshot and uploading it under âEvent Triggerâ to paint a picture of where the event should trigger. In this example, we can add a screenshot of the different types of flights being booked to precisely describe where and when our variants should be sent.Â
4. Toggle sources for each variant
There may be occasions when you want to create an Event Variant, but itâs not relevant for all your sources. Itâs easy to toggle which sources your variant should apply to. In our Airline scenario, letâs imagine the iOS team is still working on their flight booking experience for one way flights. In a couple of clicks, we can easily toggle the âOne Wayâ variant off for iOS, and turn it back on again later when theyâre ready to roll out the feature.
Stay tuned for more Event Variant updates (coming soon)
With these upgrades to Event Variants, weâve made significant steps towards a more granular tracking plan that works for domain owners and global governance leaders alike. To sum up, our latest Event Variant updates include:
- Descriptions
- Event triggers
- Source selection
- Property presence
- Pinned property values
- Variant specific Code Changes and Codegen functions
- Variant details included in Publishing integrations
Join the Beta: Advanced event naming rules and define allowed property values at the event levelÂ
Still reading? Awesome, because we wanted to use this opportunity to let you know about two new beta features we are very excited about.
Advanced event naming rules
Creating perfectly named events is about to get a lot easier, for anyone on your team! Set advanced rules to ensure workspace editors structure their events correctly (like object before action), use approved words (for example for describing generic user actions), and nail the casing every time, even with complex casing conventions.Â
Curious? Dive into our docs or reach out to us (at the email provided below) to request access!
![](https://cdn.prod.website-files.com/65bd765adb9e34fba478f2e7/668ff317d5c59a90805d5935_AD_4nXfl_0iECkDeTnY5BDW1lqtfXjRzHmYE4FHYvqXEKS1engOuaXhsEaImBZqFSJKF5LthYBiWm9_rdyB4P7CS_fKuPqTwwkYq3KLdM7T7FSuML8weRF0y3rw73hHlGk4K576dtkUcgd91yRGHmFd3EbUBV8Gd.png)
Define allowed property values at the event level
We heard you loud and clear, youâd like to be able to define allowed property values at the event level, and thatâs exactly what our latest beta release enables you to do.
Weâll be rolling out a private beta over the next few weeksâreach out to us (email below) if youâre interested in taking it for a spin in your workspace!
![](https://cdn.prod.website-files.com/65bd765adb9e34fba478f2e7/668ff8085912ab4bca29b354_Allowed%20values.jpg)
Thatâs it for now, but weâll continue to roll out more functionality to Event Variants and to other Avo features, so if thereâs something youâd love to see included, let us know!
As a reminder, you can reach us at support@avo.app with ideas, questions, feedback, or to get access to these latest beta features. Otherwise we wish you good luck, and have fun on your journey to better data.