Hello Tim,
The Players engineering team has weighed in and decided that this is not something that they want to expose via an API event. Sorry to disappoint.
Cheers,
-Jeff Posnick, YouTube API Team
groups.google.com/group/youtube-api-gdata | apiblog.youtube.com | @YouTubeDev
On Mon, Apr 2, 2012 at 5:30 PM, Jeffrey Posnick <jeffy@google.com> wrote:
Hello Tim,
Yes, I'll update this thread when I hear back one way or another.
(Which hasn't happened yet.)
Cheers,
-Jeff Posnick, YouTube API Team
groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
@YouTubeDev
On Mar 30, 2:56 am, Tim Wintle <timwin...@gmail.com> wrote:
> Thanks Jeff
>
> Could you let us know if it's accepted for future work or if it's
> rejected?
>
> Tim
>
>
>
>
>
>
>
> On Thu, 2012-03-29 at 13:44 -0700, Jeffrey Posnick wrote:
> > Hello Tim,
>
> > Okay, I'll bring it up with the Players API team and see how they
> > feel about implementing that sort of callback. I can't make any
> > promises, though.
>
> > Cheers,
> > -Jeff Posnick, YouTube API Team
> > groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
> > @YouTubeDev
>
> > On Mar 27, 1:37 pm, Tim Wintle <timwin...@gmail.com> wrote:
> > > On Tue, 2012-03-27 at 09:41 -0700, Jeffrey Posnick wrote:
> > > > I don't think there are any plans to add that, and it might be a
> > > > tough sell.
>
> > > My justification for why it's worth doing:
>
> > > I believe the main reason for website owners to embed YouTube (besides
> > > bandwidth and ease of use) is because we want the videos to be
> > > shareable, and YouTube provides that for us - white-listing on most
> > > oembed containers, sharing options, messaging, etc.
>
> > > For a lot of sites, a "share" is the equivalent of a "conversion" on a
> > > retail site - not being able to optimise a page or site around them is a
> > > major issue, and might justify moving video hosting.
>
> > > The largest new feature in Google Analytics (besides the complete UI
> > > redesign) was adding tracking for sharing buttons - adding sharing to
> > > the YouTube player in a way which can't be tracked by that seems
> > > counter-productive from a "google wants to let you track social events"
> > > perspective.
>
> > > > What's the use case—is it required because clicking on those links
> > > > currently put the player into some sort of inconsistent state, and you
> > > > need to be notified of when that happens?
>
> > > That's not my issue (not sure about others).
>
> > > > Or is it mainly because keeping track of which videos got shared/etc. would be a useful
> > > > metric?
>
> > > Yup.
>
> > > You'd want to be able to set up a listener on your page which would hit
> > > Google Analytics Event tracking with a social event.
>
> > > > Also, how are you proposing this notification would work—a new state
> > > > that gets fired in onStateChange? Something else?
>
> > > That was what I imagined - the api is already there and well defined.
>
> > > Anything that would (mostly) work with the GA API would be fine:http://code.google.com/apis/analytics/docs/tracking/gaTrackingSocial....
>
> > > or if that's too complex (as you'd need message passing to the window to
> > > find which button had been clicked) then just an event to say that a
> > > sharing window had been opened.
>
> > > Tim
--
You received this message because you are subscribed to the Google Groups "YouTube APIs Developer Forum" group.
To post to this group, send email to youtube-api-gdata@googlegroups.com.
To unsubscribe from this group, send email to youtube-api-gdata+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/youtube-api-gdata?hl=en.
No comments:
Post a Comment