Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Documentation Review

    1. Methodology Documentation

      1. Forward and Reverse circulation/wiki/spaces/DPP/pages/2002354177

    2. Fleet Impression Changes

      1. “What has changed” and “Why it matters”

  2. Review User Workflows

    1. Systemwide/targeted/combined

...

  1. Draft transit executive summary

  2. Gather additional fleet measurement requirements

  3. Gather additional feedback on UX workflow

Meeting Notes:

Demand side. Is the explanation sufficient?

General trends.

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 , metro markets, etc. Wraps double counted. Pedestrian model

Markets by operator (footprint, product, etc).

User Workflows: mixing in roadside inventory

Highlighting inventory that is placed in area (Manhattan). Exposing route data by garage?

Geopath Spot ID level of detail. street/curb breakout. garage breakout.

Reporting: aggregate level of inventory sets/ package

Exposing routes data by garage?

Hybrid approach - intermediate level between market and inventory plan. Connect with developers to share expected final product.

Reach/Frequency in Inventory Plan available this week

Market Plan 25, 50, 100 weekly TRPs standard package sizes

R/F for transit and roadside being updated, transit alone will remain

Geopath IDs being included in rfps. How will these be provided?

...

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

  1. Review updated fleet impressions “What has changed” and “Why it matters”. (Task Force Members)

  2. Test out UX workflows (Task Force Members)

  3. Post list of available systems in staging (Geopath)

  4. Add thoughts on best practices for Geopath Spot IDs (Task Force Members)

  5. Inventory Plan reach and frequency for fleet packages (Geopath)