We’ve added a new section at the bottom of your dashboard to help you visualize how much better Tracklution performs compared to traditional client-side and third-party pixel tracking.
We’ve added a new section at the bottom of your dashboard to help you visualize how much better Tracklution performs compared to traditional client-side and third-party pixel tracking.
It includes two panels:
This chart shows how many events Tracklution was able to recover that would have otherwise been lost due to tracking limitations:
Total recovered events: Events saved from being blocked or dropped, including:
Not under tracking restrictions: Events tracked from browsers that do not prevent tracking, like Chrome.
💶 Hover for € values to see the tracked monetary value of recovered value-based events (e.g. Purchases, ViewContent).
📈 Hover over bars to see what was saved despite blockers or browser restrictions.
This is the first version of the Recovery Panel, so some of the data may still need fine-tuning. For example, in certain cases the recovered Purchase value may be slightly off.
Also, while the panel highlights events affected by tracking restrictions, it may appear as though a percentage of events are always lost with client-side tracking. That’s not entirely accurate- those events are at risk, but not always completely blocked.
Client-side tracking can still work in some restricted environments depending on:
So while those events are at risk, they aren't always blocked 100% of the time. The highlighted percentage represents potential loss, not a guaranteed drop.
We’re actively improving the accuracy- just keep this context in mind when reviewing the numbers. 😊
Want to see how the GTM template by Simo Ahava works in practice?
We’ve got a full walkthrough video included in this article: 📺 Watch here
It’ll show you exactly how to set it up in Google Tag Manager without leaving you puzzled.
🚀 As always, happy tracking,
The Tracklution Team