Yuhui's Data Science Blog

Update (10 December 2020) : the Google Analytics definition of "visit" used here is for Classic and Universal Analytics. It is not applicable to Firebase / GA4's definition. In a perfect web analytics world, an analyst would be able to take all of his knowledge about one product and apply it to another. All of their technical and analytical knowledge would be transferable easily, and the analyst can easily switch between web analytics products without missing a beat. But we don't live in that perfect web analytics world. So we have to contend with differences in web analytics products, especially technical differences that result in reporting differences. One of those differences is something as fundamental as what a "visit" is. Understanding this is crucial to a web analyst's job because it is the foundation upon which a lot of other data and reports depend on. Crucially, metrics like Conversion Rates and dimensions like User Loyalty depend on what

When publishers have a lot of video (or audio) content in their websites, their key measurement requirements would be to know a) how many people are watching their videos, and b) which parts of the videos are people watching. In this three-part series, I describe how to use Adobe Experience Platform Launch (or Adobe Launch, as it's more commonly known) to track video playback events to Adobe Analytics or Adobe Media Analytics: Part one (this part): tracking video playback events using Adobe Analytics' Custom Links Part two: tracking video playback events to Adobe Media Analytics, Adobe's media tracking and reporting solution. Part three: tracking Brightcove video playback events to Adobe Media Analytics, instead of Brightcove's own analytics integration. (Each part if written as a standalone guide, so you don't need to read them one-by-one.) There are a few things to note: These instructions work with HTML5 audio and video only , because they depend on