Yuhui's Data Science Blog

Data layers are an essential component of modern web analytics implementation. They provide an easily accessible and dynamic means of providing data from the website for marketing and analytics purposes, keeping it separate from the website's application layer. The most common data layer is probably the one associated with Google Tag Manager, or GTM. But other tag management systems, like Tealium, also provide their own data layers. The "new kid on the block" is the Adobe Client Data Layer, released in 2020. Unlike the other data layers, this one is independent of any tag management system, making it portable as well. I've prepared a simple, side-by-side comparison of how GTM dataLayer and Adobe Client Data Layer are used. This will help you be in a better position to understand their similarities and differences, and also how to properly transition from one to the other seamlessly. GTM dataLayer and Adobe Client Data Layer: a side-by-side comparison of us

About two months ago, my extension, YouTube Playback , was released on Adobe Experience Platform Launch (or Adobe Launch, for short). ( Read the blog post announcing its v1.0 launch. ) Since that time, it has been used in a couple of Properties, which is far fewer than I'd prefer, but I'm expecting it to grow in usage over time. Well, now, there's an even better reason to use it to track your YouTube video playback in Adobe Launch. Version 1.2.0 was released about a week ago, and it's what I would really consider the "real version 1" because of one key feature: Enable YouTube playback tracking within a Rule, instead of only at window load. This is an immense development. Previously, my extension would only enable YouTube playback tracking for videos that were loaded with the current web page. But if your YouTube videos were loaded dynamically, for instance, when a user clicked a button, then my extension would fail to track that video. Not any more!   Enable

About 2 weeks ago, I released a new extension for Adobe Experience Platform Launch (or "Adobe Launch" for short): Differential Privacy . In the current era of digital analytics where user privacy is becoming more and more important, what with governmental regulations and the like, it is increasingly important for analysts to consider protecting their users' privacy while still being able to do their analytical work with a fair amount of precision. That brings us to differential privacy . It's not a new idea, but it has become more prevalent in recent times. Essentially, it allows data analysts to be confident about their data at the aggregate level, but not too confident at the individual level. In that way, user privacy can be controlled for while still allowing good quality insights to be derived. For my extension, I implemented a very simple level of differential privacy: given a list of items and a random number, return either a pre-selected item (if the random

Today is a big day for me. After 24 hours over 10 days, my very first extension for Adobe Experience Platform Launch has been published: YouTube Playback . As the name implies, it allows marketers to measure playback of their YouTube videos – without any custom coding! It performs the following functions: Prepares YouTube IFrame elements with enablejsapi and origin parameters. Detects all YouTube player and playback events, including playback state change, playback quality and rate changes, and player errors. It also allows a selector to be used to select specific YouTube IFrame elements to track their playback. Announcement of my extension in the Launch Developers Slack workspace This has been a labour of love for me. It all started when I had to setup YouTube video tracking for a client in Adobe Launch. Like most marketers, I went with the tried-and-true method of adding custom code to work with YouTube's IFrame API. But as I worked on that implementation, I realised that this wa

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

When going from an Adobe Analytics world to a Google Analytics world or vice versa, you're bound to face terminologies that you're unfamiliar with, mainly because of how both products have evolved in their functionality over time. But never fear! Here's a handy cheat sheet to help you know what something in Adobe Analytics is similar ( but not always equivalent! ) to in Google Analytics, or the other way around. Base Terminologies Adobe Analytics Google Analytics Remarks Report Suite Property Besides data storage, an Adobe Analytics Report Suite provides the primary reporting interface. A Google Analytics Property does not have a reporting interface. Instead, its reporting interface is a View. Virtual Report Suite View An Adobe Analytics Virtual Report Suite is based on applying a segment to a Report Suite. A Google Analytics View is based on applying many filters to a Property. Visitor ID Client ID Modern implementations of Adobe Analytics rel

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