Bulk Screens Inventory Update

You can use the Bulk Update flow to update a large number of your screen inventory by using a .csv data file.

Note: You can update up to 10,000 screens at the same time.

If you want to quickly update a limited number of information directly from the interface, you can use the Quick Screens Inventory Update flow.

Note: The Inventory page is available to users with the Admin , Direct Sales Admin, Programmatic Admin, and Static Admin roles. See User Permissions for more information.

The screens inventory is synchronized with our Content and Network Management solution. Some of the information is already pre-filled when accessing the inventory for the first time. See Screen Information Origin.

For missing or wrong information for a large number of screens, you can update the information of all of the screens in your network by using a .csv file. We provide a screen data template for you.

To bulk update screens inventory:

Digital Inventory

Creating the .csv file requires three general steps:

  1. Select and export the screen data template from the Inventory list.

    This template contains all the current screen information. See Step 1 – Export the Screen Data Template.

    2. Note: You must follow the format of the screen data template. Otherwise, Broadsign will consider the file to be invalid.

  2. Complete or update the screen data information by respecting the format.

    You don't need to enter the information all at once. You can enter a part of the information and enter the rest later. See Step 2 – Enter Your Screen Data.

  3. Import the file, now containing your screen data, back into your network. See Step 3 – Import the File into Your Domain.

The screens data template provides the allowable columns and correct format. If your publisher has no screens created yet, the columns will be empty.

To export the screen data template:

Digital Inventory

  1. In the Inventory list, select the screens that you want to update.
  2. Click Update Inventory.

    3. Update Inventory

  3. In the window that is displayed, select Bulk Update, then click Continue.

    4. Bulk Update

  4. In the Update Inventory window, click Download Inventory CSV to download a .csv file of your selected inventory.

    5. Download Inventory CSV

    • Your system will download a .csv file.
    • The file name is screen_export.csv.

Note: You must follow the format of the screen data template. Otherwise, Broadsign will consider the file to be invalid.

Some parameters must be properly defined so that your screen can be programmatically transactable. See Transactable vs. Non Transactable.

To open the screen data file:

  1. Open the screen data .csv file that you downloaded (Broadsign recommends Microsoft Excel or similar spreadsheet program).
  2. Enter your screen data as described in Step 2B – Format the Screens File.

The screens data file includes several columns (see CSV File Column Details).

Supported Encoding

Broadsign supports the following data file encoding formats:

  • ASCII
  • UTF-8
  • UTF-16
  • 2143-ordered
  • 3412-ordered
  • Big5
  • EUC-JP
  • EUC-KR
  • EUC-TW
  • GB18030
  • GB2312
  • HZ-GB-2312
  • IBM855
  • IBM866
  • ISO-2022-CN
  • ISO-2022-JP
  • ISO-2022-KR
  • ISO-8859-2
  • ISO-8859-5
  • ISO-8859-7
  • ISO-8859-8
  • KOI8-R
  • MacCyrillic
  • SHIFT_JS
  • TIS-620
  • UTF-16BE
  • UTF-16LE
  • UTF-32BE
  • UTF-32LE
  • windows-1250
  • windows-1251
  • windows-1252
  • windows-1253
  • windows-1255

CSV File Column Details

Column Letter Column Name Description

A-D: Screen identification columns

These columns contain information imported from our Content and Network Management solution. They help to identify the screen on your domain and its location in the field.

Note: You cannot modify columns A-D. If you try to edit them in the file, Broadsign will revert them to what was imported from our Content and Network Management solution.
A

id

Unique identifier for your screen.

This parameter cannot be edited in the Broadsign Platform. Changes must be done in our Content and Network Management solution.

Example: 0a123b4c-56de-7f89-8043-26f93626bf03
B display_unit_id

The ID of the corresponding display unit screen in our Content and Network Management solution. This information is optional.

This parameter cannot be edited in the Broadsign Platform. Changes must be done in our Content and Network Management solution.
C address

Address of the screen taken from the Display Unit.

This parameter cannot be edited in the Broadsign Platform. Changes must be done in our Content and Network Management solution.

Example: 21 Greens Road RD 2 Ruawai 0592
D

internal_name

Name of the screen autogenerated based on the Display unit name and Frame name. See Screen Naming.

This parameter cannot be edited in the Broadsign Platform. Changes must be done in our Content and Network Management solution.
E buyer_facing_name

A short and descriptive name of the screen (location, specialty, etc.). It must be unique.

Example: Times Square Screen
F venue_type_id

Screen venue type ID. See options in Screen Venue Types.

Example: 80701
G allowed_ad_types

Ad types supported by the Broadsign Platform. If more than one type is supported, use a ";" to separate them.

  • static
  • video
  • audio
  • html

Example: static;video;html
H motion_allowed

Whether or not motion type content is allowed to play on this screen.

Example: true
I min_ad_duration_ms

Minimum ad slot length in milliseconds. It must be a value higher than 0.

Example: 10000
J max_ad_duration_ms

Maximum ad slot length in milliseconds. It must not be lower than the Min Ad Duration value.

Example: 30000
K floor_cpm_usd

Screen CPM floor in US dollars.

This is an information field where the publisher should add an average CPM for the screen. Actual pricing will be set at the deal ID level.

Example: 10
L floor_cpm_eur

Screen CPM floor in Euros.

This is an information field where the publisher should add an average CPM for the screen. Actual pricing will be set at the deal ID level.

Example: 10
M floor_cpm_gbp

Screen CPM floor in British pounds.

This is an information field where the publisher should add an average CPM for the screen. Actual pricing will be set at the deal ID level.

Example: 10
N floor_cpm_aud

Screen CPM floor in Australian dollars.

This is an information field where the publisher should add an average CPM for the screen. Actual pricing will be set at the deal ID level.

Example: 10
O floor_cpm_cad

Screen CPM floor in Canadian dollars.

This is an information field where the publisher should add an average CPM for the screen. Actual pricing will be set at the deal ID level.

Example: 10
P open_exchange_enabled

Whether this screen is transactable on our Programmatic Campaigns solution's Open Exchange. If enabled, floor prices are taken directly from the screen object, screens will be visible to integrated DSPs and transactable without a Deal ID.

Supported enable values are:

  • Yes
  • True
  • 1

Supported disable values are:

  • No
  • False
  • 0
  • leave the cell empty
Q audience_sources

Name of the audience data source, separated by ";". See Screen Audience Sources for supported sources.

Example: ACI;Blimp
R audience_type

General descriptor for the type of audience being used:

  • basic – If you are uploading audience schedules into the Broadsign Platform.
  • live – If you are sending audience information live in the ad requests. The audience information is usually from a live source such as Quividi or a real-time audience provider.
S average_weekly_impressions

Estimated average weekly total impressions. It must be a value higher than 0.

This value is calculated automatically by using the next four weeks worth of data to calculate how many impressions are delivered on a weekly (7 days) basis.

This value is used by DSPs to plan their campaigns.

Example: 1000
T average_imp_multiplier

Average impression multiplier for the screen, as in the average amount of viewable impressions per ad slot.
U dma_code

Designated Market Area (Nielsen measurement). Applicable only to US networks.

Example: 501
V bearing

Facing direction of the screen, in degrees. Select between N, NE, E, SE, S, SW, W, and NW.

Example: NE
W diagonal_size

Diagonal size of the screen in the measurement unit defined in Diagonal Size Unit. It must be a value higher than 0.
X diagonal_size_unit

Measurement unit for the diagonal size of the screen. Select between:

  • inches = in
  • centimeters = cm
  • meters = m
  • feet = ft

Example: in
Y screen_image_urls

URL to fetch an image of the screen. The URL must point to a valid Direct Hosted Image URL and not a link to the website containing the image.

You can add multiple URLs by separating them with a semicolon (";").

Valid URL Examples:

https://webkit.org/demos/srcset/image-src.png

https://drive.google.com/uc?export=download&id=1NkxF_oIKN1UrPPp0lJtcbY1oYw9pvsWf

Invalid URL Example:

https://drive.google.com/file/d/1NkxF_oIKN1UrPPp0lJtcbY1oYw9pvsWf/view

Z reference_id

Field available to the Publisher in which they can insert a reference ID for this screen. The field is limited to 255 characters.
AA screen_type_id

Type of the screen used. The screen type is used to assist with Broadsign’s sustainability efforts. Accepted values are:

  • 101: CRT
  • 102: LCD
  • 103: LCD (LED Backlight)
  • 104: LCD (Cathodic Backlight)
  • 105: LED
  • 106: LED Flat Screen
  • 107: LED Large Format
  • 108: Micro-LED
  • 109: oLED
  • 110: Plasma
  • 111: Projector
  • 112: Projector (Laser Bulb)
  • 113: Projector (LED Bulb)
  • 114: Projector (Regular Bulb)
  • 115: QD-LCD
  • 116: QD-OLED
  • 117: QLED
  • 118: QODLED
  • 119: Other (Non-specified)

Example: 101
AB hivestack_id Screen Identifier in Hivestack.
AC vistar_id Screen Identifier in Vistar.

Once the screen data file has been properly filled out, you can import it into the Broadsign Platform. If you encounter issues when importing the file, contact Broadsign Services.

The Upload screen allows you to select your screen data file and upload it in the system.

To upload the screen data file:

  1. In the Update Inventory window, click Continue to Upload.

    2. Upload screen data file

    The Update Inventory window is displayed. You can upload any .csv, .tsv, .xls, .xlsx, .xml, or .txt file with any set of columns, as long as it has one record per row.

  2. Click the Upload data from file button.

    3. Upload data from file

  3. Navigate to your data file and select it.

The Match screen allows you to match your spreadsheet columns to the right data points. You will be able to clean up or remove any corrupted data before finalizing your report. For more information on the data that you must use for each column, see Interface Column Details.

To match your data:

  1. Check your screen data file encoding. If your data in this preview does not look right, you may need to try other encoding schemes. See Supported Encoding.

    2. Screen data file encoding

  2. Define whether your file has column headers.

    3. Selecting your first row of data ensures that you will have the data that you need to move ahead.

    Tip: Once you have selected the useful data and the row containing column headers, you can skip this step in the future.

    Only one row of header data is currently supported.

  3. The import tool has selected the row that it considers as the header row. Select one of the following possibilities:

    • To accept this row as the header row, click Yes.

      • Accept row as the header row

    • To select another row in the file as the header row, click Select another row. Click the radio button next to the row that should be the header row, and then click Confirm.

      • Select another row

    • If your data file does not have a header row, click No header row. You will need to properly match each column in your file.

      • No header row

    The next screen allows you to finalize your data matching. It indicates whether your data columns match the template columns that Broadsign needs to properly display your screen inventory.

  4. Do one of the following:
    • If all of your columns already have a match, click the Review button at the bottom of the screen.

      • Columns already have a match

    • If one or more of your columns do not have a match, use the Lookup matching fields drop-down menu to select a corresponding column. Once done, click Review.

      • Columns do not have a match

    • You can confirm the mapping column by column by clicking the Confirm mapping button. After doing it once, you won't need to do it again.

    • If you do not want to use a column in your file, click Ignore this column. It may be useful if you are using a template that is not the one provided by Broadsign and it has extra columns.

Interface Column Details

The following columns contain information imported from our Content and Network Management solution:

  • ID
  • Display Unit ID
  • Address
  • Internal Screen Name

These columns help to identify the screen on your domain and its location in the field.

You cannot modify these columns. If you try to edit them, Broadsign will revert them to what was imported from our Content and Network Management solution.

Column Name Description
Address

Address of the screen taken from the Display Unit.

This parameter cannot be edited in the Broadsign Platform. Changes must be done in our Content and Network Management solution.

Example: 21 Greens Road RD 2 Ruawai 0592
Allowed Ad Types

Ad types supported by the Broadsign Platform. If more than one type is supported, use a ";" to separate them.

  • static
  • video
  • audio
  • html

Example: static;video;html
Audience Data Sources

Name of the audience data source, separated by ";". See Screen Audience Sources for supported sources.

Example: ACI;Blimp
Audience Type

General descriptor for the type of audience being used:

  • basic – If you are uploading audience schedules into the Broadsign Platform.
  • live – If you are sending audience information live in the ad requests. The audience information is usually from a live source such as Quividi or a real-time audience provider.
Average Impression Multiplier

Average impression multiplier for the screen, as in the average amount of viewable impressions per ad slot.
Average Weekly Impressions

Estimated average weekly total impressions. It must be a value higher than 0.

This value is calculated automatically by using the next four weeks worth of data to calculate how many impressions are delivered on a weekly (7 days) basis.

This value is used by DSPs to plan their campaigns.

Example: 1000
Bearing

Facing direction of the screen, in degrees. Select between N, NE, E, SE, S, SW, W, and NW.

Example: NE
Buyer Facing Name

A short and descriptive name of the screen (location, specialty, etc.). It must be unique.

Example: Times Square Screen
Diagonal Size

Diagonal size of the screen in the measurement unit defined in Diagonal Size Unit. It must be a value higher than 0.
Diagonal Size Unit

Measurement unit for the diagonal size of the screen. Select between:

  • inches = in
  • centimeters = cm
  • meters = m
  • feet = ft

Example: in
Display Unit ID

The ID of the corresponding display unit screen in our Content and Network Management solution. This information is optional.

This parameter cannot be edited in the Broadsign Platform. Changes must be done in our Content and Network Management solution.
DMA Code

Designated Market Area (Nielsen measurement). Applicable only to US networks.

Example: 501
Floor CPM (AUD)

Screen CPM floor in Australian dollars.

This is an information field where the publisher should add an average CPM for the screen. Actual pricing will be set at the deal ID level.

Example: 10
Floor CPM (CAD)

Screen CPM floor in Canadian dollars.

This is an information field where the publisher should add an average CPM for the screen. Actual pricing will be set at the deal ID level.

Example: 10
Floor CPM (EUR)

Screen CPM floor in Euros.

This is an information field where the publisher should add an average CPM for the screen. Actual pricing will be set at the deal ID level.

Example: 10
Floor CPM (GBP)

Screen CPM floor in British pounds.

This is an information field where the publisher should add an average CPM for the screen. Actual pricing will be set at the deal ID level.

Example: 10
Floor CPM (USD)

Screen CPM floor in US dollars.

This is an information field where the publisher should add an average CPM for the screen. Actual pricing will be set at the deal ID level.

Example: 10
hivestack_id Screen Identifier in Hivestack.

ID

Unique identifier for your screen.

This parameter cannot be edited in the Broadsign Platform. Changes must be done in our Content and Network Management solution.

Example: 0a123b4c-56de-7f89-8043-26f93626bf03

Internal Screen Name

Name of the screen autogenerated based on the Display unit name and Frame name. See Screen Naming.

This parameter cannot be edited in the Broadsign Platform. Changes must be done in our Content and Network Management solution.
Max Ad Duration (ms)

Maximum ad slot length in milliseconds. It must not be lower than the Min Ad Duration value.

Example: 30000
Min Ad Duration (ms)

Minimum ad slot length in milliseconds. It must be a value higher than 0.

Example: 10000
Motion Allowed

Whether or not motion type content is allowed to play on this screen.

Click the check box to allow.
Open Exchange Enabled

Whether this screen is transactable on our Programmatic Campaigns solution's Open Exchange. If enabled, floor prices are taken directly from the screen object, screens will be visible to integrated DSPs and transactable without a Deal ID.

Click the check box to enable.
Reference ID

Field available to the Publisher in which they can insert a reference ID for this screen. The field is limited to 255 characters.
Screen Image URLs

URL to fetch an image of the screen. The URL must point to a valid Direct Hosted Image URL and not a link to the website containing the image.

You can add multiple URLs by separating them with a semicolon (";").

Valid URL Examples:

https://webkit.org/demos/srcset/image-src.png

https://drive.google.com/uc?export=download&id=1NkxF_oIKN1UrPPp0lJtcbY1oYw9pvsWf

Invalid URL Example:

https://drive.google.com/file/d/1NkxF_oIKN1UrPPp0lJtcbY1oYw9pvsWf/view

Screen Type

Type of the screen used. The screen type is used to assist with Broadsign’s sustainability efforts. Accepted values are:

  • 101: CRT
  • 102: LCD
  • 103: LCD (LED Backlight)
  • 104: LCD (Cathodic Backlight)
  • 105: LED
  • 106: LED Flat Screen
  • 107: LED Large Format
  • 108: Micro-LED
  • 109: oLED
  • 110: Plasma
  • 111: Projector
  • 112: Projector (Laser Bulb)
  • 113: Projector (LED Bulb)
  • 114: Projector (Regular Bulb)
  • 115: QD-LCD
  • 116: QD-OLED
  • 117: QLED
  • 118: QODLED
  • 119: Other (Non-specified)

Example: 101
Venue Type

Screen venue type ID. See options in Screen Venue Types.

Example: 80701
vistar_id Screen Identifier in Vistar.

The Review screen allows you to check your screen data one last time to ensure that everything is correct.

Review screen

You can do the following:

  • Select to only show the rows in your data file that have issues in them by toggling the Only show rows with problems option.

    • Only show rows with problems

    The problems are shown in red. You can hover over the problem to get a hint at what is wrong, and then correct it. For more information on the data that you must use for each column, see Interface Column Details.

  • Select to only show the modifications that you have done in the update wizard (not in your data file) by toggling the Show modifications option.

    • Show modifications

  • If there is missing information, you can type the proper value in the corresponding cell. If you type something that does not have the correct format, the cell is displayed in red. You can hover over it to get a hint at what is wrong, and then correct it.

Once everything is right, click the Continue button.

If you still have issues in your data, the following window is displayed:

Unresolved format issues

  • Click Go back to return to the Review page and fix the issue.
  • Click Continue to go on with the import process. The row that contains the problematic data will be discarded and will not be imported. The valid rows will be imported.

The Broadsign Platform finishes the import process and displays your updated screen inventory.

Now that you have updated your screens inventory, you can do the following: