It seems people in our industry use these two words interchangeably and this has created some confusion as to when we should properly use the words reporting vs. analytics and in what context. Trevor’s article goes into detail on when you should or shouldn’t use these two words and adds fun illustrations to drive the point home as to why it matters.
When I sat down with Trevor, we dived a little bit into what his company, Bitten Labs, does and how he became a data scientist. Trevor revealed to me that the main reason why we confuse reporting and analytics is because they both work hand-in-hand with one another. You honestly can’t have one without the other, so sometimes the lines between what they’re responsible for does get blurred.
Trevor shares some examples as to when it’s the right time to use analytics and when it’s the right time for reporting. In fact, based on Trevor’s definition, it should really be called Google Reporting, not Google Analytics.
After we had cleared up the subtle differences between reporting and analytics, I wanted to pick his brain on another article he wrote entitled,CRAPOLA design principles for quantitative data. His title really stuck out to me and his article on LinkedIn only covered the very basics as to what CRAPOLA stands for and means. My interview with Trevor on episode 3 of After Hours Marketing dives further into the CRAPOLA acronym for those who are eager to find out!
When I had finished the interview with Trevor, Andy and Damon joined me to discuss what they thought of Trevor’s conversation and the reporting vs. analytics definition. I really enjoyed their input on this and thank Trevor for helping us get a little clearer on what it really means when we talk about analytics or reporting.