Sources and destinations for documentation

2 minute read

If you open the “Connections” tab in your Avo workspace you’ll find yourself in a place to define sources and destinations.

Sources and destinations are an important part of your tracking plan, and crucial for implementation, so we recommend maintaining an up-to-date list of them and attaching relevant sources and destinations to events. If you use Avo Functions the same data is used to generate the tracking code.


The sources are code bases that you send events from, for example your website, mobile application or your server.

The sources help you understand what app is sending particular events and they will also help you to locate a subset of changes to give to the platform developers to implement. Either using the “Copy instructions for developers” (on adoption steps 1 and 2) or the generated code (on adoption step 3) Avo will automatically select relevant changes for a particular platform and will help the developer to orient in the tracking plan.

Creating a source

To create a source press “Add Source” button in the “Connections” tab.

Add Source button

Then you’ll see a configuration dialog, define necessary config and press “Create Source”.

Source configuration

Managing sources in the tracking plan

What sources are sending an event is defined on the event level.

When creating an event we recommend to add it to all the existing sources where it’s sent from. This information is also used by the codegen to automatically create the tracking code if you are using the Avo functions.

Source configuration

Think “Import Completed event is sent from our web site”.


Destinations are analytics platforms you send events to.
In Avo you can use any event-based analytics destination.

Creating a destination

To create a destination press “Add Destination” button in the “Connections” tab

Add Destination button

Then you’ll see a configuration dialog, define necessary config and press “Create Destination”

Can't find your analytics tool in the list of available destinations? In that case you can pick the "Custom" destination type and give a descriptive name.

Destination configuration

Managing destinations in the tracking plan

What destinations you send data to is defined on the source level.

If you press the source name in the “Connections” tab it will open the source details where you’ll be able to pick destinations this source sends data to.

Web source details

Think “Our web app sends data to Amplitude”.

What's next?

Now you know how to define and maintain sources and destinations in Avo. Next thing to learn is the branched workflows.