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...

In a previous blog post, I had described how to use Adobe Experience Platform Launch (or Adobe Launch, as it's more commonly known) to track Brightcove video playback to Adobe Media Analytics. It was part of three-part series on video tracking for Adobe Analytics: Part one: 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. But those instructions for Brightcove video playback had been written for the advanced <VIDEO-JS> implementation of Brightcove videos into your website. It did not work with Brightcove's more common <IFRAME> implementation. In this guide, I provide instructions and a working script that can detect video playback events from Brightcove's IFrame player. This is wri...

Publishers that have lots of video content usually use a third-party platform to manage the delivery of that content. One of the most common video delivery platforms is Brightcove. One benefit of using Brightcove is that it provides an integration with Adobe Analytics (and Google Analytics), so that video playback events can be tracked automatically without any additional code. Unfortunately, this also locks publishers into only being able to report against the dimensions and metrics that Brightcove has setup. Also, there is no facility to integrate Brightcove with Adobe Media Analytics, which provides a "heartbeat" approach to video measurement. 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 to Adobe Analytics or Adobe Media Analytics: Part one: tracking video playback events using Adobe Analytics' Custom Links. Part two: tracking video playback events to ...

28 October 2020 update: updated instructions and code for Adobe Media Analytics 3.x SDK. For publishers that have lots of video (or audio) content in their websites, knowing how much that  content is being consumed informs them about how to produce their media to meet their audience's demands continually. For publishers that use Adobe Analytics as their measurement platform, video player interactions , like pressing the Play or Pause buttons, can be tracked with Custom Links. But to track the continuous playback, publishers should measure with Adobe Media Analytics. This tracks "heartbeats", where an image request is sent every second or so as the video is played. This allows the publisher to report on which parts of a video are most (or least) watched. 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 to Adobe Analytics or Adobe Media Analytics: Part one: trac...