You may wonder, why I created the three implementation criteria at all.
It’s really about one thing, consistency.
In the end, what Component Analytics sets is to achieve is scalable consistent analytics.
Having your data analysts get the same data for the same interaction on different pages makes them confident in their analysis.
Their experience analyzing the site will lead to predictable analytics.
That is, when they see any part of the site, they will know how to find it in the data.
This improves communication, as any department can ask the analysts by showing the part of the site they’re interested in.
The streamlined communication and the predictability of the analytics leads to increased speed.
The increased speed comes in three parts:
- Automating Component Analytics leads to less development time spent on it.
- Predictable analytics leads to less time spent on analyzing and understanding the data.
- Which means other departments get their analysis faster.
In my experience, analytics consistency is where a lot of sites falter.
Consistency is strongly correlated with high data quality.
Which means a lot of site analytics have low data quality.
Give your analysts the best tools available by implementing Component Analytics.
– Samy
Component Analytics daily
Every weekday, I publish about Component Analytics and analytics collection strategies.
