The generated code gives you access to functions, each function representing an event, user identification, user properties update, page view, revenue or mix of those as they are defined in your tracking plan.
We call those functions Avo functions.
You invoke the Avo functions, provide tracking parameters and
It's useful to get the overview of the tracking implementation when working on new tracking. You can also get more insights into dev implementation and actual production state of your tracking with the Inspector implementation status
When tracking plan changes, you generate the file again and swap the old file with the new one. Avo manages the merge conflicts inside the file. Then, if the existing events changed, you'll have to update your Avo functions calls according to the new tracking plan to pass the runtime checks in the Avo file. You'll also get access to the new events defined in your tracking plan after the previous generated code update.
Avo supports multiple languages and platforms:
Each platform/language combination supports a set of event destinations. We often add support for new destinations, and Avo also allows you to send to custom destinations. For an overview or implementation details please see the docs for Analytics Tools.
We are currently working on adding support of the following languages:
Even if your favorite language isn’t currently listed it might be arriving soon. In any case, please contact us to inquire or let us know what you’re looking for.