Yuhui's Data Science Blog

This article was posted originally at Adobe Experience League Communities. (Disclaimer: The following recommendation is based on my personal experience. It is not endorsed nor recommended by Adobe or any of its partners.) Background: sending more than one beacon in the same page When it comes to accurate analytics tracking, one of the most important things to guard against is that you don't track variables that shouldn't actually be tracked. This happens particularly often when multiple beacons are sent from the same web page. A simple example is what happens when you want to track a link click on a page. When the page's Pageview beacon ( s.t() ) is sent, you might have tracked eVar8 with the page's site section. This eVar8 remains set in the Analytics "s" object. So when you track the click on the link with a Custom Link beacon ( s.tl() ), that eVar8 would be tracked as well – even if that wasn't your intention . This problem manifests itself ev

A new milestone has been reached for my YouTube Playback extension for Adobe Experience Platform Launch. With version 1.5.0, video milestones can now be tracked! (And also customised states when the video is playing.) For a long time, I've resisted adding video milestone tracking to my extension for one simple reason: it's not actually a supported feature in YouTube's IFrame API. My goal for my extension was to ensure that whatever functions that YouTube exposed in its API could be accessed through my extension with no (or little) coding. To that extent, I had succeeded. But my extension's users wanted more. And top of their list was video milestones. This is where pre-set milestones, like 25%, 50% or 75% of the video, will trigger Events that Adobe Launch can detect and operate on. Whenever someone asked me for it, my usual response was "That's not in the API, so you'll have to write your own custom code for it." But that response was clearly not wha