# A CSV Template with Edited Landers

Voluum TRK Bulk Actions Landers

A table format of the CSV file with edited landers requires that all data should be provided according to a certain pattern. To successfully import updated entities of landers, you need to keep the proposed file structure and, if required, double check the data modified in the file. It is highly recommended to provide the data and then check its structure in one of the popular text editors such as Notepad in Windows or Text Edit in OS X. For example, you might need to verify if all columns with data are separated by semicolons. You can perform all updates locally on your machine.

Moreover, once the file with all landers is downloaded, you might provide your changes only for selected entities; those ones that do not require any updates should be removed from the file to make the process of importing the file to Voluum as fast as possible.

The below table visualizes what kind of data is required in the file and which data properties are optional for a single landing page entity updated in the CSV file. You need to keep in mind that the first line in the CSV template is always booked for a description of columns.

In the below panel you can find an example of a single row in the CSV file:

# 1. Lander ID;2. Lander's name;3. Lander's URL;4. Country code;5. Tags

5a144987-7a51-4817-ae9b-0fc0dc484803;My Lander;http://voluum.html?geo={country}&os={os};GB;health summer

Moreover, there are basic rules that you need to follow to avoid issues with the file upload:

1. The file must be properly formatted CSV and saved using UTF-8 character encoding.

2. One CSV file can contain up to 250 landers. It means that there should be up to 251 rows in the file - the first row is dedicated for a description of columns.

3. One lander is represented on a separate row in the CSV file.

4. In the file, each row must end with a line break.

5. Each column must be separated with a semicolon.

### Caution

Voluum Note: Each property of the lander needs to be separated with a semicolon.

• If you edit the CSV file in one of the text editors, you will be able to see the semicolons while editing it.

• If you edit the CSV file with Excel, you need to pay attention to the delimiter setting set locally on your machine. If Excel uses as separators semicolons, then each property is located in a separate Excel column. You should see that the CSV file looks as follows while editing it:

6. Only certain pieces of information are required and they are associated with the required fields in the lander's form in Voluum. Other properties might remain blank.

7. If you leave the optional properties blank in the CSV file, the values of the properties will be respectively overridden with the default values after importing to Voluum.

For example, if you leave the Country code property blank in the file, the Country setting in Voluum will be set to Global.

8. Lander's properties need to be added according to the following patterns:

1. Lander ID

Property: Required

Description:

This is a unique lander ID specific for Voluum.

### Note

Voluum Info: The lander ID is automatically available in the downloaded CSV file.

Only if something got messed up with the ID, you can easily find it by performing the following steps:

b. Go to Landers. The Landers view will show up.

c. If the ID is not displayed in the Landers view, perform the steps in the picture below:

d. After clicking the Apply button, the lander ID should show up in one of the columns of the Landers view.

e. Find the ID of your lander and copy it to your CSV file.

Example:

Lander ID that is available in the CSV file: 5a144987-7a51-4817-ae9b-0fc0dc484803

2. Lander's name

Property: Required

Description:

This is a unique lander’s name.

If you are familiar with the Voluum lander’s name pattern, it should be the custom suffix of the lander’s name that you provide in the Name field in Voluum:

{country_label or Global} - {your unique custom name}

You need to keep in mind that the {country_label or Global} phrase is added automatically by Voluum while saving the lander entity.

Example:

Lander's name that should be added to the CSV file: My Lander

3. Lander's URL

Property: Required

Description:

The lander’s URL with its additional tokens can be passed in a URL’s query string to perform dynamic call-outs.

Example:

Lander's URL that should be added to the CSV file: http://voluum.html?geo={country}&os={os}

4. Country code

Property: Optional

Description:

This is a two-letter country code. Voluum accepts the country codes provided according to a certain pattern - if required, you can download the file with codes for all countries: two-letter_country_codes.csv

If you leave the Country code property blank, then the Global value will be set for your lander.

Example:

Country code that should be added to the CSV file: GB

5. Tags

Property: Optional

Description:

You can add one or more tags to your lander to easily search for the lander in Voluum. If you want to use more that one tag, they should be separated by spaces.

Example:

Tags that should be added to the CSV file: health summer