Designing and implementing analytics in Avo is now more collaborative, flexible, and scalable: you can push and pull events, properties, and property bundles between branches.

As tracking plans grow and more teams contribute across platforms, one challenge comes up again and again: How do we scale our event data structures without slowing everyone down?

Branches often contain shared changes, but teams rarely ship on the same timeline. Until now, that meant two imperfect options:

• Delayed merges, which stall collaboration and trigger false positives in data validation
  
• Early merges, which block Codegen pulls and pollute the source of truth for downstream tools

Neither scales well—especially as more teams, sources, and platforms get involved.

Push & Pull: Designed for how teams actually work

You can now push and pull items between branches—making tracking structures discoverable and reusable across branches without conflicts. Whether you're collaborating across teams or splitting up a large branch, this gives you reusable tracking structures that stay in sync—without merge conflicts or duplicated effort.

Here’s how it improves your workflow:

🔀 Break up big branches

Too many tracking changes leading to a bloated branch? Now you can push events, properties, bundles and sources (only available for pushing) into smaller, purpose-driven branches—perfect for focused implementation and easier review. The original branch keeps everything, and child branches can move at their own pace. 

👥 Enable asynchronous implementation

When multiple teams are responsible for implementing changes, timelines rarely line up. Now, each team can push just the items they’re ready to implement from the data design branch to their own implementation branch. For example, the iOS team can push events relevant to them to a branch, implement and merge, while Android continues working in their own branch.

♻️ Reuse without recreating

Working on a new feature and need a property or event that already exists on another branch? Just pull it in. Avo surfaces items from other branches in search, creation flows, and context views—so you avoid duplication and ensure consistency across branches.

How it works

1. Initiate push/pull

Start by pushing items from the Tracking Plan Changes view—available on any event, source, property, or property bundle.

Or pull items directly into your branch via:

• In-context search – For example, when adding a property to an event, Avo now surfaces matching items from other branches alongside those on your current branch.
  
• Creation modals – When creating new events or properties, similarly named items from other branches are suggested for reuse.
  
• Global search (CMD+K or search bar) – Search results now include items from other branches, making it easy to discover and pull existing structures.
  

2. Review

Once you initiate a push or pull, Avo presents a detailed preview of the changes. You can review related items—like sources, properties, or bundles—and choose what to include. Avo makes smart recommendations, but you’re in control.

3. Confirm

After reviewing, confirm the action. The item is now available in your current branch—ready to use, modify, or implement.

4. Merge

Pushed and pulled items retain the same ID across branches. That means when it’s time to merge, it’s smooth and conflict-free. Since items retain their IDs, Avo knows exactly how to reconcile branches—no manual cleanups, no versioning headaches.

Check out the full documentation to learn more.

A more scalable, collaborative Avo

As your tracking plan scales and more teams collaborate, managing change becomes harder—but with push and pull, it doesn’t have to be. This update makes it easier than ever to keep your tracking plan clean, reusable, and up to date—no matter how many branches, teams, or platforms you’re working with.

We can’t wait to see what you build with it. Let us know what you think—how can we make it even easier to collaborate on event data structures at scale?