How To Measure Streaming On Polandowan Internet

Transcription

1 Warsaw, December 12, 2011 Polish Internet Research Al. Jerozolimskie 65/79, lok Warsaw, Poland LETTER OF INQUIRY Executing the agreement signed by co-owners of Polish Internet Research Ltd (Polskie Badania Internetu) we are sending the letter of inquiry for research of streaming consumption on Polish Internet. Please prepare your offer according to the points listed below: I. Subject of the letter of inquiry II. Requirements III. Offer form requirements IV. Deadline for the submission and offer expiry date V. Additional requirements VI. Postal address VII. Additional information With kind regards Andrzej Garapich President / CEO

2 Ad I. Subject of the letter of inquiry Research of streaming consumption on Polish Internet Ad II. Requirements for the measurement and analysis of streaming consumption on Polish Internet MAIN OBJECTIVES We require a system to measure user behavior when streaming audio and/or video content via any type of player, e.g.: RTMP protocol - Flash Player Flash HTTP streaming - Flash Player Apple HTTP streaming - QuickTime, ios, HTML5, Set-Top Box Microsoft Smooth Streaming (HTTP) - Silverlight Player, Windows Phone 7, Set-Top Box RTSP protocol - Quicktime, 3GP players for mobiles, Set-Top Box, Windows Media Player MMS protocol - Windows Media Player The methodology should be based on User Side measurement. The resulting data must describe the real user consumption of all streaming content, both audio and video. In addition, all key events on the player must be logged by action, including: play, stop, pause, rewind, forward, resolution change, bitrate change and buffering. The methodology may be supported by Server Side measurement if necessary and if it provides greater accuracy. EVENTS FOR MEASUREMENT For the purpose of this document, a stream is defined as the sequential playing of video or audio content. It will have the following attributes: Event ID Category ID - multi-tree categorization common for whole market User ID Site ID - the Internet Site where the player is embedded; on that site the Page Views is being counted

3 Platform: PC, Mobile, Smart TV, etc. Player Service ID - the identifier of the service - owner of the video/audio content Date and Start Time of playing Start position in the audio/video content Length of viewing Stream type: audio/video Stream model: live/vod Event class: add/program/promo Geolocalization Broadcaster specific categorization The categorization process should be based on event levels. It needs to be common for the whole market and remain sufficiently flexible to allow for future changes in the market. The Research company must define and support the categorization, which should be clear for all services. The Company should propose a method of constant verification that each service is being properly categorized. DATA REQUIRED The final reports must include the following information: Reach - Number of unique users receiving the video/audio stream Impression - Number of contacts between the user and event (VOD or Live Channel) Number of streams Number of Sessions defined as a list of viewed streams when the break of viewing between them is less than a specified constant (such as 30 minutes) Time spent Average length of viewing weight by the length of stream Impression of completed event - number of contacts which meet the user defined condition (threshold of viewing) for the length of viewing, for example completed material is defined as 95% proportion between the viewed time and the material length Average Viewed Time per User Average Number of Sessions per User Average Impression Demographic Profile of Users REPORTS The final report will need to have a proposition of solution to make data compatible with Gemius Explorer, which currently provides Polish Internet survey data to the market. The Research Company

4 should also propose a method for integration of the streaming research results with the Megapanel survey data of standard traffic measurement for both internet sites and applications. This report format should also enable further analysis of the data in a separate analytical application, specifically to include the following: Online access with maximum 1 day delay in data publication Any resolution for time aggregation, e.g.: user-defined day part, days, weeks, months, etc. Should allow the flexible aggregation of data based on any attribute of stream (which can be aggregated), like category, stream type, model, etc. For such a set of streams all variables should be counted Should allow the flexible filtering of the analyzed streams based on any attribute Ad III. Offer form requirements Offer in written form in Polish or English languages, signed by proxies. Ad IV. Deadline for the submission: Jan 10-th, Offer expiry date: 90 days Ad V. Additional offer requirements Offer has to consists: 1. Methodology description 2. Schedule for the implementation 3. Price 4. List of references for chosen methodology

5 Ad VI. Postal address Al. Jerozolimskie 65/79, lok Warsaw, Poland Ad VII. Additional information Questions concerning research process and methodology please send to: