This page is work in progress. Any critical changes to the page will be communicated directly by Norway. |
For more information on the current project status and schedule, please contact Kantar Norway, Oslo.
The Norwegian project team is led by Kantar in Oslo. Our technology specialists from Kantar Media Spring, Germany, will assist with your technical queries as you begin and progress each player/platform implementation.
Before you start your implementation we will discuss with you and your teams which of our libraries you should use and be available to answer queries arising from your review of our documentation and testing framework.
We will be directly involved in the sign-off process for your implementation, undertaking a review of the data we receive from your implementation once on a staging environment.
Please contact us at the following address:
Please contact our Norwegian Project Development Director Christian Thune-Larsen.
Please contact our Norwegian Digital Project Manager Lars Nitteberg.
Please contact our Norwegian Digital Project Manager Lars Nitteberg and DE Technical Project Support Customer Support.
| Function | |
Associate Director Client Services | christian.thune-larsen@kantar.com | |
Digital Project Manager | lars.nitteberg@kantar.com | |
| ||
Customer Support | Am Saaraltarm 1 |
Audience Tagging Instructions (English Version)
Important: |
Important: |
NOTE: First unified Java Script release for browser, TVML/TVJS (Apple TV), TAL (Smart-TV) and WebMAF (Playstation)
For the web environment or other JavaScript capable environments
(not natively supported)
For desktop player implementations, you will need to observe the log stream data and verify the content of the heartbeats.
You do this by running a simple analysis of the http-requests sent from and to a browser whilst your webplayer is operating.
There are NO warnings or error messages produced using this method, it is a simple tracking of the HTTP-requests sent to the Kantar Media Spring measurement systems.
You can observe an example of a correct webplayer implementation using an HTTP-analyser such as the "developer tools" in Chrome/Internet Explorer or "HttpFox" plugin in Firefox.
|
This section briefly explains what the heartbeats sent from the libraries should look like. A concrete example of a viewing session is used.
Please use the record layout descriptions below for reference.
Variable | Description |
---|---|
counting domain | "tns-cs.net" = Norwegian counting domain e.g. “sitename” = “example" see Norwegian Internet Project#First Request Statement |
pl | player = own player name (set by the broadcaster) |
plv | player version = own player version (set by the broadcaster) |
sx | width of the stream window |
sy | height of the stream window |
stream | stream name (set by the broadcaster) |
cq | content-ID = broadcaster's content ID |
uid | unique Id of the view sequence |
pst | play state = list of viewing intervals on the stream |
dur | stream length in seconds (set by the broadcaster) |
vt | view time in seconds (time of visual contact with the stream) |
The actual record output should look similar to below:
First play state: 0+0+mbeswh
http://example.tns-cs.net/j0=,,,pl=jwplayer+plv=version1+sx=640+sy=517;+,stream=od+cq=123456789+uid=3f3tv5p+pst=,,0+0+mbeswh;+,1+1+mbeswj;;+dur=1501+vt=2;;; |
The output records should look similar to the records below, note the time of the “heartbeat” records = play states records at 21, 41, 61,.... seconds
http://example.tns-cs.net/j0=,,,pl=jwplayer+plv=version1+sx=640+sy=517;+,stream=od+cq=123456789+uid=3f3tv5p+pst=,,0+0+mbeswh;+,1+21+mbeswj;;+dur=1501+vt=22;;; http://example.tns-cs.net/j0=,,,pl=jwplayer+plv=version1+sx=640+sy=517;+,stream=od+cq=123456789+uid=3f3tv5p+pst=,,0+0+mbeswh;+,1+41+mbeswj;;+dur=1501+vt=42;;; http://example.tns-cs.net/j0=,,,pl=jwplayer+plv=version1+sx=640+sy=517;+,stream=od+cq=123456789+uid=3f3tv5p+pst=,,0+0+mbeswh;+,1+61+mbeswj;;+dur=1501+vt=62;;; http://example.tns-cs.net/j0=,,,pl=jwplayer+plv=version1+sx=640+sy=517;+,stream=od+cq=123456789+uid=3f3tv5p+pst=,,0+0+mbeswh;+,1+83+mbeswj;;+dur=1501+vt=84;;; http://example.tns-cs.net/j0=,,,pl=jwplayer+plv=version1+sx=640+sy=517;+,stream=od+cq=123456789+uid=3f3tv5p+pst=,,0+0+mbeswh;+,1+105+mbeswj;;+dur=1501+vt=106;;; |
Last play state: 1+121+mbeswj = 120 sec playtime.
http://example.tns-cs.net/j0=,,,pl=jwplayer+plv=version1+sx=640+sy=517;+,stream=od+uid=3f3tv5p+pst=,,0+0+mbeswh;+,1+121+mbeswj;;+dur=1501+vt=124;;; |
There may be 1 or 2 seconds added to every heartbeat due to internal workings of the library. |
Mobile Tagging Instructions (English Version)
Important: |
Mobile App Sensor Documentation (English Version)
Important: The variable <application> may NOT be selected and will be notified by Norway individually. |