Size selection
To filter spaces by size, e-planning allows the following operations:

All the sizes: This option is only visible when the global preference Hide space details in campaign and ads is disabled (option = NO). When the user selects this option, the advanced selection system will not filter by ad size.
Variable: option to select only the VARIABLE spaces, also consistent with the criteria in point (2).
Invisible: option to select only the INVISIBLE spaces, also consistent with the criteria in point (2).
Text: option to select only the TEXT LINKS spaces, also consistent with the criteria in point (2).
(width x height): this option allows to select only the spaces are WIDTHxHEIGHT, also consistent with the criteria in point (2).

Use from the API:
To indicate the size through the API, the user shall indicate in the tamano_id variable, some of the following values:

Variable: tamano_id=v
Invisible: tamano_id=i
Text link: tamano-id=t
Fixed with width W and height H: tamano_id=WxH

If you don’t want to filter by size (All the sizes option), do not include the variable tamano_id within the parameters.

Size selection through conditions:
Through this filter the user may select which spaces to associate to the campaign. In order to do this, at least 1 inclusive condition should be indicated (no maximum limits). A condition is a combination (type, expression) which elements are detailed below:

-Type:
The conditions may be INCLUSIVES or EXCLUSIVES.INCLUSIVE conditions are the ones indicating which spaces may be ASSOCIATED to the campaign. On the contrary, EXCLUSIVE conditions are the ones indicating which spaces SHOULDN’T BE ASSOCIATED to the campaign. The variable type may take the values 0 or 1, where 0 is INCLUSION and 1 is EXCLUSION.

-Expresion:
A condition must also contain a CHARACTER CHAIN, called EXPRESION, which represents a set of spaces. This expression contains objects names (site, zone and subzones) separated by the / character, from which e-planning delimits the spaces search. It is important to note that, given an expression, the spaces to search will be those that are ACTIVE (from now on, when mentioning the spaces, these will be considered always as ACTIVE unless otherwise stated) and that accomplish with the size criteria indicated before.

The first item to mention in the expression is the site’s name. This is mandatory. Then, a zone’s name can be specified. Finally, the subsequent names specified, will be considered as subzone’s names.

You may use wildcards to simplify the expressions
* all the spaces match in the same level within the site’s tree structure.
** all the spaces match in the same level and in the descending levels.

Use from the API:

The variables to specify type and expression are type_N and expression_N accordingly, where N indicates the condition number beginning with the value 0. If 2 conditions are to be indicated, the generic way to do it should be:
tipo_0=<first condition type>&expression_0=<first condition expression>&tipo_1=<second condition type>&expression_1<second condition expression>

Examples:

Example 1

This condition indicates e-planning to select all the spaces from Site1, in Zone2 and with no defined subzones. The variables to define from the API are:
tipo_0=0&expression_0=Site1/Zone2

Example 2

On the other hand, this conditions wll search all the spaces from Site1, Zone2 belonging to any Level 1 subzone. Note that the 3 spaces from the previous example don’t match since they don’t have level 1 subzones. Regarding the other spaces, although the have level 1 subzone, these belongs to subzones from a level greater than 1. The variables to define from the API are:
tipo_0=0&expression_0=Site1/Zone2/*

Example 3

In the example 3, the wildcard ** operation is shown. In this case, e-planning will search all the spaces from Site1 and Zone2 independently from the subzone (this is, spaces with no defined subzone and spaces with subzones from any level as long as they belong to Site1 and Zone2). The variables to define from the API are:
tipo_0=0&expresion-0=Site1/Zone2/**

Example 4

Now, in this example, the exclusion conditions operation is shown. The first condition is the same to the one indicated in the previous example. The second indicates that all the sites from Site1, Zone2 explicitly belonging to the level 2 subzone SubZone2Level2 must be excluded. As shown, the result is intuitive and equal to the previous, excluding the indicated tree portion. The variables from the API are:
tipo_0=0&expression_0=site1/zone2/**&tipo_1=1&expression_1=Site1/Zone2/SubZone2Level1/SubZone2Level2