This week we released Version 4.31. We’ve made the following changes and improvements:
- System warns users when dissociating creatives from live campaigns/line items
- Reporting now supports parent/child venue type relationships
- Search for venues by name or ID in targeting
- Support for screen counts in venue management and inventory tools
System warns users when dissociating creatives from live campaigns/line items
The system now alerts users when they attempt to dissociate creatives from actively delivering campaigns or line items. Once alerted, users can select to continue with the action or cancel out of it.
Reporting now supports parent/child venue type relationships
Some OOH venue types include nested options. For example, within “Transit” a user can target “Subways”, “Street Level”, etc. To make it easy to filter on nested venue types, now if you select a parent venue type in reporting (e.g. "Transit"), the selection automatically includes all child venue types associated with the parent (e.g. "Transit|Street Level", "Transit|Subways", etc.).
Search for venues by name or ID in targeting
For media owners that leverage direct ad serving, this improvement will facilitate easier venue search for targeting from the Orders tab.
With both venue name and venue ID available, media owners have the ability to pick which option works best for their use.
Support for screen counts in venue management and inventory tools
A single venue in Vistar’s system corresponds to a single player in the field. In some cases one player can control content for multiple synchronized screens. Following the latest release, media owners can now set screen counts for the venues in order to more accurately reflect the inventory that each player controls. Screen count can be set on the standard venue edit form.
Once screen counts are appropriately set, the Inventory Management tool will display the total number of screens that your proposals target in addition to the total number of venues. This information will be shareable with clients via the export on the shared map.