Comments (4)
To be honest - I don't believe we want this kind of repetition in the taxonomy. In this case, I would suggest that we probably want to maintain the current format, and ask for the "most specific" view, since I think in most cases either what we have will be a pharmacy chain/publisher where a few of their locations happen to be embedded, or a Big-Box retailer where a few of their screens happen to be a pharmacy.
I do think we could explore whether we either want to:
- Allow multiple selections for taxonomy (I suspect this is likely to create confusion and not necessarily to pubs interests, since blocking is a common reason for types)
- Perhaps maintain the taxonomy, but introduce a concept (either as part of this spec, or perhaps just directly in OpenRTB or wire protocols for "related categories" or "nearby POI" or something like that
@davidweinfeld would something like the proposal above address your use cases?
from venue-taxonomy.
While it's a thoughtful approach, I don't think the proposal above addresses our use cases. Nor do think that it effectively supports the most accurate level of venue identification.
We have two networks that have thousands of screens in the pharmacy sections of grocery and big box retail stores. Today, the pharmacy venue type sees less than 0.2% of all demand on one of programmatic DOOH's largest exchanges. Grocery stores, on the other hand, see in excess of 5% of all demand. Some of the reasons for this include a higher number of product SKUs, higher consumer spend, longer dwell times, and, most definitely, higher venue traffic in grocery stores.
As such, there's a lot of demand impact when reclassifying a venue type. With that in mind, I think the section of a retail store is preferential (Retail Grocery.Aisle.Pharmacy) and much more accurate than calling it Retail.Pharmacy. This is based on the profile of the audience, buyer behavior, and advertiser expectations of the primary venue type.
from venue-taxonomy.
Based on discussion with expert group - this will not be added to the taxonomy in 1.2 - recommend we consider fleshing out some of the cases more thoroughly.
e.g. I think the argument around current spend patterns is a difficult one - the taxonomy should be focused on accurately describing the activities and behaviors happening at a location - and the market should determine it's valuation of different areas.
In the interim, for in-grocery pharmacy sections, I think it would be reasonable to consider (working with any partners you're working with) categorizing them as grocery stores - since if there are multiple potential classifications, any/all of them are probably valid - and seeing if in a future revision of the spec or related specs we might want to consider something more prescriptive
from venue-taxonomy.
marking as closed for 1.2 - but open to creating a separate followup to explore in more detail
from venue-taxonomy.
Related Issues (20)
- Add: Retail > Malls > Normalize Mall Grandchildren HOT 1
- Add: Transit ->Travel Plaza HOT 4
- Add: Transit -> EV Charging Stations HOT 6
- Add: Point of Care > Hospitals HOT 3
- Remove deprecated string formats HOT 1
- Align wire protocol with OpenRTB 2.6-202211 HOT 1
- Add "Retail" > "Big Box"
- Add "Retail" > "Discount Store" HOT 1
- Transit_Airport_Parking Space
- Adding Window Shops as a GC category HOT 2
- Health and Beauty_Fitness Studios
- Add: "Health and Beauty" > "Indoor Sports Hall"
- Add: Office Buildings_Coworking Space
- Introduce a 0 in front of parent types HOT 3
- Add: "Retail" > "Tobacco Shop" HOT 1
- Add: Shooting Range as a Category HOT 1
- Add "Retail" > "Laundromats"
- Add "Transit" > "Trams"
- Add "Transit" > "Train Stations" > "Escalators"
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from venue-taxonomy.