Zum Inhalt

Stammdaten IDOOH

Hier wird das Format und die Interpretation der Stammdaten beschrieben. Die hier angezeigten Informationen werden direkt aus diesen Stammdaten erzeugt:

  • Stammdaten (gekürzt für Doku): IDOOH Objekt- und Screenliste 2025-07-14 Freeze_v26 für Comsulting-1000.xlsx
  • Doku: IDOOH_Standards_Stammdaten für ISBA und Comsulting 2025-06-21.xlsx

Belegungseinheiten

Dies sind die Einheiten, die ausgewertet werden können. Wir benötigen für den Import nur folgende Felder aus der Doku:

Hauptfelder

Data Field Format comma-separated lists allowed Status Description
bid text no required Global unique ID for booking unit issued by IDOOH. Must be specified by publisher for matching to historical data. Publisher can obtain bid from IDOOH DMP (in the future).
parent_bid text no optional Can be used to cumulate smaller booking units into larger booking units, e.g.:
- group several networks into one overarching sales unit (e.g. Gesamtnetzwerk Fahrgastfernsehen)
- group several cities (e.g. "Top 15 cities")
Only one parent_bid allowed (no comma-separated lists).
bname text no required Name of booking unit as given by the publisher (e.g. "Airport Touchpoint Düsseldorf Sicherheitsbereich").
publisher_id integer no required Unique ID for publisher issued by IDOOH. In the case of secondary marketing, the object and screen lists are maintained by the primary marketer and made available to the secondary marketer (read-only rights). the secondary marketer can use the object_ids and screens_ids for its booking units.
bid_status text no required Allowed values:
active = bid is active
inactive = bid is temporarily inactive
retired = bid is removed/discontinued
pending = bid is due to be used / not yet active
reserved = bid has not yet been used but will be in the future
Contact values are calculated by market research institute for all screens except for "retired" screens (notice: if bids contain "retired" objects or screens, then contacts for these "retired" objects and screens will be set to zero; compare to documentation of "objects" and "screens" tables).
For active bids, only active screens will be counted, i.e. inactive and pensing screens will not be included into an active bid.
Only active bids will be calculated by market research institute and subsequently displayed in media planning tool; all other bids will be ignored.
Reserved bids are empty bids that haven't been used yet (but will be in the future) and are reserved or one specific publisher.
Status flag will be displayed in media planning tool.
publication boolean no required determines whether booking unit will be exported to media planning tool "mediMACH" (TRUE) or not (FALSE)
net_id integer no optional Unique ID for DOOH network issued by IDOOH. Only one net_id allowed (no comma-separated lists). To generate bids containing more than one net_id, use matching tables.
geo_id integer yes optional hierarchical structure for geospatial grouping of screens and objects in booking unit:
- leave empty to designate a booking unit encompassing entire network
- provide first two digits of AGS to designate booking unit encompassing all screens in one state (Bundesland)
- provide first three digits of AGS to designate booking unit encompassing all screens in one government district (Regierungsbezirk)
- provide first five digits of AGS to designate booking unit encompassing all screens in one county (Kreis/Landkreis)
- provide complete AGS to designate booking unit encompassing all screens in one municipality (Gemeinde)
may be combined with "venue_id" and "city_size" filters;
comma-separated lists allowed.
object_id integer yes optional one object_id (for generating a booking unit of only one object)
is_net boolean no provided by IDOOH TRUE if booking units comprises an entire net (i.e. contains all screen with the same net_id); FALSE otherwise

Hinweis zu object_id

Die Spalte object_id wird lediglich zu Bestimmung des Geo-Levels benötigt.

Info - Fehlende Spalte geo_hierarchy in Stammdaten Standards

Fehlende Spalte geo_hierarchy in Stammdaten Standards

In der aktuellen Version der Stammdaten für das Herbstupdate (IDOOH Objekt- und Screenliste 2025-07-14 Freeze_v24 für Comsulting) wurde eine neue Spalte geo_hierarchy eingeführt, die für die Berechnung des Geo-Levels benötigt wird. Für diese Version wurden keine neuen Stammdaten-Standards mitgeliefert, daher ist die Spalte in der Liste der Hauptfelder noch nicht enthalten.

Beispiel

Die ersten 5 Zeilen aus den Stammdaten

bid parent_bid bname publisher_id bid_status publication net_id geo_id object_id geo_hierarchy
50000001 Airport InfoNet Stuttgart - Gesamt 22 active True 78
50000002 Airport InfoNet Stuttgart - Abflug 22 active True 78
50000003 Airport InfoNet Stuttgart - Ankunft 22 active True 78
50000004 Airport InfoNet Stuttgart - Business 22 active True 78
50000005 Airport InfoNet Stuttgart - Touristik 22 active True 78

Filter

Screenfilter

Die Screenfilter müssen bei der Weiterverarbeitung der Stammdaten nicht berücksichtigt werden, da die Screens von Belegungseinheiten von IDOOH in den Spalten list_screens_active_[1-4] bereitgestellt werden. Aus der Änderung vom 6.2.2025:

Screens einer BE

Die Anbieter wählen die Screens über Filter oder Matching Tables aus. Das IDOOH wertet diese Vorgaben aus und stellt fertig ausgezählte Listen der Objekte und Screens in den „grauen Spalten“ rechts in der BE Tabelle (in der o.g. Stammdatentabelle) zur Verfügung. ISBA und Comsulting können auf diese kommaseparierten Listen zugreifen und müssen nicht selbst Filter und Matching Tables auswerten. Achtung: Die aktiven Screens verteilen sich auf bis zu vier verschiedene Spalten, da eine Excel-Zelle nur 32.000 Zeichen aufnehmen kann.

Spotkonfigurationen

Allgemein

Die Zuordnung von Spotkonfigurationen in den Stammdaten ist wie folgt beschrieben:

  • Filters for time selection, spot length and playout frequency:
  • If any one of these four data fields is left empty, then the network default values are used for the empty data field(s) (see "networks" table), while for non-empty data fields the values specified in the bid are used.
  • If comma separated lists are specified in either filter, then sub-bids (one for each item specified) are generated by the market research institute. This way, sub-bids for e.g. all dayparts for all weekdays can be generated with just one line in the booking unit list.
  • That means: comma-separated lists are interpreted as specifying separate sub-bids.

Erläuterung Felder

ID Typ comma-separated list allowed Status Description
daypart_id text yes optional ID for times of day according to table "daypart";
comma-separated lists allowed;
if left empty or set to "default" or "DEFAULT", then the network default ("daypart_id_network" in table "networks") is used
weekday_id integer yes optional ID for day of week according to table "day of week";
comma-separated lists allowed;
if left empty or set to "default" or "DEFAULT", then the network default ("weekday_id_network" in table "networks") is used
spot_length integer yes optional spot lengths in seconds;
comma-separated lists allowed;
if left empty or set to "default" or "DEFAULT", then the network default ("spot_length" in table "networks") is used
playouts_per_hour decimal yes optional number of playouts per hour;
comma-separated lists allowed;
if left empty or set to "default" or "DEFAULT", then the network default ("playouts_list" in table "networks") is used

Preise

Allgemein

Die Zuordnung von Preisen in den Stammdaten ist wie folgt beschrieben:

  • Price can be specified as:
    • fixed price per booking unit (fields "price …"
    • CPM per booking unit (fields "CPM …" (price will be calculated with spot contacts (WMK) of this booking unit as specified by market reaesarch institute calculation fpr mediMACH)
    • reference to pricing table
  • Either "price..." fields "or "cpm..." fields or pricing table can be used.
  • Using one of the groups of fields is required. The only exception to this rule are parent bids: The prices for parent_bids are calculated as the sum of the prices of the child bids (which may need to be calculated from the CPM and the contacts of each child bid)

Erläuterung Filter

ID Typ comma-separated list allowed Status Description
price_q123 currency no optional (if empty, then cpm_q123/cpm_q4 or pricing_table_id needs to be supplied) Cost für booking unit in Q1-3 and Q4
Calculation of prices of parent_bids from prices/cpms of child_bids:
- Multiplication of the Child-BE CPMs with their respective contacts / 1000
- Addition of these products = parent_bid
- Addition of the prices of these products = price of parent_bid
- Calculated CPM of the parent_bid = price of the parent_bid divided by the (total contacts/1000)
price_q4 currency no optional
cpm_q123 currency no optional CPM für booking unit in Q1-3
cpm_q4 currency no optional CPM für booking unit in Q4
pricing_table_id integer no optional ID of pricing table containing CPMs for all dayparts of a week

Vermarkter

Die Angaben zu den Vermarktern sind nicht in der Dokumentation (IDOOH_Standards_Stammdaten für ISBA und Comsulting 2025-06-21.xlsx) beschrieben.

Sie finden sich in den Stammdaten unter dem Tab "Publisher":

publisher_id publisher_name publisher_id_faw
1 Brand Community Network (BCN)
2 echion Corporate Communication AG 954.0
3 Executive Channel Deutschland GmbH 674.0
4 Edgar Ambient Media Group GmbH 13.0
5 El Cartel Media
6 eisbach.media 668.0
7 HYGH AG
8 inovisco Mobile Media GmbH 449.0
9 ISM Intelligent Signage for Media GmbH
10 mcR&D

(erste 10 Einträge)

Spalten

  • publisher_id => ID, die zur Referenzierung innerhalb der Stammdaten genutzt wird
  • publisher_name => Name des Publishers
  • publisher_id_faw => Vermutlich ID des Publishers beim FAW

Netze

Hauptfelder

Data Field Format comma-separated lists allowed Status Description
net_id integer no required Unique ID for DOOH network issued by IDOOH.
parent_net_id integer no optional Can be used to cumulate networks or subnetworks into parent networks.
publisher_id integer no required Unique ID for publisher issued by IDOOH.
venue_id_network text no required IDOOH venue taxonomy ID (refer to https://idooh.media/standards/).
net_name text no required name of network assigned by publisher; must be identical to network name in mediaplanning tool (mediMACH)
spot_length_list integer yes required standard spot length in seconds (usually 10 seconds); used by market research institute for calculation of contacts and reach together with playouts/hr (base frequency); ; may contain comma-separated lists; this is used as the "network default" for booking units in which the data field "spot_length" is not specified.
playouts/hr_list decimal yes required determines the number of playouts per hour as allowed in this network; may contain comma-separated lists; this is used as the "network default" for booking units in which the data field "playouts_per_hour" is not specified.
Base frequency (i.e. standard number of playouts/hr as specified in media data and plannning tools) should be the first entry.
weekday_id_network integer yes required determines whether screens in network can be booked on individual days of week, entire week or parts of week (e.g. Mo-Fr); refer to table "weekday_id"; may contain comma-separated lists; this is used as the "network default" for booking units in which the data field "weekday_id" is not specified.
daypart_id_network text yes required determines during which hours of day (during hours of operation) screens in network can be booked (e.g. 1-hour time slots, 3-hour time slots, entire day); refer to table "daypart_id"; may contain comma-separated lists; this is used as the "network default" for booking units in which the data field "daypart_id" is not specified.
network_status text no required network_status = active if network is active
network_status = inactive if network is (temporarily) inactive (e.g. during negotiations about continuation of a sales mandate)
network_status = pending if network is not yet active (e.g. during initial rollout)
network_status = retired if network is permanently discontinued
Only active networks will be considered by market research institute; all others will be ignored for contact calculation.

Beispiel

Die ersten 5 Zeilen aus den Stammdaten

net_id parent_net_id publisher_id venue_id_network net_name playouts/hr (standard) spot length (standard) weekday (standard) daypart (standard) spot length_list
1 4 7.4.2 Public Video Fitness 12 10 10 AX 10
2 6 1.1 Airboards Köln 30 10 10 AX 10
3 6 1.1 Airboards Paderborn 30 10 10 AX 10
4 25 1.1 Airport Touchpoint Classic Gesamt 20 10 10 AX 10
64 4.0 25 1.1 Airport Touchpoint Düsseldorf Sicherheitsbereich 20 10 10 AX 10

Weitere Felder

Ausspielungszeiten

Es gibt noch weitere Spalten, die sich auf die Ausspielungszeiten für einzelne Wochentage beziehen:

None

Data Field
op_hrs_mon_start
op_hrs_tue_start
op_hrs_wed_start
op_hrs_thu_start
op_hrs_fri_start
op_hrs_sat_start
op_hrs_sun_start
op_hrs_mon_end
op_hrs_tue_end
op_hrs_wed_end
op_hrs_thu_end
op_hrs_fri_end
op_hrs_sat_end
op_hrs_sun_end
Erläuterung

Hours of operation for each weekday (Monday-Sunday) for entire network.

  • Hours of operation for each weekday (Monday-Sunday) for entire network.
  • Hours of operation for individual objects can be supplied in "objects" table.
  • If hours of operation for an individual objects table are supplied, they override the opening hours in the "networks" table (for that particular location only).
  • Hours of operation are the times of day that advertising is sold on the screens (screens and/or players may e.g. be running 24/7, but only the hours between 6am and 23pm may be actually sold - these are the hours of operation).
  • Only full hours should be specified (e.g. "8:00-19:00" or 11:00-23:00"). If an quarter or half hour are specified, the whole hour is interpreted as open. Example: 7:15 - 12:30: All hours from 7:00 to 12:59 are interpreted as open (i.e. 6 hours).
  • If the end time is midnight > "23:59" should be specified.
  • For networks not operating on sundays (or saturdays) > "23:59" should be specified as start time AND end time.
  • If hours of operation are neither specified on the network level nor on the object level, then this will be interpreted as 247/ hours of operations (i.e. 168 hours per week).

Von diesen gibt es insgesamt 3 Sets.

Touchpoints

Und dann sind die Netze noch mit Touchpoints verbunden.

Data Field Status Description
has_off_hours generated by IDOOH TRUE if hour profiles for objects in this network have off hours (i.e. opening hours of object during which screens are switched off, e.g. in train stations) cut out of hour profile. In this case sum of percentage values over the entire week doesn't add up to 100% (in order to eliminate site_frequencies in off hours from contact calculation).
FALSE if object has no off hours, i.e. site_frequencies are provided for operting hours of screens only.

Screens

Letztendlich setzen sich alle Belegungseinheiten aus Screens zusammen, die in Objekten (Gebäuden) stehen.

Felder

Data Field Status Description
screen_id required Global unique ID for screen issued by IDOOH. Must be specified by publisher for matching to historical data. Publisher can obtain screen_id from IDOOH DMP (in the future). "0" for newly installed screens, meaning IDOOH has to issue a new screen_id.
net_id required Unique ID for DOOH network issued by IDOOH. Screen can only belong to one network = no comma-separated lists allowed.
object_id required Link to object table
object_id_publisher optional Link to object table via publisher's object_id. Used for new screens in new objects where no IDOOH object_id has been assigned yet in order to match new screens to new objects.
screen_name_publisher required Name of object as given by the publisher (e.g. "Stele Eingangsbereich links"); max. 256 characters.
screen_id_publisher required Unique ID for screen issued by publisher. Must be unique in the sense that there may be no doubles and no re-using of old IDs for new screens.
player_id_publisher optional Unique ID for player issued by publisher. Must be unique in the sense that there may be no doubles and no re-using of old IDs for new players. Player IDs allow grouping of screens by player.
pos_x optional Geo-coordinates (WGS84) (long) of individual screen as located in the object
pos_y optional Geo-coordinates (WGS84) (lat) of individual screen as located in the object
pos_z optional floor number: 0 = ground floor, 1 = first floor, -1 = first basement floor, etc.
venue_id_screen optional IDOOH venue taxonomy ID (refer to https://idooh.media/standards/): venue_id_screen may be different from venue_id_object (e.g. airport as an object vs. screens in the arrival vs. departure areas of an airport). If no venue_id_screen is specified, then venue_id is inherited from venue_id_object
venue_id_tag_screen optional IDOOH venue taxonomy double-tag for screen (refer to https://idooh.media/standards/)
zone required Zone type name for contact calculation (i.e. market research). For most DOOH touchpoints venue_id_screen and zone will be identical (i.e. supermarkets: entrance, cash_out, ..). Zones in shopping malls, universities, train stations and airport may be different from venue_id_screen (see table "zones" and chapter 6 of "IDOOH Standards Stammdaten": https://idooh.media/download/IDOOH_Standards_Stammdaten.pdf).
zone_id required Unique ID for each zone type (see tables "zones")
edge optional "zone" in train station; derived from "Knoten-/Kantenmodell" of train stations (see chapter 7 of "IDOOH Standards Stammdaten": https://idooh.media/download/IDOOH_Standards_Stammdaten.pdf); can carry the numbers of up to three edges per train station separated by commas (e.g. "1, 4, 7").
screen_status required allowed values:
active = screen is live
inactive = screen is temporarily inactive
retired = screen is removed/discontinued
pending = screen is due to be installed / not yet active
Contact values are calculated by market research institute for all screens except for "retired" screens.
Status flag will be displayed in media planning tool.
screen_valid_since optional Validity period for screen. If no "screen_valid_since" is specified, the start of the validity period of the market research data set - e.g. in the media planning tool mediMACH - is used as a default (e.g. start of quarter).
screen_valid_till optional
screen_inactive_from optional validity period for temporary inactivity of screen (e.g. closures of POI/object)
screen_inactive_till optional
screen_type_key required Code for screen types issued by IDOOH: Screens are classed into horizontal and vertical screens and into large, medium, and small screens (needed for calculation of contacts per screen):
refer to table "screen_types"
past_screen_id required (if past_screen_id exists) predecessor ID to current screen_id (e.g. after change of publisher for that screen resulting in new screen_id (see accompanying document). Past_screen_ids enable historic tracking of individual objects across changes in screen_ids.
animation_enabled optional values (default value = "video"):
video = full video allowed
animation = only some animation allowed
cinemagram = slight animation for individual elements only in static picture allowed
static = static pictures only
Statuanimation_enabled flag will be displayed in media planning tool.
picture_link optional until end of 2024; required in 2025 Link to picture of screen on internal or external server. No generic pictures allowed; pictures of each individual screen required (from 2025 onward). All file formats allowed.
aspect_ratio optional Aspect ratio of screen; possible values: "16:9", "9:16", "4:3", "16:10", (other non-standard values permitted)
screen_id_publisher_2 optional Alternative unique ID for screen issued by publisher. Must be unique in the sense that there may be no doubles and no re-using of old IDs for new screens.
share_of_frequency optional Only needed for screens in train stations without "Knoten-/Kantenmodell" (see above: "edge"): Percentage of site_frequency passing by that screen.
zone_info required for touchpoints where "needs_zone_info" in table "zones" is TRUE; optional for all other touchpoints Airports & malls: individual zone code for each zone in each specific airport or mall as designated by publisher in corresponding site map.
Subway & suburban train station (optional): Lines of transport connected to this screen, e.g. subway lines (including direction) for screens on a specific platform
Highway rest areas (optional): highway number (including direction) for screens in rest areas.
screen_frequency optional frequency (i.e. number of customers, passengers or visits) per week for this screen as supplied by external measurements:
for some individual screens individual frequency measurements may have been conducted; these take precedence over site_frequency and onsite interviews.
"screen_frequency" represents "site_frequency * p * n"
net_zone provided by IDOOH concatenation of net_id and zone_id (used for matching of onsite interviews to individual zones (by network)
net_zone_source provided by IDOOH zone_id of onsite interviews (from table "F2F für ISBA") to be used for p, n, k, DT parameters for this net_zone / net_zone_screen
site_frequency_E14+ provided by IDOOH site_frequency (see above) reduced by children under the age of 14 to yield only people of age 14 years and older.
p P&PS 3.0 provided by IDOOH p-value (share of site_frequency_E14+) to be used by ISBA for this screen (for all active networks except Public Video networks)
k P&PS 3.0 provided by IDOOH k-value (contact probability) to be used by ISBA for this screen (for all active networks except Public Video networks)
k_per_screen P&PS 3.0 provided by IDOOH k-value divided by number of screens per optical unit ("#Screens Optische Einheit" in "Onsite description")
n P&PS 3.0 provided by IDOOH n-value (number of passages per visit) to be used by ISBA for this screen (for all active networks except Public Video networks)
DT P&PS 3.0 provided by IDOOH DT-value (dwell time in front of screen) to be used by ISBA for this screen (for all active networks except Public Video networks)
net_zone_screen provided by IDOOH concatenation of net_zone and screen_id (used for matching of onsite interviews to individual screen_type_key in individual zones (by network)
touchpoint provided by IDOOH Touchpoint of object according to data field "touchpoint" in IDOOH Venue Taxonomy.
net_type provided by IDOOH Tells ISBA which method of calculation to use for ech individual screen. Background: Infoscreens may be located in train stations, subway stations and airports. The airport touchpoint takes precedence: all media in airports are calculated by the "airport" method. All Infoscreens - regardless of the publisher - are calculated by the "Infoscreens" method. Therefore, the allowed values for this field are:
- Airport
- Infoscreen
- Other

Beispiel

Die ersten 10 Zeilen aus den Stammdaten (ausgewählte Spalten):

screen_id net_id object_id object_id_publisher screen_name_publisher screen_id_publisher pos_x pos_y venue_id_screen zone zone_id screen_status picture_link net_zone
10000001 57 20002425 2 8552101-1 TVW-8552101-1 11.6691 48.0544 4.1.5 Healthcare.waitingroom 4.1 active https://cms.tvw.systems/api/location-picture/QJ8k41AVY3 57.4.1
10000002 57 20002426 4 4023701-1 TVW-4023701-1 6.80145 51.2366 4.1.11 Healthcare.waitingroom 4.1 active 57.4.1
10000003 57 20002427 5 4426301-1 TVW-4426301-1 7.5031 51.4851 4.1.17 Healthcare.waitingroom 4.1 active https://cms.tvw.systems/api/location-picture/G1OAJykPmw 57.4.1
10000004 57 20002428 9 4747501-1 TVW-4747501-1 6.54811 51.5019 4.1.17 Healthcare.waitingroom 4.1 active https://cms.tvw.systems/api/location-picture/egloxBADBM 57.4.1
10000005 57 20002429 20 8641501-1 TVW-8641501-1 10.9889 48.265 4.1.5 Healthcare.waitingroom 4.1 active https://cms.tvw.systems/api/location-picture/6N2r0qonwB 57.4.1
10000006 57 20002430 21 8756101-1 TVW-8756101-1 10.2795 47.4066 4.1.22 Healthcare.waitingroom 4.1 active 57.4.1
10000007 57 20002431 25 4285301-1 TVW-4285301-1 7.18757 51.1808 4.1.17 Healthcare.waitingroom 4.1 active 57.4.1
10000008 57 20002432 36 4486601-1 TVW-4486601-1 7.13154 51.4819 4.1.22 Healthcare.waitingroom 4.1 active 57.4.1
10000009 57 20002433 41 2254901-1 TVW-2254901-1 9.85513 53.5829 4.1.17 Healthcare.waitingroom 4.1 active https://cms.tvw.systems/api/location-picture/29mAZJAGLZ 57.4.1
10000010 57 20002434 49 9042701-1 TVW-9042701-1 11.0473 49.4966 4.1.1 Healthcare.waitingroom 4.1 active https://cms.tvw.systems/api/location-picture/G1OAJzyAPm 57.4.1

Objekte

Screens stehen in Objekten.

Hauptfelder

Data Field Format Status(without POI database)
object_id text required
poi_id text (empty)
object_id_publisher text optional
object_name_publisher text required
publisher_id integer required
street text required
street_number text required
postcode5 text required
city text required
AGS text required
lat decimal required
long decimal required
polygon text required
venue_id_object text optional
venue_id_tag_object text optional
site_frequency decimal required
location_id_doohry text optional
op_hours_monday_start time optional
op_hours_monday_end time optional

Es gibt dann ähnlich wie bei den Netzen 3 Sets zu Ausspielungszeiten.

Spalte AGS '(sales)'

Diese Spalte ist laut Feedback vom 6.2.2025 zur Zeit nicht relevant:

"Ist bisher noch nicht passiert und auf unbestimmte Zeit verschoben."

Ansonsten sind folgende Felder noch wichtig:

Feld object_status

optional

Weitere Felder

Data Field Description
site_frequency_E14+ site_frequency (see above) reduced by children under the age of 14 to yield only people of age 14 years and older.
touchpoint Touchpoint of object according to data field "touchpoint" in IDOOH Venue Taxonomy.

Beispiel

Die ersten 10 Zeilen aus den Stammdaten (ausgewählte Spalten):

object_id object_id_publisher object_name_publisher publisher_id street street_number postcode5 city AGS lat venue_id_object object_status site_frequency_E14+ site_frequency_E14 ohne Off-hrs
20000001 2368-3048-9499-6739 Park Hotel Berliner Tor Hamburg 27 Borgfelder Straße 1-9 20537 Hamburg 2000000 53.5537 7.2 active 46405.4 46405.4
20000002 0462-8785-0967-8580 Stadthotel Hamburg 27 Normannenweg 16 20537 Hamburg 2000000 53.5507 7.2 active 18459.3 18459.3
20000003 6032-5626-5529-0843 Hotel DENBU DTN GmbH 27 Hindenburgstraße 171 22297 Hamburg 2000000 53.618 7.2 active 3700 3700
20000004 3316-5703-8542-6275 Hotel Hanseport 27 Erichstraße 18 20359 Hamburg 2000000 53.5477 7.2 active 3700 3700
20000005 6194-6144-5954-3700 Eidelstedt Center 6 Elbgaustraße 1 22523 Hamburg 2000000 53.6071 2.3 active 60630 60630
20000006 7865-6379-9547-1920 Wandsbek Quarree 6 Quarree 8-10 22041 Hamburg 2000000 53.5729 2.3 active 175827 175827
20000007 0950-5711-9385-2892 Total Hamburg Neuhöfer Straße 28 6 Neuhöfer Straße 28 21107 Hamburg 2000000 53.5107 1.3.2 retired 2971.81 2971.81
20000008 8267-1338-3551-4812 Total Hamburg Billstedter Hauptstraße 21 6 Billstedter Hauptstraße 21 22111 Hamburg 2000000 53.5415 1.3.2 retired 4166.92 4166.92
20000009 2547-6963-9161-0410 Total Hamburg Mundsburger Damm 47 6 Mundsburger Damm 47 22087 Hamburg 2000000 53.5687 1.3.2 retired 4674.19 4674.19
20000010 4660-6629-0447-4413 Total Hamburg Aluminiumstraße 5 6 Aluminiumstraße 5 21129 Hamburg 2000000 53.5173 1.3.2 retired 7209.06 7209.06

Pricing Tables

Enthält Preise für einzelne Ausspielungseinstellungen.

Hauptfelder

Data Field Status Description
publisher_id required Unique ID for publisher issued by IDOOH.
pricing_table_id required Global unique ID for princing table issued by IDOOH. Link to one or more bid(s) via data field "pricing_table" in table "booking units".
pricing_table_id_publisher optional pricing_table ID assigned by publisher; can be used by publisher for newly created pricing tables (no bid assigned yet).
playouts_per_hour required playouts per hour (comma-separated lists allowed) which must correspond to one or more of the values in data field "playouts_per_hour" in table "booking units" (in the bid(s) linked to this pricing table).
spot_length required spot length (comma-separated lists allowed) which must correspond to one or more of the values in data field "spot_length" in table "booking units" (in the bid(s) linked to this pricing table).
weekday_id required weekday_id (comma-separated lists allowed) which must correspond to one or more of the values in data field "weekday_id" in table "booking units" (in the bid(s) linked to this pricing table).
daypart_id required daypart_id (comma-separated lists allowed) which must correspond to one or more of the values in data field "daypart_id" in table "booking units" (in the bid(s) linked to this pricing table).
price_q123 required Price for first through third quarter of year for bid(s) linked to this pricing table for the number of playouts per hour, the spot length, the weekday(s) and daypart specified in the four data fields above.
(either both "prices" OR both "cpm" must be specified = exclusive OR)
price_q4 Price for fourth quarter of year for bid(s) linked to this pricing table for the number of playouts per hour, the spot length, the weekday(s) and daypart specified in the four data fields above.
cpm_q123 CPM for first through third quarter of year for bid(s) linked to this pricing table for the number of playouts per hour, the spot length, the weekday(s) and daypart specified in the four data fields above.
cpm_q4 CPM for fourth quarter of year for bid(s) linked to this pricing table for the number of playouts per hour, the spot length, the weekday(s) and daypart specified in the four data fields above.