Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Agenda

Added Items

For UX, can we select just an Operator Media Name instead of having to select Media Class and then an Operator Media Name (Dynamic Filtering)

Data Standardization: the same product under different operator media names. We’ll be modifying operator media names for consistency

Action Items Review

  1. Review transit systems for approval from staging into production (Task Force)

    1. Review the impressions for individual transit systems, approve measures

  2. Test Market Plan to create campaigns for multiple media classes (Task Force)

    1. Reach and frequency will be updated

  3. Review Market Plan by Place and Placement Type via API (Geopath)

    1. Sample measure return posted in Workspace - Market Plan

    2. Calculations reviewed for number of units required to meet goal

  4. Process Tier 3 inventory for base impressions (Geopath)

    1. Routes assigned to garages, media data updates being finalized

    2. Timeline for Tier 3

Notes

 

Added Items

For the UX, can the Media Class specify a filtered list of Operator Media Names? This is something our dev team is aware of and would require some overarching updates to the query process, not only affecting transit. We’ll be able to report updates and share wireframes as they become available. 

Data Standardization: the same product will appear under slightly different operator media names.  We’ll be able to make edits to standardize the media without changing the given word.  For example, we wouldn’t change an operator’s submission of super king to kong but we would update aspects such as singularity (kings vs. king), prepositions (with vs w/), and casing (lower vs. proper).  We’ll also include some additional written guidelines when submitting inventory. 

 

Action Items Review

System Status

We were able to note that the System Status page has been updated with respect to Tier 3.  It was recommended to start looking at an individual system for approval. 

 

Market Plan

Reach and Frequency will be updated for across media classes.  Impressions and TRPs are a good point of review though please note that R/F will be changing. 

We reviewed a Market Plan by Place Name sample output via API which is the data that will populate the updated Market Plan.  Certain Market Plan inputs such as Audience, Market, Media, Plan Period and Delivery Goals were specified.  The updated Market Plan allows us to query by Place name as well.  Based on the garage, we would require a different number of spots to meet the example goal of 40 TRPs.    

A second post in Confluence walked through how the calculations are made to arrive at 36 spots.  We broke down the number to a single spot over one week.  The spot represented the driver and passenger side impressions. 

 

Tier 3 Impressions

Tier 3 base impressions will be available by the end of the week.  Those base impressions will then make their way into staging through Friday, 5/6. 

 

Audiences

Certain campaigns were not populating.  Can we specify which audiences should be populating with measures?

Action Items

  1. Review transit systems for approval from staging into production.  Review the TRPs and impressions for individual transit systems, approve measures (Task Force)

  2. Review Market Plan by Place and Placement Type via API.  Apply max frames limits by garage for campaigns. (Geopath)

  3. List out all audiences which should be producing measures in staging, ensure they are populating correctly (Geopath)

  4. Process Tier 3 impressions, upload into Staging (Geopath)

  • No labels