...
If the "uid" or stream name changes, there is something wrong with the implementation and more than one view is being counted for this single view sequence.
The above example is a generic one.
For the BARB TV Player project, you You should be seeing heartbeats sent out at regu-lar0regular internvals 0,3,10,20,30,40,50,60,120,180,.. seconds (or every 20 seconds, depending on your market's setting).
NOTE: There may be 1 or 2 seconds added to every heartbeat due to internal workings of the library.
...
- A counter with the analyzed requests. The screenshot example above contains a “12” in this box, indicating that “12” requests have been generated up to that point.
- Any messages generated by the 'validator'. The validator assesses specific TV Player Report project variables such as the library version being used, content ID, and the stream variable. The full list of items that are validated is held at the following link:BARB TVPR Project#Playermonitoringrequirements
The stream requests are split out on screen within the large bars. The screenshot shows these in red and yellow. The status of each section is colour coded to highlight specific warnings when something is incorrect:
...
The app can now be considered “ready” for the BARB TV Player Report your project!