Thanks for the update - yes I can see there is a difference between CMS and Channel user. Got that now. Thanks.
However I'm really struggling to understand where to get an accurate backup of our data. The overview report is great, but does not cover any of the financials. So no CPM, no Estimate Earnings, as well as a lot of great detail in some of the views and engagement reports. It appears the insight token only gives us access to just the one report.
Sure we can manually download them, but we managing about 15k videos today, and growing fairly fast. I don't see any way how to get this information cleanly?
Cheers,
Geoffrey
On Thursday, 17 May 2012 19:48:49 UTC+1, Jeffrey Posnick wrote:
Hello Geoffrey,
Please see http://apiblog.youtube.com/2011/10/introducing-google- account-support-and.html
Cheers,
-Jeff Posnick, YouTube API Team
groups.google.com/group/youtube-api-gdata | apiblog.youtube.com |
@YouTubeDev
On May 16, 12:45 pm, djhomeless <geoff...@bedl.am> wrote:
> I am working for a startup that is taking over the management of a number
> of existing YouTube Channels (I believe the term that is used is novate).
> While we can see Insight Reports via the YouTube CMS for all the assets in
> the channels, we cannot get the Insight token code (per the Google
> documentation) unless we authenticate with the channel account (as opposed
> to our CMS account which manages the channel). Unfortunately, not all our
> partners are able to share their credentials with us, but we definitely can
> see token code in the response object when we fire a test request via the
> API sandbox using a channel login. eg:
>
> http://gdata.youtube.com/demo/index.html
>
> I have also tried creating a developer key and using that in the request,
> but still the same response, NoLinkedYouTubeAccount.
>
> So, we can still browse and download individual Insight reports via the
> YouTube CMS, but the only we can get the token code in order to query the
> API is to inspect the HTTP traffic when downloading the report (for each
> individual video). Suffice it to say, the videos we are managing are in the
> 10s of thousands, so we'd really like to find a way to do this correctly.
>
> Any advice would be appreciated!
>
> Geoffrey
You received this message because you are subscribed to the Google Groups "YouTube APIs Developer Forum" group.
To view this discussion on the web visit https://groups.google.com/d/msg/youtube-api-gdata/-/s1ePMr_18woJ.
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