Loading Search...
Analytics Plug-in Guide

Audience and Overview

This guide is intended for all publishers that wish to integrate a Limelight Video Platform (LVP) player with an existing 3rd party analytics engine, such as Google Analytics or Omniture Sitecatalyst. You can configure an LVP player to send viewership metrics directly to your account by simply including the LVP Analytics Plug-in when creating a player. The inclusion of the plug-in does not prevent the tracking and reporting of metrics in your LVP console. Metrics that are sent to 3rd party analytics engines are in addition to those already reported in the 'Analytics' section of LVP.

Table of Contents

1.0 Google Analytics Tracking
2.0 Omniture SiteCatalyst Tracking

1.0 Google Analytics Tracking

An LVP player can be configured to send viewership metrics directly to an existing Google Analytics account. The tracking is enabled on a per-player basis using the LVP Google Analytics player plug-in. See below for instructions on enabling this feature. The LVP plug-in reports the following metrics to Google's event tracking system:

Media Type Metric
Media
Load Recorded when the media is made the focus of the player
Play Recorded when the media is played back for at least 1 second
Complete Recorded when the media completes
Replay Recorded when 'replay' is selected or when seeking back after htting the media complete screen
totalPlayTimeInSeconds Total time the media has been played
Milestone# Total for each playback milestone (25, 50, 75)
Ad
Load Recorded when ad is made the focus of the player
Complete Recorded when the advertisement is watched to completion
Channels
Load Recorded when the channel is made the focus of the player
totalPlayTimeInSeconds Total time the channel has been played
Live Stream
Load Recorded when the live steam is made the focus of the player
Plays (Views) Recorded when the live stream is viewed for at least one second
totalPlayTimeInSeconds The total playtime in seconds for all viewers

1.1 Enabling Tracking

You can enable Google Analytics tracking on any of your Limelight LVP players by following the steps outlined below :
  1. Obtain your Google Analytics account ID (e.g. UA-12345678-1)
  2. Log into your LVP account and access the Player Builder
  3. Select the desired player and click to 'Edit'
  4. Toggle to 'Expert Mode' then click the 'XML' tab
  5. Add the following code (substituting your own Google Analytics ID) right below the player declaration at the top of the XML: 

    <plugins>
<plugin type="analytics" url="http://static.delvenetworks.com/deployments/google-analytics-plugin/google-analytics-plugin-1.4.swf?account=UA-12345678-1&trackPageView=false"/>
</plugins>

    This screenshot shows the location of the code:
    (The plugin version shown in this image may not be current. Use the code above):

  6. Save your player. The player will now send metrics to Google Analytics

1.2 Viewing Metrics in Google Analytics

Your video metrics can be found by doing the following:
  1. Login to your Google Analytics account
  2. Click on your profile
  3. Click on 'Content' then 'Event Tracking'
  4. Click on 'Categories' and choose between 'media', 'channel', 'ad' and 'livestream'
  5. The useful metrics can be found in the 'Event Value' column
  6. To drill down to a specific media, click on a metric (e.g. load, play, totalPlayTimeinSeconds) and filter on the title


2.0 Omniture SiteCatalyst Tracking

A Limelight Video Platform player can be configured to automatically send viewership metrics to an existing Omniture SiteCatalyst account. The tracking is enabled on a per-player basis using the LVP SiteCatalyst player plug-in. See below for instructions on enabling this feature.

2.1 Enabling Tracking for SiteCatalyst 15

Before enabling SiteCatalyst 15 tracking on an LVP player, you must first complete the following setup:
  1. Work with your Omniture representative to complete a data mapping .XML configuration file (e.g. mycompany_config.xml). This file will contain your SiteCatalyst account identifiers (e.g. account name, visitor namespace, and tracking server) as well as mapping for all video events to your various Sitecatalyst account variables (e.g. evars and props). The following should be used as a template for this file (NOTE: the values that appear below are simply examples. You should replace the values with the specifics of your account):

    <config>
<account>my_report_suite</account>
<debugTracking>true</debugTracking>
<visitorNamespace>company_name</visitorNamespace>
<trackingServer>company_name.112.2o7.net</trackingServer>
<dc>112</dc>
<Media>
	<autoTrack>true</autoTrack>
	<trackMilestones>10,20,30,40,50,60,70,80,90,100</trackMilestones>
	<trackVars>events,eVar3,eVar4,eVar5</trackVars>
	<trackEvents>event13,event14,event15,event16,event40,event41,event42,event43,event44,event45,event46,event47,event48</trackEvents>
	<segmentByMilestones>true</segmentByMilestones>
	<trackUsingContextData>true</trackUsingContextData>
	<contextDataMapping>
			<a.media.name>eVar3</a.media.name>
			<a.media.segment>eVar4</a.media.segment>
			<a.contentType>eVar5</a.contentType>
			<a.media.timePlayed>event13</a.media.timePlayed>
			<a.media.view>event14</a.media.view>
			<a.media.segmentView>event16</a.media.segmentView>
			<a.media.milestones>
				<item name="100">event15</item>
				<item name="90">event48</item>
				<item name="80">event47</item>
				<item name="70">event46</item>
				<item name="60">event45</item>
				<item name="50">event44</item>
				<item name="40">event43</item>
				<item name="30">event42</item>
				<item name="20">event41</item>
				<item name="10">event40</item>
			</a.media.milestones>
	</contextDataMapping>
</Media>
</config>

  2. Save your config file as a .XML and host it on a web server that is publicly accessible. Note the name and address of this file; these will be used later to enable tracking on an LVP player. To avoid latency, it is recommended that the file be hosted on the CDN.
  3. Include a crossdomain.xml file in the root directory where your config file is hosted. For example, if your config is hosted at "http://www.yoursite.com/sitecatalyst/config.xml" then include the crossdomain file at "http://www.yoursite.com/crossdomain.xml". A crossdomain.xml file allows the LVP player to access your config file. See below for examples (feel free to use either of these as your crossdomain.xml).

    Cross-domain Example 1 -
    This allows any flash application on any website to make requests to your website. 
    <?xml version="1.0"?>

<!DOCTYPE cross-domain-policy SYSTEM "http://www.macromedia.com/xml/dtds/cross-domain-policy.dtd">
<cross-domain-policy>
    <allow-access-from domain="*"/>
    <allow-http-request-headers-from domain="*" headers="*"/>
</cross-domain-policy>

    Cross-domain Example 2 -
    This limits the requests to only flash applications that exist on Limelight-owned domains. 
    <?xml version="1.0"?>

<cross-domain-policy>
    <allow-access-from domain="*.delvenetworks.com" secure="false"/>
    <allow-access-from domain="*.limelightnetworks.com" secure="false"/>
    <allow-access-from domain="*.limelight.com" secure="false"/>
    <allow-access-from domain="*.llnw.com" secure="false"/>
    <allow-access-from domain="*.llnw.net" secure="false"/>
    
    <allow-http-request-headers-from domain="*.delvenetworks.com" headers="*" secure="false" />
    <allow-http-request-headers-from domain="*.limelightnetworks.com" headers="*" secure="false" />
    <allow-http-request-headers-from domain="*.limelight.com" headers="*" secure="false" />
    <allow-http-request-headers-from domain="*.llnw.com" headers="*" secure="false" />
    <allow-http-request-headers-from domain="*.llnw.net" headers="*" secure="false" />
</cross-domain-policy>

Now that you are done with setup, you can enable SiteCatalyst 15 tracking on any of your Limelight LVP players. To do this, execute the following:
  1. Log into your LVP account and access the Player Builder
  2. Select the desired player and click to 'Edit'
  3. Toggle to 'Expert Mode' then click the 'XML' tab
  4. Add the following code (substituting the address of your config file) right below the player declaration at the top of the XML. 

    <plugins>
<plugin type="analytics" url="http://s.delvenetworks.com/deployments/omniture-plugin/omniture-plugin-1.6.swf?configURL=INSERT_THE_URL_ENCODED_ADDRESS_OF_YOUR_CONFIG_FILE&displayName=title"/>
</plugins>

    This screenshot shows the location of the code:
    (The plugin version shown in this image may not be current. Use the code above):

  5. (Optional) To specify how media is represented in your Sitecatalyst account, include a value for 'displayName' in the above code. Valid values are: id, title, refId. For example, 'displayName=title' would ensure that all tracked media is represented by the media title in Sitecatalyst.
  6. Save your player. The player will now send metrics to Omniture

2.2 Enabling Tracking for SiteCatalyst 14

SiteCatalyst 14 tracking can be enabled on any of your Limelight LVP players by following the steps outlined below:
  1. Obtain the following information about your Omniture account:
    • Account Name
    • Tracking Server
    • Tracking Server Secure
    • VisitorNameSpace
    • dc
  2. Log into your LVP account and access the Player Builder
  3. Select the desired player and click to 'Edit'
  4. Toggle to 'Expert Mode' then click the 'XML' tab
  5. Add the following code (substituting your own values) right below the player declaration at the top of the XML: 

    <plugins>
<plugin type="analytics" url="http://static.delvenetworks.com/deployments/omniture-plugin/omniture-plugin-1.3.2.swf?account=your_account_name&trackingServer=your_tracking_server&trackingServerSecure=your_secure_tracking_server&visitorNamespace=your_visitor_name_space&dc=your_dc_value&pageName=pagename_where_player_is_embedded&playerName=your_player_name&trackMilestones=25,50,75"/>
</plugins>

    This screenshot shows the location of the code:
    (The plugin version shown in this image may not be current. Use the code above):

  6. Save your player. The player will now send metrics to Omniture