Implement analytics events

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.

Implementing 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:

1. Use the Branch Code Changes as a task list for what events need to be implemented or updated changed to align with your tracking plan changes.
2. Open a git branch to implement your analytics tracking changes in your product’s codebase.
3. Implement the changes in your existing analytics tracking code, using the schema details provided by Avo as your reference.

Branch Code Changes

Read more on using the branch code changes screen for a simple and accurate implementation

Read

Implementing with Avo Codegen

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:

Avo 101 for developers

Learn about Avo’s developer tools

Read

For teams that are using Avo Codegen to implement their tracking code, the typical implementation workflow looks like this:

1. Open a git branch to implement your analytics tracking changes on.
2. Use the Avo CLI to pull the updated code from the branch you are implementing. You can find the Avo CLI command for each source in the top right corner of the branch review screen under “Branch Implementation”. From there you can also access documentation for all the events that need to be implemented
3. Use the functions provided Avo Codegen to implement your events in your source code. Codegen tab in your workspace provides documentation and code snippets for each event

If Avo Codegen haven’t been set up in your project yet, learn how to set them up in our Avo Codegen quickstart guide:

Avo Codegen overview

Start using Avo Codegen

Read

What’s next?

5. Validate implementation

Learn how to validate implementation

Read