A CSV Template with New Landers

While using the Export/Import

feature, all provided data needs to be accurately structured. In order to import many landers at once, you need to add lander's properties for each single landing page to the CSV file and upload the file to Voluum. The below table visualizes what kind of data is required in the file, which data properties are optional and what the order is in terms of adding data to a single row 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 to make the process of adding entities much clearer.

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

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

My Lander;http://voluum.html?geo={country}&os={os};GB;5;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'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

2. 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}&amp;amp;os={os}

3. 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

4. Number of offers

Property: Optional

Description:

The number of offers set within a lander’s configuration that must match exactly to the number of Voluum click URLs present in the landing page itself.

If you leave the Number of offers property blank, then 1 will be set as a default value.

Example:

Number of offers that should be added to the CSV file: 5

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

6. Lander's workspace ID

Property: Required if the Workspaces feature is active.

Description: This is the ID of the Workspace that landers will be assigned to. If you do not have the Workspace feature enabled on your account or you want to assign them to the public Workspace, leave it blank.

Caution

Voluum Note: Users with a Worker role have a read-only access to the Public Workspace, so they will not be able to assign landers to the Public Workspace in bulk.

Example:

This is an ID of the Workspace that landers will be assigned to. You can find the lander Workspace ID in the Landers view in Voluum: