Avo provides a set of developer tools to make it faster and less error prone to implement tracking code. Avo Codegen, our type safe analytics wrappers, are one of those tools. Using Avo’s developer tools is optional, but something we highly recommend.
In this guide we’ll cover how to implement analytics events with and without using Avo’s developer tools.
You can continue implementing your tracking code like you are used to using analytics SDKs from analytics platforms (like Mixpanel, PostHog or Amplitude), SDKs from CDPs (like Rudderstack, Segment or mParticle), or using internal built SDKs or APIs.
A typical implementation workflow looks like this:
Avo Codegen produces type safe analytics wrappers that are code generated based on your tracking plan. Designed to speed up the tracking code implementation, while also making it more reliable with type-safety.
Learn more about Avo’s developer tools in Avo 101 for developers:
For teams that are using Avo Codegen to implement their tracking code, the typical implementation workflow looks like this:
If Avo Codegen haven’t been set up in your project yet, learn how to set them up in our Avo Codegen quickstart guide: