A. Agenda
Action Items Review
Documentation Review
Methodology Documentation
Fleet Impression Changes
...
2. Methodology Documentation
b. Forward and Reverse circulation
3. Additional 3rd Party Fleet Measurement for Observed
a. StreetMetrics as comparison
Review User Workflows
...
Systemwide/targeted/combined
...
Transit Release Roadmap
...
Review of UX in Staging
Direction on using new UX in Staging
New Features
Ability to query inventory by transit system
...
Display total quantity of frames (e.g. Kings) by garage
...
c. Walk through video
2. Development
...
Known Bugs
Inventory Plan RF not displaying
Market Plan allocation (next week)
Under Development
Roadside RF dependency for plans with transit AND roadside (TBD)
Important Dates
3/21 release of new systems into staging
3/30 cutoff for 4/4 release to production
Next Steps:
Draft transit executive summary
Gather additional fleet measurement requirements
Gather additional feedback on UX workflow
Meeting Notes
Impressions Changes
For the buy side, is the explanation of the impressions enough? The documentation of the auditing process and methodology is sufficient though additional questions will be garnered.
Are there general trends or movements in impressions? E.g. Do kings deliver fewer impressions or how are metro markets affected?
It was noted that summarizing a datapoint into an overall outcome could be misleading. Perhaps a market-by-market analysis would be more useful. Each system has its own footprint within the market and a portfolio of inventory.
User workflows
Campaigns will commonly mix in additional media classes. Inventory could also be highlighted by its coverage. For example, showing the inventory which moves through Manhattan. While the ability to filter garages within a specific county exists, we are considering additional solutions.
Geopath Spot IDs
The Geopath spot IDs contain a very granular level of detail, they provide a garage and streetside/curbside breakout.
This may be resolved with the way we can report the data. An aggregate level of inventory sets would summarize the underlying data into a more consumable package.
We could also potentially expose routes by garage data or explore a hybrid approach with the development team.
Because there are some questions around how the Geopath IDs will be used, we will document best practices.
Staging
The reach and frequency in the Inventory Plan will be available this week. We are keeping in mind that r/f for roadside will be updated in the immediate future and any campaigns running both media classes would be affected.
For standard package sizes, we can use TRP levels of 25/50/100.
Action Items
Review updated fleet impressions “What has changed” and “Why it matters”. (Task Force Members)
Test out UX workflows (Task Force Members)
Post list of available systems in staging (Geopath)
Add thoughts on best practices for Geopath Spot IDs (Task Force Members)
Inventory Plan reach and frequency for fleet packages (Geopath)