Comments on: Brightcove Video in SiteCatalyst 15

By: Pavan Prasad

Pavan Prasad — Wed, 02 May 2012 02:59:10 +0000

We are also facing the same issue of Video Name not getting populated. The AppMeasurementExtension.swf needs to modified to facilitate this.

Secondly, you will need to ensure that you are providing the correct value for visitorNamespace and trackingServer if you are not using the normal Brightcove analytics engine.

Pav.

By: Phil Almeida

Phil Almeida — Thu, 29 Mar 2012 16:41:13 +0000

It’s a social world we are living in.

http://www.facebook.com/Brightcove

If you would like to see this change put into action then you can ‘like’ the comment which now appears on their Facebook wall or add your own.

By: Tim Elleston

Tim Elleston — Mon, 26 Mar 2012 06:36:02 +0000

Phil, unfortunately, there isn’t a way I know of that passes the friendly name of the video through. That’s definitely a pain as you need to use classifications to get reports nice. It would be great if more people approach Brightcove to enable this though.

By: Phil Almeida

Phil Almeida — Fri, 09 Mar 2012 16:23:37 +0000

We have just gone through this exercise on one of our players to test it before moving ahead with a wide spread roll-out.

What is unfortunate about this is that, rather than feeding the Brightcove Video Name into whatever prop/evar represents the Video Name in the Sitecatalyst reporting, what gets passed is the Brightcove Video ID prefaced with the Brightcove API version, like this:

Video by Player
1 Brightcove 3:1323832461001
2 Brightcove 3:1402642239001
3 Brightcove 3:1350747819001
4 Brightcove 3:1313014035001
5 Brightcove 3:1395327953001

This is not particularly useful to anyone. Even if they had a way to correlate the video ID to an actual video name this greatly limits the usability of this information to end users.

If you know of a way to change this, one that does not involve uploading classifications, but rather adjusts things so that what gets passed initially is the Brightcove Video Name and The actual player name instead, it would be really great to see a follow-up post from you on that.

By: Tim Elleston

Tim Elleston — Mon, 13 Feb 2012 21:03:55 +0000

You’re absolutely right Patrick – my error in the post. The actual config file does have the correct capitalisation – thanks for pointing that out and I’ll update it shortly.
Cheers
Tim

By: Patrick Brown

Patrick Brown — Mon, 13 Feb 2012 17:02:43 +0000

Hey Tim,

Great post, but there are some errors in your XML file. If the node names aren’t capitalized properly the tracking won’t work.

For example, the following XML nodes should be mixed case:

debugTracking
visitorNamespace
trackingServer
Media
autoTrack
trackMilestones
trackVars
trackEvents
segmentByMilestones
trackUsingContextData
contextDataMapping

By: Tim Elleston

Tim Elleston — Sun, 18 Sep 2011 14:07:21 +0000

Hi Toby and Jai. You both raise good questions and to be honest, I don’t have an answer to that at the moment. If I get some spare time, I’ll check into it though and post back something if I find a solution.

By: Jai

Jai — Thu, 08 Sep 2011 19:33:30 +0000

Hi Tim,

This is a very clean blog post. I got the url from a webinar hosted by Semphonic. I have the same question as Toby about HTML5 players. Since swf method will not work for HTML5 players, do you have any tips on video tracking with HTML5 players?

THanks
Jai

By: Toby

Toby — Sun, 28 Aug 2011 21:33:25 +0000

Hi Tim,

Nice post. We are currently looking at this atmo. Two questions come to mind;

1) From your understanding, what are the options as you understand it using the method above for setting when the players sends Omniture server calls?

In our applications, we need to control costs around tracking long form videos with pre-, mid- and post-roll ads and would prefer only to send through data at the start of each ad or content segment. Our current Sc14 tracking implementation had to be custom created in order to achieve this. I’m wondering if Sc15 standard tracking will achieve this.

2) Will the above method also cater for the HTML5 players that Brightcove can auto-deploy using their client-aware smart player switching, or would we have to code a separate js-based tracking solution for these?

Happy for you to say ‘don’t know’ to either, and I’ll take up the questions with Omniture ClientCare

Cheers,
Toby