Different tracking methods in Mida
Queue-based tracking (recommended)
<script>
window.mdq = window.mdq || [];
window.mdq.push(["track", "Clicked Sign Up"]);
</script>
This is the recommended way to track events in Mida. It records events in a way that allows them to be used as goals across multiple experiments.
One of its biggest advantages is that it works retroactively — you can launch a test first and define your goals later without missing any data.
mida.track()
This is the underlying event tracking method used by Mida. It logs events to the database so they can later be selected as goals in experiments.
While it works the same way functionally, calling mida.track() directly requires Mida to be fully loaded. Using the queue-based snippet above is safer and recommended.
mida.converted()
This method is more limited in scope. It ties conversions directly to visitors in a specific test and updates their status in real time.
Unlike event tracking, it doesn’t work retroactively and cannot be reused across experiments. While it may work for simple setups, event tracking is better suited for long-term and more flexible testing needs.
In essence
Event tracking (
mdq.push(["track", ...])/mida.track()) logs events to the database. When reports are generated, Mida matches events with experiment results during the test period.mida.converted()directly flags visitors in a test as converted in real time, without broader tracking capabilities.