Cisco Cisco StadiumVision Mobile Reporter Manual De Mantenimiento
© 2011 Cisco Systems, Inc. All rights reserved. This document is Cisco Internal Information.
Page 11 of 28
Before you generate a proof of play report, consider the following:
•
If the name of the content contains a space, proof of play will not
recognize it.
•
Proof of play records are not available until the script completes.
•
While the proof of play report is processing, there is a delay between the
end of an event and the availability of the reports in the Proof of Play
screen. Click the refresh button before generating and viewing a proof of
play report to be sure the latest report status is displayed.
screen. Click the refresh button before generating and viewing a proof of
play report to be sure the latest report status is displayed.
•
Depending upon the amount of data you have in the script, it may take
from 10 seconds to several minutes to generate the report.
•
The last event state is traditionally used to turn off the displays in the
venue. Because of this, the last state does not offer proof of play data.
•
Content placed in the first event state may not appear in proof of play
records.
•
For zero-duration non-video items in a playlist, the proof of play record
will show the airtime when the item started to play and the Duration as 0
(zero).
(zero).
•
StadiumVision Director is unable to generate proof of play for an event if
proof of play is turned on for a Dynamic Menu Board playlist. Therefore,
before generating a proof of play report, be sure to turn off proof of play
for all Dynamic Menu Board playlists.
before generating a proof of play report, be sure to turn off proof of play
for all Dynamic Menu Board playlists.
•
Proof of play reports are not generated for playlists that contain less than
three items. If proof of play is required, create playlists that contain three
or more items.
or more items.
•
Custom screen templates do not support proof of play.
•
For proof of play, you can have only one region with an ad playlist.
Best Practices for Naming and Tagging Content to Generate
Proof of Play Reports
Proof of Play Reports
Use of a consistent naming strategy makes it easier to generate and manage
reports. For example, prefixing region 2 content file names with “R2” (e.g.,
“R2_filename.jpg”) allows you to generate reports on region 2 content since
filters can be applied to look for “R2” at the head of the string. Other types of
content should have unique identifiers like “FS” for full screen content and so
on.
reports. For example, prefixing region 2 content file names with “R2” (e.g.,
“R2_filename.jpg”) allows you to generate reports on region 2 content since
filters can be applied to look for “R2” at the head of the string. Other types of
content should have unique identifiers like “FS” for full screen content and so
on.
Additionally, associating proof of play tags to content provides excellent
metrics for reporting and filtering. Tag names are free form so they can
reflect an advertiser account number, campaign identifier, or other reporting
metric. These tags will appear in the KORE CSV file.
metrics for reporting and filtering. Tag names are free form so they can
reflect an advertiser account number, campaign identifier, or other reporting
metric. These tags will appear in the KORE CSV file.