Adobe Experience Platform Launch has been rebranded as a suite of data collection technologies in Adobe Experience Platform. Several terminology changes have rolled out across the product documentation as a result. Please refer to the following document for a consolidated reference of the terminology changes.
Prerequisites
Each tag property in Adobe Experience Platform requires that the following extensions are installed and configured from the Extensions screen:
Use the “Embed a player using an <iframe> tag” code snippet from the Google developer docs in the HTML of each Web page where a video player is to render.
This extension, version 2.0.1, supports embedding one or more YouTube videos on a single Web page by inserting an id
attribute with a unique value in the iframe script tag, and appending enablejsapi=1
and rel=0
to the end of the src
attribute value, if not already included. For example:
<iframe id="player1" width="560" height="315" src="https://www.youtube.com/embed/xpatB77BzYE?enablejsapi=1" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
This extension is also designed to dynamically check for a unique ID attribute value, like player1
, regardless of whether the enablejsapi
and rel
query string parameters exist and if their expected values are correct. As a result, the YouTube script tag can be added to a Web page with or without the id
attribute and whether the enablejsapi
and rel
query string parameters are included or not.
On pages with more than one video, each video uses the same configuration set in the tag rule executing on that page. For example, if you create a rule with an event that triggers on video 50% complete, each video on the page triggers the rule at the 50% cue point.
The Extension relies on the following logic to rewrite the iFrames:
document.onreadystatechange = function () {
if (document.readyState === 'complete') {
Therefore, there is a slight flicker after the page loads. This behavior is expected.
There are six data elements available within the extension, none of which require configuration.
There are eight events available within the extension, only Custom Cue Point Tracking requires configuration.
player.getCurrentTime() === 0
player.getCurrentTime() !== 0
One tag rule can be set for every video event (the seven events listed above). Create a specific tag rule for each event you want to track. If you do not want to track an event, simply omit to create a rule for it.
Rules have three actions:
The following video extension objects are to be included.
Events: “Video Start” (This event causes the rule to fire when the visitor starts playing a YouTube video.)
Condition: None
Actions: Use the Analytics extension to “Set Variables” action, to map:
Then, include the “Send Beacon” action (s.tl
) with link name “video start,” followed by a “Clear Variables” action.
For implementations where multiple eVars or props for each video element can’t be used, data element values can be concatenated within Platform, parsed into classification reports using the Classification Rule Builder tool, as explained in https://experienceleague.adobe.com/docs/analytics/components/classifications/classifications-rulebuilder/classification-rule-builder.html, and then applied as a segment in Analysis Workspace.
To concatenate video information values, create a new data element called “Video Meta Data,” and program it to pull in all the video data elements (listed above) and assemble them together. For example:
var r = [];
r.push('YouTube'); //Player Name
r.push(_satellite.getVar('Video ID'));
r.push(_satellite.getVar('Video Name'));
r.push(_satellite.getVar('Video Duration'));
r.push(_satellite.getVar('Extension Version'));
return r.join('|');
For more information on how to create and leverage data elements effectively within Platform, read the data elements documentation.