You can update the data for the following Static data types:
Static Data Types
Static Campaigns
- Divisions – Divisions are used to indicate internal corporate units for your company.
- Area Levels – The Area Levels creation is mandatory in the system to assign them to Assets. They are part of the setup for Sales Markets.
- Sales Markets – Sales markets are groups of geographic areas.
- Areas - The Area is the lowest-level in an Area Hierarchy.
- Media Groups – Each customer has a different hierarchy of media groups. These are used to organize the inventory of assets into logical groups.
- Sites – A Site refers to the civic address where the media is located. Faces are the installation points at the site. A Site is one of two mandatory hierarchy levels for assets, the other one being a Face.
- Vehicles – Vehicles are part of an Area Hierarchy.
- Faces – A Face represents the advertising surface. A Face is one of two mandatory hierarchy levels for assets, the other one being a Site.
- Advertisers – Clients or companies available for use in the Broadsign Platform.
- Agencies – Firms that create and are responsible for overall planning and of the advertising campaign.
Tip: Each Static data type must be updated individually.
Note: The Static Data Import page is available to users with the Admin, Static Admin, or Static Campaign Manager role.
To update the individual Static data types, you will need to create a .csv file with the appropriate data for each type. Broadsign provides a static data template for you. To speed up the import process, you can update only the data types that need an update.
To update the Static data:
Static Campaigns
Creating a .csv file requires three general steps:
- Select and export from the Broadsign Platform the Static data template for the data type that you want to update.
The template contains all the current Static data. On a new domain, the columns will be empty. See Step 1 – Export the Static Data Template.
Note: You must follow the format of the Static data template. Otherwise, Broadsign will consider the file to be invalid.
- Enter your Static data into the file, respecting the format. You can leave existing columns blank, but you cannot add columns to the file. See Step 2 – Enter Your Static Data.
- Import the file, now containing your Static data, back into your domain. See Step 3 – Import the File into Your Domain.
Note: Broadsign can import files with up to 10,000 rows.
The Static data template provides the allowable columns and correct format. On a new domain, the columns will be empty.
To export the Static data template:
- In the Static Data Import list, click the Update Static Data for the data type that you want to update.
- In the Update Static Data window, click Download Static Data CSV – [Data Type] to download a
.csvfile for the Static data type to update. - Your system will download a
.csvfile. - The file name is in this format:
[data_type]_template. For example: division_template.
Note: You must follow the format of the Static data template. Otherwise, Broadsign will consider the file to be invalid.
To open the Static data file:
- Open the Static data
.csvfile that you downloaded (we recommend Microsoft Excel or similar spreadsheet program). -
Enter your Static data as described in Step 2B – Format the Static Data File.
The Static data file includes several columns that differ depending on the Static data type that you are updating (see CSV File Column Details).
Supported Encoding
Broadsign supports the following data file encoding formats:
|
|
|
CSV File Column Details
The .csv file differs for each Static data type to update. The following tables list the columns for each data type.
We suggest to import your static data in the following order:
- Divisions Column Details
- Area Levels Column Details
- Sales Markets Column Details
- Areas Column Details
- Media Groups Column Details
- Sites Column Details
- Vehicles Column Details
- Faces Column Details
- Divisions Column Details
- Agencies Column Details
Divisions Column Details
Static Campaigns
Note: Changing the Divisions once imported could lead to issues with the data. Assets and Sales Contracts will be impacted by the change.
| Column Letter | Column Name | Description |
|---|---|---|
| A | Division Code | Code identifying the division for external processes and products. This is mandatory. |
| B | Division Name | Name for the division. This is mandatory. |
| C | Is Selling Division? |
Specifies whether this is a Selling Division. Available values are:
Note: A Division can be both Selling and Operator. |
| D | Is Operator Division? |
Specifies whether this is an Operator Division. Available values are:
Note: A Division can be both Selling and Operator. |
Area Levels Column Details
Static Campaigns
Note: Changing the Area Levels after all the Areas and Sales Markets have been imported could lead to issues with the data.
| Column Letter | Column Name | Description |
|---|---|---|
| A | Area Level | Level of the Area, where 0 means the highest level. This is mandatory. |
| B | Area Code | Code identifying the Area. It must be unique per Account Type. This is mandatory. |
| C | Area Name | Name of the area. This is mandatory. |
Sales Markets Column Details
Static Campaigns
Note: To import Sales Markets, at least one Division must already exist in the system.
| Column Letter | Column Name | Description |
|---|---|---|
| A | Area Group Code | Code identifying the Area Group. It must be unique per Account Type. This is mandatory. |
| B | Area Group Name | Name of the Area Group. This is mandatory. |
| C | Sales Market Code | Code identifying the Sales Market. It must be unique per Account Type. This is mandatory. |
| D | Sales Market Name | Name of the Sales Market. This is mandatory. |
| E | Office Code | Code identifying the Office. It must be unique per Account Type. This is mandatory. |
| F | Office Name | Name of the Office. This is mandatory. |
| G | Division Code | Code identifying the division for external processes and products. This is mandatory. |
Areas Column Details
Static Campaigns
Note: To import Areas, at least one Sales Market must already exist in the system.
| Column Letter | Column Name | Description |
|---|---|---|
| A | Area Code | Code identifying the Area. It must be unique per Account Type. This is mandatory. |
| B | Area Name | Name of the area. This is mandatory. |
| C | Area Level | Level of the Area, where 0 means the highest level. This is mandatory. |
| D | Parent Area Code | Code identifying the Area. It must be unique per Account Type. |
| E | Area Group Code | Code identifying the Area Group. It must be unique per Account Type. This is mandatory. |
Media Groups Column Details
Static Campaigns
| Column Letter | Column Name | Description |
|---|---|---|
| A | Media Category |
Media Category to use. Available values are:
This is mandatory. |
| B | Media Group Code | Code identifying the Media Group. This is mandatory. |
| C | Media Group Name | Name of the Media Group. This is mandatory. |
| D | Media Group Description | Description of the Media Group. This is mandatory. |
| E | Media Type Code | Code identifying the Media Type. This is mandatory. |
| F | Media Type Name | Name of the Media Type. This is mandatory. |
| G | Media Type Description | Description of the Media Type. |
Sites Column Details
Static Campaigns
| Column Letter | Column Name | Description |
|---|---|---|
| A | Division Code | Code identifying the division for external processes and products. This is mandatory. |
| B | Site Number | Number identifying the Site. It must be unique per Account Type. This is mandatory. |
| C | Site Description | Description of the Site. This is mandatory. |
| D | Site Type Name |
Name of the Site Type. Available values are:
This is mandatory. |
| E | Area Code | Code identifying the Area. It must be unique per Account Type. This is mandatory. |
Vehicles Column Details
Static Campaigns
| Column Letter | Column Name | Description |
|---|---|---|
| A | Site Number | Number identifying the Site. It must be unique per Account Type. This is mandatory. |
| B | Site Date From (YYYY-MM-DD) | Date as of when the Vehicle is present at that site. |
| C | Vehicle Number | Number identifying the Vehicle. It must be unique per Account Type. This is mandatory. |
| D | Vehicle Description | Description of the Vehicle. This is mandatory. |
| E | Vehicle Category Code | Code related to the Vehicle type. This is mandatory. |
| F | Vehicle Category Name | Name of the Vehicle type, for example: Bus, Tram, Metro. This is mandatory. |
Faces Column Details
Static Campaigns
| Column Letter | Column Name | Description |
|---|---|---|
| A | Site Number | Number identifying the Site. It must be unique per Account Type. This is mandatory. |
| B | Vehicle Number | Number identifying the Vehicle. It must be unique per Account Type. |
| C | Face Number | Number identifying the Face. It must be unique per Account Type. This is mandatory. |
| D | Face Description | Description of the Face. This is mandatory. |
| E | Media Type Code | Code identifying the Media Type. This is mandatory. |
| F | Start Date (YYYY-MM-DD) | Date as of when the Face must be posted. This is mandatory. |
| G | Is Virtual? |
Defines whether the Face is Virtual, that is, are faces that envelope other faces. For example, full bus wraps are surfaces added to the exterior of buses that cover the sides and rear faces of the bus. This is mandatory. Available values are:
|
Advertisers Column Details
Static Campaigns
| Column Letter | Column Name | Description |
|---|---|---|
| A | Advertiser Code | Code identifying the Advertiser. It must be unique per Account Type. This is mandatory. |
| B | Advertiser Name | Name for the Advertiser. This is mandatory. |
Agencies Column Details
Static Campaigns
| Column Letter | Column Name | Description |
|---|---|---|
| A | Agency Code | Code identifying the Agency. It must be unique per Account Type. This is mandatory. |
| B | Agency Name | Name of the Agency. This is mandatory. |
| C | Agency Default Commission | Default commission percentage given to the Agency. If left blank, the system uses the domain default; otherwise it uses the specified value. |
Once the Static data file has been properly filled out, you can import it into the Broadsign Platform. If you encounter issues when importing the file, you can click the Download Log File button to get the error logs for that import (see Download Log File). You can also contact Broadsign Services.
The Upload screen allows you to select your Static data file and upload it in the system.
Note: Broadsign can import files with up to 10,000 rows.
To upload the Static data file:
- In the Update Static Data window, click Continue to Upload.
- Click the Upload data from file button.
- Navigate to your data file and select it.
The Update [data type] window is displayed. You can upload any .csv file, as long as it has at least one row and one record per row.
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 CSV File Column Details.
To match your data:
- Check your Static data file encoding. If your data in this preview does not look right, you may need to try other encoding schemes. See Supported Encoding.
- Define whether your file has column headers.
-
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.
- 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.
- 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.
- Do one of the following:
- If all of your columns already have a match, click the Review button at the bottom of the screen.
- 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.
-
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.
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.
The next screen allows you to finalize your data matching. It indicates whether your data columns match the template columns that Broadsign needs.
The Review screen allows you to check your imported Static data one last time to ensure that everything is correct.
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.
- 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.
- 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.
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 CSV File Column Details.
Once everything is right, click the Continue button.
If you still have issues in your data, the following window is displayed:
- 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. A successful import means that all the data provided has been checked and is compliant. If you encounter issues when importing the file, you can click the Download Log File button to get the error logs for that import (see Download Log File). You can also contact Broadsign Services.
After this step, Broadsign updates the static data in the background.
