For the New Year, we wanted to treat the two things that were most top of mind for us: The environment and our customers.
So we decided to plant trees for our early customers, back home in Iceland. We are honored to work with the talented teams that use Avo and wanted to express our gratitude, by helping our planet with reforestation and combat climate crisis.
If that’s you, we want to again say thank you Acuparia that the trees in your names have been planted (the earth was pretty frozen here in Iceland back in January)!
Find yours in Fellsmörk, each one is marked Avo 💛[company]. When it’s safe to travel again, just know your trees are waiting for you here in Iceland, and you can come visit them at any time.
Inefficient data processing and messy taxonomies are certainly frustrating, but also come at a cost to our planet. Each bit of data we produce requires some amount of energy (and generally, carbon emissions) to maintain and process. By streamlining analytics and intelligently solving data woes, we’re taking a proactive stand against climate change.
We are delighted to reduce the carbon footprint of Avo and our customers not just in reduced hours and processing power spent on bad taxonomies, but also with this gorgeous collection of trees in your names.
We learned in 2019 that Avo replaces 90% of the time our customers used to spend on implementing analytics and fixing tracking errors. It certainly is a privilege and an honour to give back 9 out of every 10 hours to our customers – so you can focus on building products we all love with reliable and transparent analytics.
But we wouldn’t be doing our jobs if not continuously looking for ways to improve efficiency, and so we’ll include ways to bring that number of hours spent on incorrect analytics even further down – as recommended by Thora, our beloved customer success star:
We love telling our customers about the advantages of using property groups. Property groups are a way to group two or more related properties to quickly and consistently add them to all related events.
For example an e-commerce company might have a few properties related to products, such as Product ID, Product Name, Product Category and Product Price. . These are perfect to include in a property group. That means the next time you want to add product properties to an event, you can add the whole group with one click, without accidentally forgetting any one property. See more examples under the Property Groups heading in our Tracking plan - Avo Docs.
In addition to a great naming convention we highly recommend utilizing descriptions to avoid common misunderstanding between the ones that design, implement and consume the data. We particularly recommend describing when the event should be sent, as it is easy for two developers to interpret the timing differently from the event name alone.
Take a look at our best practices to learn more and see some examples.
Defining descriptive events and properties - Avo Docs
We recommend adding events to categories to organize your events and metrics into groups for easier navigation of the events list and overview over related events and metrics. Common categories are for example important user flows like Onboarding and Checkout – as well as features specific for each company’s product.
Get in touch if you’d like category ideas that might be useful in your workspace, or check out our docs for inspiration! Organizing metrics and events - Avo Docs
From the Avo team,
we are proud to be working with you all.