General Info
What should I be tracking?
In the first iteration of TVPR, your implementation should track only programme content and no advertisements. You should call the library's track-Method only once per stream.
What metadata must I provide to the library?
See Player monitoring requirements. Our library needs to receive mandatory information on the current position of the stream in seconds, a stream identifier (unique BARB Content ID and/or name of the stream) and information about the stream duration if the stream is VOD not live (so-called duration of the stream).
How do identify my programm content?
See Player monitoring requirements. For on-demand you must provide the BARB standard Content ID. For live, this is still being revised because it might not always be possible to supply a standard Content ID in a live context.
What should I do if duration (media length) is not available at the start of my stream?
We have seen cases where duration of a stream is not available to the library until after 10-20 seconds. This is not a problem.
When should I call Start/Stop?
You should call Start (so-called "track-Method") only once at the beginning of a stream.
You should call Stop only at the end of a stream, to stop the measurement.
Should I call Pause/Resume?
There is no functionality to "pause" or "resume" the measurement. The Kantar Spring library "lives and dies" together with the content being played.
How and when is data transmitted?
All transmission is over http;
Get requests, not POST;
Flushed on event
What happens during clock change (DST changeover)?
All measurement is done in GMT. Timezones are handled in post-processing.
Content and Advertising
How do I manage pre- and mid-rolls?
In most cases, it is enough to connect the Kantar library to only the content object in your player, and not connect it to advertisement objects. The library will automatically keep track of the content when it is being paused for mid-rolls. You should not try to micro-manage what the library is doing.
Mobile App Streaming
What happens if my app is sent to the background by the user?
A Stop event is called when the app goes to background causing a new measurement session to start when user returns and resumes.