This may be difficult without having a plugin within the s_code.js. The
HTML 5 player is based on how each browser decides to support the w3c
specification. There are people building wrappers around that. video.js
is an example and I know that Brightcove is currently working on one.
(they have one but it basic) I havent seen anyone come up with an api
for their HTML 5 wrapper yet. It will most likely be a JS plugin and
will need to take advantage ofr a video js framework for cross browser
You can only see the issues "you opened". So basically when I am out on
vacation for two weeks I have to give someone access to my account to
follow up (thats a really bad idea) . We have serveral people both
technical and on the analytics side who support our install. I really
need anyone in the team to be able to view, interact and follow up on
As a supported user it would be nice to see all of the tickets submitted
and open for my organization. We have a team of people who are
responsible for Omniture problems and the process of staying on top of
all the issues we open is challenging.
I'm glad to see there are consideration being looked at. I think my only
comment is your competitors certainly have a more open approach. I
understand the concern around cost of people heavily hitting the apis. I
personally feel that use of the API shouldnt be limited just like use of
the Site Catalyst inteface isnt limited. I think setting a reasonable
value of how open you can hit the API to limit load is reaosnable and
protects your infrastructure. Opening that up more and more as your
The integration with Brightcove works well however one feature that
would seriously improve the video reporting is the ability to assign
custom brightcove meta data to omniture props and evars. Since this
information is available in the Brightcove player API the tracking swift
could easily be extended to leverage this. You can expand your xml
configuration so that we could assign brightcove meta-data to props.
It doesn't look like the out of box video tracking functionality capture
the url that the video is embedded on. This seems like a valuable piece
of information that should be sent automatically so that you can report
on Viral Video. We currently have to go to our video provider to get
that information. We are big on making sure people can get their
information in one place.
The rumor of a REST api for site catalyst was good news. I suggest
opening up the API so we do not have to operate under a TOKEN based
solution. The current API calls are expensive in that you have to burn
multiple tokens to get at the data. Ideally we would like to see the API
as open as Site Catalyst and more in-line with your competitors.