In the last couple of weeks we’ve been focusing on helping you design better tracking plans with Avo by showing you a tracking plan audit for all suggested changes in Avo. We also managed to squash a few bugs and improve a couple of things along the way.
Keep scrolling for updates on what we’ve been shipping 🚤
Up until now, when viewing changes on a branch, it has been fairly difficult to see the impact of those changes on the quality and consistency of your tracking plan as a whole – and reviewers have had to check manually for any issue on the branch.
To help you consistently get your tracking plan to a better state, we've launched an audit feature on the branch review screen where you can evaluate the quality of your work and quickly make fixes where needed.
The audit evaluates the same criteria for events and properties as the overall tracking plan audit, highlighting duplicates, incorrect casing, flagging missing descriptions and making sure all properties have a defined type.
Issues are highlighted in the context of each event, enabling you to fix them as you go while reviewing your changes
At the bottom of the branch review screen, you now have an audit listing all issues (or no issues, if you're a tracking plan rockstar 🎸)
When the audit flags events or properties with incorrect casing, Avo suggests an alternative name that adheres to your naming conventions – change to the correct casing in one simple click!
For Enterprise plans you’re able to enforce that there are no issues introduced on branches before they are merged.
Learn more about branch audits in this doc ->
As always, thanks for your invaluable feedback that allows us to make Avo better every day!
That’s all for now! Let us know what you think, and what you think we should build next, by hitting reply to this email 🤗
Love from the product team @ Avo 💛